dummzeuch

OK, so Left := -(GetSystemMetrics(SM_CXSIZEFRAME) + GetSystemMetrics(SM_CXPADDEDBORDER)); works for Left (actually it's Left := Form.Monitor.WorkAreaRect.Left - (GetSystemMetrics(SM_CXSIZEFRAME) + GetSystemMetrics(SM_CXPADDEDBORDER)); because the left edge of the monitor might not be at pixel 0). It does not work for the height though: Height := Form.Monitor.WorkAreaRect.Height + 2* (GetSystemMetrics(SM_CXSIZEFRAME) + GetSystemMetrics(SM_CXPADDEDBORDER)); still leaves a gap to the bottom border of the monitor. But that's consistent with Windows + Left (but not with maximizing the window)

btw: https://devblogs.microsoft.com/oldnewthing/20150304-00/?p=44543 (I knew I read about this somewhere, just didn't remember were.)

Hm, that seems to be kind of a magical value, because if I use that rather then the -7, it works. It's also -8 on my PC.

This is not about letting the user do anything but the program positioning its window. (To allow the user to do that, the ScreenSnap property is no longer necessary in Windows 10.)

This patch was missing the changes to the .dfm file. GX_GenericUtils.GetUserApplicationDataFolder can replace the %appdata% environment variable which is what causes the dialog to fail showing the correct directory. As far as I am aware there is no official way to get that number. GExperts declares some constants depending on the VERnnn symbols in GX_VerDepConst. The public documents subdirectory is not one of them, but you could easily add a constant for that. since the required number is already part of the CompilerDefinedProductRegistryKey. Please remember that Wuppdi was only available for some Delphi versions (I don't really known which ones), so that option doesn't make sense for e.g. Delphi 6. Yes. I would implement it this way: Instead of showing the file select dialog show your own dialog. It gives the path of the wuppdi ini file in an edit field (you know the path and filename, so you can check whether it exists and display an error if it doesn't). This edit should allow drag and drop (TWinControl_ActivateDropFiles) and autocompletion (TEdit_SetAutocomplete) and offer a ... button to let the user select the file. A second edit field allows entering the name of a subfolder to import into.

Welcome to date format hell. Once you go that way, you will find out that there are many more different date formats than you ever imagined and that many of them are incompatible to each other. My favourite example: US: MM/DD/YY UK: DD/MM/YY If you have the choice always go with an international standard: ISO 8601

Assign NIL to it and later reassign the original event.

Since he already has a hex editor (looks like HxD in the screenshot), setting those bytes to zero would be easy. I don't really see the need for anything Delphi specific there at all

As far as I know they can only read from the registry. I'm also not sure when the IDE updates these entries: Whenever they change or only when closing.

I know of only one "pure pascal" solution for jpeg compression: nativejpeg

You could try to use libjpeg-turbo (or even the original libjpeg, but I don't recommend it). I don't know how do use that with TBitmap32 though, I only used it with TBitmap and a BGR-in-memory-buffer. There are Delphi interface units for it.

Bug report(s) on Sourceforge please.

general FAQ bug reports

Bug report on SourceForge please.

Some things that were obvious in the VCL apparently are not in FMX. I want to change the background color of a single control on a form, e.g. set a TEdit control which failed input validation to yellow. This must not affect the color of the other controls on the form. In the VCL I would simply set TheEdit.Color := clYellow. An FMX TEdit does not have a Color property. Instead apparently one has to use styling, controlled by the properties StyledSettings, StyleLookup and StyleName. Am I missing something? How can I accomplish this?

Now this is interesting. I wonder whether the TVirtualTreeView descendant used in the Delphi IDE also implements that API. Not having access to the entries in these various trees has prevented me to implement some useful functionality.

You are out of luck. TVirtualStringTree is completely written in Delphi and does not have an underlying Windows control, so there are no messages that can be intercepted.

That would be illegal. Are you saying that it would be illegal to ask a friend to compile Delphi source code on their own copy and send me the exe? No, it would be illegal to send you "the compiler exe". That's what he wrote, but apparently he meant to write "the compiled exe". That would be perfectly legal. Sorry for the misunderstanding.

That would be illegal.

Hm, all GExperts units have an underscore in the name: GX_Whatever and all units in my dzlib library do too: u_dzWhatever as well as most units and forms in the projects at work: w_Whatever and u_Whatever. We are not using D11 yet at work (and for GExperts I try to avoid it too because it always breaks the dfm files), but that doesn't bode well. I wonder whether using underscores in unit names is that uncommon that nobody has come across a problem with that during the beta.

Yes, they have been broken basically since forever and for the CurlyHalfCommentEnd one I don't really care much. But the MultilineFunctionDirective bug is really annoying. I must find some time to finally fix that. The way the tests currently work is by checking the all the supplied settings with various input files and comparing them to the output files. Testing one particular setting is currently not really part of the test. Maybe it would be easier for you to simple create a new TTestCase and, based on the default settings of the formatter, only run the two tests you mention. btw: Thanks for caring about the unit tests. That's a first for any contributor.

I seem to remember something about that on on StackOverflow. GExperts only shows a warning if more than one instance of the same IDE version is opened. I usually disable that warning because I actually want to habe multiple instances (for multiple projects on multiple virtual desktops). Then I have no idea what the problem might be. You can download the help file from SourceForge just in case your version is broken.

Maybe its not the file itself but the project that's broken?

I'm pretty sure that wasn't meant as a joke. You didn't mention that it happens rarely, so he probably assumed the problem to be reproducible. In that case uninstalling stuff until the problem goes away would have been a good strategy.

GExperts does not have such a functionality. As for the help not showing: Is that a standard installation or did you copy the help file somewhere else? The help file in the installer is definitely fine, I just checked. It's many years out of date though since I have never updated it.