Jump to content

Tom Mueller

  • Content Count

  • Joined

  • Last visited

Community Reputation

5 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Tom Mueller

    Menu captions with images are hard to read under Windows 11

    Yes, that's something Embarcadero can't change. But it seems that if the menu is connected to an ImageList Embarcadero uses its own draw method. There are no round corners anymore and the text color does not change to white. I found a QP issue for the rounded corner as well and I created one for the text color problem: https://quality.embarcadero.com/browse/RSP-34597 https://quality.embarcadero.com/browse/RSP-35800
  2. Hello I found that the Captions of Delphi's TMainMenu and TPopupMenu are hard to read under Windows 11, if an ImageList is connected to the menu. Tested with Delphi 10.4 and 11.0. Windows 10 menu without and with images (ok) Windows 11 menu without and with image (hard to read black text on dark-blue background) Can anyone reproduce this behavior? Best regards Tom
  3. Tom Mueller

    Delphi 11.0 has a different form Caption offset than Delphi 10.4

    Set the forms BorderStyle to bsDialog, bsToolWindow or bsSizeToolWin. Sorry, forgot to mention that.
  4. Tom Mueller

    Delphi 11.0 has a different form Caption offset than Delphi 10.4

    Yes, OwnerDraw would probably work - if I use a base form for all the forms in an application. I hoped that there is a more simple way to I just adjust the intent of the caption.
  5. Hello Has anyone noticed that in Delphi 11.0 the indentation of the form caption is larger than in Delphi 10.4? Especially under Windows 11 the small indent with Delphi 10.4 is irritating. IMO Delphi 11.0 makes the better indentation. Is there a way in Delphi 10.4 to adjust the intent of the form caption (without using Styles)? Best regards Tom
  6. After installing Delphi Rio Update 2 with the WebInstaller, I realized that some core files are dated from 08. July 2019 00:55 and others from 30. July 2019 15:55. The build number is 26.0.34749.6593 and as far as I remember this build was release on the 08. July 2019. So, how can it be that a lot of core files, like BDS.exe and BPLs have a newer date than the release date but the same build number? Any Ideas?
  7. Tom Mueller

    Add support for High-DPI gdiScaling

    Yes, I agree - it would be the right way to update all applications to fully support high dpi. For our applications this will take probably 1-2 years and some money that our customers won't spend.. I will do so. Thank you for comments!
  8. Tom Mueller

    Add support for High-DPI gdiScaling

    I agree, but what means seriously outdated applications - all MDI applications and Delphi IDE? 😉 No, it should be an additional item in the DPI awareness drop down box. I called it "System Aware (enhanced)" - but I see it makes it clearer if it is named "GDI Scaling". Delphis DPI Awareness modes and its Manifest entries would then look like (simplified):
  9. Tom Mueller

    Add support for High-DPI gdiScaling

    Yes, but it would be easier and more logical if it would be an auto generate option. "System Aware" in Delphi should corresponds to "System" in application properties (<dpiAwareness>system</dpiAwareness>). So I named it "System Aware (enhanced)" that should correspond to "System (enhanced)" in application properties (<gdiScaling>true</gdiScaling>)
  10. Most "older" applications do not have full support of High-DPI scaling. To enhance the appearance of these applications Microsoft added the gdiScaling option in Windows 10 Creators Update (1703) . <asmv3:application> <asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2017/WindowsSettings"> <gdiScaling>true</gdiScaling> </asmv3:windowsSettings> </asmv3:application> In the compatibility settings of the windows property dialog of an application this is marked as "System (enhanced)" Delphi manifest option do not support this scaling mode at the moment. Our Build-tool sets the gdiScaling option in the manifest - but a build inside the IDE with gdiScaling is not possible! I also added a feature request in QP: https://quality.embarcadero.com/browse/RSP-24175. If you miss this option too - please vote for It. Best regards, Tom
  11. Hi Andi Thank you for providing us your tools! dfmCheck is a very useful tool - especially for large projects with a lot of forms. I encountered one problem for projects with FastReport. FastReport writes the main component TFrxReport into the pas file - all sub-components are only stored inside the dfm without a reference in the pas file. Unfortunately our projects use a lot of FastReport and therefore a compilation with your generated special unit is not possible. My question: do you see a possibility to exclude units or classes (actually only TFrxReport) from the dfmCheck - or even a switch "- Ignore FastReport"? Best regards, Tom
  12. Tom Mueller

    What is the compiler switch -VN used for?

    Yes, I've seen that - "-VN = TDS symbols in namespace" but what does it mean?
  13. Hello Some questions: Can somebody explain what the compiler switch -VN is used for? Where can it be set inside the IDE (Delphi 10.3.1)? Why is this switch the default Delphi 10.3.1 setting for new projects? Why is this switch doubled when the -VT switch is set inside the IDE? (you can see the command line in the "Build" tab of the "Messages" tool window) Any hints would be appreciated!
  14. There are not so many resource strings. In my DevExpress package I include 45 units with "resourcestings" in it - that will extracted about ~5000 resource stings. PS: Sorry for the delayed answer.
  15. Yes, I tried this approach - but it is a clumsy way. - limit the units by try_and_error per package - merge the resulting drc-files into one drc-file per 3rd party for the translation tool Actually Delphi raises the error after the creation of the drc-file (so the linker does its job with the drc-file but then raises E2621 when trying to create the bpl-file). Our automated building process will stop because of this error. I wonder if there is an option to tell the linker to just extract resources?