PeterPanettone

Having to RECREATE a Dock Window on each IDE session IS indeed useless. That would be the same as if you had to inflate your bike tires again each time before each ride on your bike.

Thomas, thanks for sharing this information. The Dock Window can indeed be useful, as it is not subjected to the whims of the IDE who often changes the position of things in a seemingly rather irrational manner. Thank you for having created the Dock Window "because you could"! However, unfortunately, it is USELESS without being automatically restored after IDE restart.

BTW, what was the motivation for you to create the Dock Window GExpert?

Ah, I suspected that. So it seems the saving and restoring of the Dock Window has to be implemented by GExperts itself. Do you need support for implementing that?

Thanks for the information. However, a thing without saving and restoring it's like a ... ... thing without saving a restoring. I am looking forward to the implementation of Dock Window restoring after IDE restart. However, isn't the saving and restoring of IDE desktop elements done by the IDE desktop itself? Thank you for your exceptional work!

When using TBCEditor in my program, how can I keep up with all copyright requirements? Should I put a Copyright remark on my About page naming all involved authors?

I have now tried SynEdit from the Delphi GetIt Package Manager: I have tried out the demos: I am very unsatisfied.

I don't understand your comment: What has TBCEditor to do with SynEdit?

I slightly extended the simple demo: BCEditorDemoEx1.zip Please feel free to extend it further.

While in Form Designer mode, when switching from one unit to another unit (e.g. by selecting another tab), the Instances List in the Object Inspector is being updated with the Object Instances of the new unit. So far so good. Unfortunately, this is not the case in Source Code Editor. However, the Object Inspector (and thus the Instances List in the Object Inspector) is often needed also when the Source Code Editor is active! So this bug should be fixed and the Instances List in the Object Inspector being updated while the Source Code Editor is active when switching from one unit to another unit and the new unit contains object instances! Please vote for this quality report to have this bug fixed: https://quality.embarcadero.com/browse/RSP-32183

You are right. I will try to add some screenshots to make the matter clearer.

You mean, an IDE expert that updates the Instances List of the Object Inspector with the objects of the current unit? This is a brilliant idea.

My question had no ironic undertone, I really meant it. I agree that reports are clearer when containing screenshots, and I thought about inserting screenshots.

As the opinions about this matter seem to be divided, maybe there should be OPTIONS to set the behavior in this case.

The object stays NOT selected while switching unit in Designer mode. Your statement is WRONG. (While I understand your point of view). When writing source code in the Source Code Editor (80% of the time), one often has to access the Object Inspector with the objects of the current unit. So it would be important to have the Instances List of the Object Inspector always updated.

What screenshots would you like?

There is no slowing down from updating the Instances List in Object Inspector when switching from one unit to another unit. Rather, the slowing down occurs when having to switch from Source Code Editor to Form Designer and then back to Source Code Editor on the new unit, only for the purpose of updating the Instances List in Object Inspector!

I tried to record a macro that does the following actions: 1. Copy the selection in the code editor to the clipboard (with CTRL-C) 2. Switch to Design mode (with F12) 3. Focus the F6 search-box (with F6) 4. Paste the previously copied selection into the F6 search-box (with CTRL V) But recording this macro in the IDE does not work!

I gave him the idea.

Liu Xiao from CnWizards has just confirmed to me that he will implement this functionality in the next nightly build. http://www.cnpack.org/showdetail.php?id=862&lang=en

If the caret in the Source-Code Editor is placed on the identifier of an existing component, for example: ...then an IDE command (e.g. "Select Component") should select this component in the Design Structure Panel (and in the Instances List of the Object Inspector). This would be VERY USEFUL! I kindly invite everybody to vote for this quality report: https://quality.embarcadero.com/browse/RSP-32108

When I type "il" in the F6 filter box , then I get these 3 results in the Components section: However, when I make the filter term more specific by typing "ilsvg" then I get these 4 results in the Components section: This inconsistency IMO makes the F6 filter-search a rather inefficient tool for filtering down the existing components for selecting them in the Designer Structure Panel. For this purpose, IMO it would be much more efficient to have a filter box in Structure Panel itself. So I kindly invite everybody to vote for this Embarcadero quality report: https://quality.embarcadero.com/browse/RSP-32021

When we all will use quantum computers - and when Windows 12 will run on quantum computers - then this kind of speed problems will be a thing of the past. 🔮

When opening the GetIt window in Delphi 10.3.1 I get this error message:

In Delphi 10.4 GExperts, Uses Clause Manager shows strange text effect upon selection of a text item where every selected text seems to have a shadow: Never seen anything like this. Has anyone else? It appears to happen only in Uses Clause Manager. I believe source code version is r3177.