Jump to content

Tom Mueller

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

2 Neutral

Recent Profile Visitors

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

  1. 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?
  2. 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!
  3. 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):
  4. 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>)
  5. 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
  6. 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
  7. 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?
  8. 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!
  9. 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.
  10. 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?
  11. Hi For our project translation tool I extract all resourcestrings from 3rd party components into drc-files. This is donne by creating a temporary package with all units containing resourcestrings and then compile it with the --drc switch. Until Delphi 10.2 this worked perfectly. With Delphi 10.3 some of these packages cannot be created anymore. Delphi will raise an "Error: E2621 Export table in output file too large: exceeds 65536 limits" There is a bug report about this error https://quality.embarcadero.com/browse/RSP-22698 but it is marked as "Resolved" "Workes As Expected". Instead of a package project I tried to include all units into a console application - this compiles without a problem - but not all resourcestrings are extracted into the drc-file. To my question: Anyone knows another way to extract all resourcestrings int a drc-file from 3rd party source files?
  12. Yes - some properties get refreshed during typing and some not. So far I checked the properties for some basic components that do not refresh: - BevelWidth - Top - Left - Width - Height - Tag - ImageIndex - Margins (Bottom, Left, Right, Top) - Constraints (MaxHeight, MaxWidth, MinHeight, MinWidth) - TabOrder It seems most numeric properties (beside the Name property) do not fire a change event when loosing the focus.
  13. Thank you for your tests - so it seems that this error came with 10.3 Update 1. I will comment this in the bug report https://quality.embarcadero.com/browse/RSP-23694 Please vote for the fix for this error in the bug report - so we might have a chance to see the error fixed in 10.3 Update 2 soon.
  14. When changing a property value, for example the name property of a TLabel in the object inspector and then directly select another component on the form, the changed name value is not saved. Only pressing the Enter key or changing to an other property saves the changed value. Steps to reproduce: add two TLabel on an empty form and select one change the name of the label without pressing the enter-key select the second label select the first label again -> your changed name is gonne! In Delphi 10.2.3 Tokyo this error was not present. It is not a killer bug but a very annoying issue! Can anyone reproduce this issue? PS: I reported the bug on https://quality.embarcadero.com/browse/RSP-23694
×