dummzeuch

Fixed the toolbars for all dialogs.

Kinda fixed that today for two dialogs.

Thanks! I just fixed the link. Note to self: Always check those links!

You could use the IDE to debug a second instance of it. That might give you a call stack and a hint what causes the problem. Just don't do what causes the crash in the first instance.

Recent versions of Delphi (for a suitable definition of “recent”) come with a TZipFile class implemented in the unit System.Zip. This class has the really neat feature that it can not only read the contents of a ZIP file directly from a stream but also extract a file from that stream to a TBytes array, thus it does not require any file system access. E.g. imagine you have got a memory stream containing the contents of a ZIP archive. [read on in the blog post]

It doesn't ignore the decimal separator as such, but will always assume it to be '.' rather than the value of DecimalSeparator. So converting '123.4' will result in 123.4, but converting '123,4' with DecimalSeparator = ',' will result in 123 and an error at position 3.

They didn't even fix all high DPI issues of the IDE itself. But yes, having to do that for a plug-in might show some more.

Should this support any number format which TryStrToFloat supports? E.g. '5.4E7', '543,543.647' or ' $0abc6'? Or are there restrictions? What about decimal and thousands separators? What about negative numbers? Negative exponents? The more flexible it must be, the slower it will become. The easiest case would be: Only decimal digits and only a decimal point, no negative numbers. No range restrictions. No exponents. That would be fairly simple and fast, because it's a state machine with only a few states.

Not going to happen. And neither the IDE. We have had this discussion too many times already.

Since the current Community Edition is 10.4, it definitely makes sense to evaluate it. Unless you plan to buy the Professional Edition, then it makes sense to evaluate Delphi 11, because that's what you will be getting.

There is a now an installer for version 1.3.19 Alpha of GExperts for Delphi 11.

You mean this one? {$IFDEF IDE_IS_HIDPI_AWARE} if MinWidth < 1000 then MinWidth := 1000; if MinHeight < 1000 then MinHeight := 1000; {$ENDIF} I don't even remember why I added it. I probably was totally frustrated with trying to get that dialog working in whatever way with Delphi 11 on high DPI, that I simply pulled some absolute values out of my hat so see whether they work. Surrounding it with if TScreen_GetDpiForForm(Self) > 96 then begin end; Will probably solve this one particular problem.

I bet if we look hard enough, we will find remnants from pretty much any old Windows version in there. I also bet that it still comes with the driver for the obsolete "Microsoft Ballpoint Mouse" and automatically installs it when a GPS is attached via a USB serial adapter. An annoyance which I had to put up with since Windows XP.

Hm, the minimum height for this form is set to 660 pixels. That might be a bit tight depending on the height of your task bar. On top of that there might be the general scaling problems in Delphi 11, but I actually doubt that this is the issue. If you want to, get the sources, change the height of the GX_Configure form to e.g. 600 and compile your own DLL.

I consider multithreading as hard enough to not use it if it isn't necessary. And there are many types of programs where it isn't. In particular, as you said, the lack of proper debugger support makes it hard.

What's your screen resolution and scaling?

The last time I looked, they not only did not supply such a file, but also shipped an ancient version of jedi.inc (with the DUnit sources if I remember correctly). I had the misfortune of including that directory in the search path once and it took me hours to find the cause for the sudden compile errors.

Actually, the $IF compiler directive appeared in Delphi 6.

Great, just what I need. GExperts for Delphi 11 just got pushed further into the future. I'm really despairing with this high DPI stuff. Maybe I should just give up and wait for 11.1. There are more fun things to do with my spare time than trying to somehow work around all those bugs in Delphi 11.

There is probably a central include file that needs updating for Delphi 11. And most likely this will fix all the compile errors.

The GroupView property was one of the compile errors, so apparently wasn't supported back then. No idea, when it was introduced. I currently haven't got the time to investigate further.

Thanks, but unfortunately it does not compile with Delphi 2007 (haven't tried any other versions yet) and after I commented out everything that did not compile, it simply does nothing (Enter opens the currently selected todo rather than filtering.) I'll have a closer look at it later to see whether it is possible to make it work somehow.

It hasn't complained yet. 😉 (16 GBytes of RAM go a long way even with Windows 10, if you don't use VMs) Currently I have got 3 instances of Delphi 2007 and 2 of Delphi 10.2 running (on separate virtual desktops with different projects of course).

That's what the BDSLauncher.exe tool in the Delphi bin directory is for. It's usually registered as default program for *.dpr / *.dproj files. (And it's the first thing I replace because I actually want a separate BDS instance for each project.)

Now would probably a good time to switch to something else. We did that about 15 years ago. Even if they find somebody that solves their problem this time, there is no guarantee that somebody will be able or willing to help out again. I just looked and could not find a link to the source code, it's not on sourceforge either, maybe it's on GitHub.