PeterPanettone

Each time I start Delphi 11 Alexandria, there is an INVISIBLE window with the window title "ProDellInterface27": (This is a row screenshot from my System Explorer 7.1.0.5359 app). 398192 is the window handle. 12468 is the Process ID of BDS.exe obviously owning this window. Does anybody know what functionality does this window have? (BTW, I don't have any Dell device in my system).

You are right. This is the BPL which integrates it into the IDE: C:\PROGRAM FILES (X86)\EMBARCADERO\STUDIO\22.0\Bin\PDIFac27.bpl

You are right - my eyesight is not the best. Maybe "Del" is an abbreviation for Delphi? But who on earth wants to save 3 letters in a 17-letter word?

Thanks for the information.

For those who use a WelcomePage mainly for organizing their projects, there is a nice project manager here - Pascal Project Manager 4.01 (Program can be used with German or English language) : https://www.hastasoft.de/PPME.htm

Thank you for WUPPDI! We are waiting with excitement.

It seems Embarcadero does not provide the information when TListView.GroupView was introduced?

I have found it here: https://my.embarcadero.com

Looking for the 2007 compiler: https://cc.embarcadero.com/MyDownloads.aspx ...does not provide a 2007 compiler. Where can the 2007 compiler be downloaded? Even in My Registered User Downloads there is no 2007 compiler: https://cc.embarcadero.com/myreg

Could you show what did not compile in 2007? The filter is based on TListView.GroupView (no advanced features have been used). Has such an essential feature as GroupView not yet been introduced in the dark age of 2007? It does compile without problems in Delphi 11 Alexandria.

There is a patch for Delphi 11 in GetIt: However, none o the most important bugs in Delphi 11 seem to have been addressed: 1. Persistent customization of the IDE toolbar still does not work 2. Still no Parnassus Bookmarks. Is there a mention of the patch in the IDE UI?

Can your computer afford the additional memory needed for multiple BDS instances?

Isn't there a startup parameter for BDS.exe to disallow multiple instances of BDS.exe? (BDS checking if there is already an instance of BDS.exe running).

You did not write where the DANGER MESSAGE can be turned off.

If the upgrader unit is part of the main application then the main application de facto is still not terminated. If this works for your company then this does not mean it works for BDS.

Thanks for verifying this. I suspect that a very short presence o two instances of BDS.exe could have triggered a modal GExperts error message which could have blocked the first instance from terminating (GExperts always shows an error message when an additional BDS instance is created). This looks like the BDS restart procedure consists only of a termination statement ("Close;") followed by a BDS execution statement (or vice-versa). This is what I would call "debile programming". A self-restart should always be done with the help of an external helper program waiting for the EXPLICIT termination of the main program.

Maybe we should define more exactly what "GetIt induced restart fail" means - as my ambiguous statement "the restart does not work" could lead to misunderstandings. For me, "restart fail" means that there are multiple instances of BDS.exe running after a restart is required after a GetIt install. A self-restart should check whether the application is still running (using an external helper program) and restart itself only when it is completely terminated.

I know. You're perfect.

What annoys me most: When the IDE needs to be restarted after a GetIt install, the restart does not work. Most of the time, there are TWO instances of BDS.exe running with lots of error messages. Can someone tell the maker of GetIt how to correctly make a program restart itself?

I call the time the user has to wait from double-clicking the app program file until the app window becomes visible AND usable the "App Start Time" (AST). If I want to minimize AST, there are different strategies: 1. Instantiate secondary forms dynamically at run-time and not before the user needs that form. The time needed for such dynamic instantiation during the app's run-time usually is neglectable. 2. During AST, show the user a funny animated splash-screen to entertain him, so he becomes unaware of the passing time. Does anybody know of other such strategies?

That's a good idea!

These are really funny.

I have already tried that. But users say it's not entertaining.

Are you sure that would entertain the user?

A great way to change things at run-time in Delphi applications is a RUN-TIME OBJECT-INSPECTOR.