Stano

To take it literally: no results can be displayed during editing.

Um, they advised me, and I follow that. Query the ID value in advance and use it in SQL. If you fail, you drop it. I have no idea if this can be done in your case. I do not have knowledge and skills.

object vilLitD: TVirtualImageList DisabledGrayscale = True Images = < item CollectionIndex = 0 CollectionName = 'button_rounded_blue_first' Name = 'button_rounded_blue_first' end item CollectionIndex = 1 CollectionName = 'button_rounded_blue_previous' Name = 'button_rounded_blue_previous' end ... ImageCollection = dtmdBasic.icDBNavD ImageNameAvailable = False Left = 50 Top = 30 end OK. See dfm.

If I understood the instructions well, VirtualImageList converts images according to DPI. Therefore, they must be on every form. So only one image size should be enough. If I misunderstood, correct me.

I have a problem with the width of the breakpoint space

If you mean me, yes. Your answer is more than weird. E.g. what about aaabbbcccddd ....? I assume you know what you're doing. Text length can be affected by: by setting a value in the DB component by defining in the DB table field used database I'm in the habit of combing each text string with leading and trailing chars (spaces) before saving it in the DB.

Remember: is the entered value valid?

As far as I know, with limited rights.

I used Format uses clause. I would like FireDAC.xx.yy to form a separate group as a System.xx, Vcl.xx and etc. That there is them FireDAC.Comp.Client, BasalForm, FireDAC.Stan.Param, FireDAC.Comp.DataSet, FireDAC.Stan.Intf, FireDAC.Stan.Option, FireDAC.Stan.Error, FireDAC.DatS, FireDAC.Phys.Intf, FireDAC.DApt.Intf, FireDAC.Stan.Async, FireDAC.DApt,

It happened.

You forgot one piece of information. What a component it is.

If you own a D professional and are considering a DB server, I wouldn't even try FireDAC

Becose: TVirtualimagelist renders images according to HDPI. It is a duty - see help This technology gives visibly better results If you look in dfm, you will find TVirtualimagelist only stores links to images You only add the necessary images to TVirtualimagelist I tried this: TAdvGlowButton has three types of images "Normal", Disable and Hot. I set the size 16/18, 24/26 and 32/36 for Hot. This achieved the "pop-up" effect of the button when aiming. Rendered it's perfect. With old technology, this is impossible in my opinion.

RAD Studio 11.1 Patch 1 This patch is about 400MB to download. Quality Portal issues addresses by this patch RSP-37880 Can't debug iOS RSP-37760 Using ImageList causes IDE to crash RSP-37733 IDE Access Violation when Inheriting from a Form with a TListView in DynamicAppearance. RSP-37690 GridPanelLayout on form memory leaks on end app -- same if not used at all RSP-37667 Cannot fit requested classes in a single dex file (# methods: 71471 > 65536) RSP-37665 Code Insight broken for classic compiler RSP-37662 Segmentation Fault(11) in SysUtils.Pop on Android64 RSP-37609 PAServer ships with Python 2.7 dependencies - which are no longer available in macOS 12.3 RSP-37408 Delayed flag break Exe's ASLR function RSP-37378 Memory leak RSP-35040 64bit packets in c++ containing delphi code do not run We have also addressed an issue with MongoDB transactions, a FireMonkey memory with the TGPUObjectsPool class var instance (associated with RSP-37690), and a Delphi compiler issue (on some platforms) related to AtomicCmpExchange128.

I passed TImagaCollecton + TVirtaulImageList. I recommend it. Now to the topic. I'm behind only one central image container. And refer to him. Reasons: The application does not inflate unnecessarily Especially if I need a change, I'll make it in one place. It is automatically reflected in all places of use

Can anyone else open Word there? Because if so, you have a problem.

an error message: "Cannot focus a disabled or invisible window" clearly states what this is about. You need to make sure that the window where you want to target a component is visible and accessible. You don't have one of them (or both). Only debugging (with Break point) will help here.

Too bad my secret dreams aren't coming true.

What would happen if they released a version with only 96 DPI support. I think that would be enough for many developers.

I learned something new again. Well thank you.

Not very confusing. But it provides many options. Luxury is paid for. Check the Arrange - by Category option in the Object Inspector. So it's clearer. All events begin with the prefix On. So BitBtn1.OnClick.

I don't know if it will be interesting for you. To avoid similar and different problems with DBGrid, I switched to TVirtualStringTree very quickly. About a week. And I was a beginner. I have no problems with TVirtualStringTree. For the same reasons, I left the DB components. Then I bought TMS components and after a while I went back to DB components. But TMS.

It is OK. Unfortunately, this has always been the case.

Cursor to TPath and F1

I always create all Actions only once. They live during the life of the instance. I define an OnExecute event in the component and, if necessary, at design time in the instance I want this behavior on the runtime: if the event is only in the component, it will not always exist, so it will be triggered if the event is only in the instance, it will fire if the event is in the component as well as in the instance, then the event in the instance is triggered first and the event in the component is called with inherited Classic behavior About component TjstVstDBNavigator = class(TCustomActionToolBar) strict private FAcnMan: TAcTionManager; Current status In the component, I assign an Action OnExecute to each. As a result Logically, only the event in the component always fires Event in the instance will never run