Forum Replies Created
-
AuthorPosts
-
June 30, 2024 at 9:45 am in reply to: Embarcadero Partners with Raize Software for KSVC Maintenance #3941
Excellent news!
Looks like Delphi 12.1 fixed two KSVC bugs:
KSVC: TRzCheckBox bottom/right anchor problem with monitor DPI change and autosize
Incorrectly scaling in HighDPI when using TRzSplitter
All of the KSVC bugs I reported in Quality Central for Delphi 11 are still open in Delphi 12.
It doesn’t look like Embarcadero did much with KSVC in 11.3. So, you might wish to vote for more KSVC issues. You can do this by going to
https://quality.embarcadero.com/secure/Dashboard.jspa
You can find KSVC issues via Issues > “Search for issues”. Enter “KSVC” in the “Contains text” search box. For “Status”, check all the check boxes except “Closed” and “Resolved”.
David
Maybe you are having this problem:
https://quality.embarcadero.com/browse/RSP-39701
RSP-39701 KSVC: TRzFormState makes form wrong size if form moved between monitorsJanuary 29, 2023 at 10:49 am in reply to: Why is Application.ProcessMessages necessary for TRzLauncher.Running? #3437P.S. I’m still wondering why, in my test app, thread 1 needs to call ProcessMessages for thread 2 to update FRunning.
January 29, 2023 at 9:12 am in reply to: Why is Application.ProcessMessages necessary for TRzLauncher.Running? #3436Ray,
Thank you. Your test project is what I was thinking of when I wrote “The
way you outlined it, the main app would be idle while the launched process
finishes, so the VCL would call ProcessMessages.”Currently, my app does more in the main thread than it should. So, I’d need
to do a good bit of recoding to make it work like your test app. I have
this on my to-do list.David
January 25, 2023 at 2:50 pm in reply to: Why is Application.ProcessMessages necessary for TRzLauncher.Running? #3432Ray,
I just tried the OnFinished event. I had it set a boolean field of the form
when it fired. It has the same behavior: I need to call
Application.ProcessMessages for the boolean field to be set.My app launches the secondary app, then continues to do other stuff. But,
there are some things I don’t want the app to do while the launched process
is still running.The way you outlined it, the main app would be idle while the launched
process finishes, so the VCL would call ProcessMessages. If my app already
knows what it wants to do next, but doesn’t want to start doing it until
the secondary app finishes, it needs to wait. That’s why I have the loop.
Maybe I can rearrange things so my app doesn’t need to wait.Regardless, I’d still like to understand why threads work this way. Is the
following correct? The main app is thread 1. The TRzLaunchThread object is
thread 2. The launched process is thread 3. The TRzLauncher object is
passed to TRzLaunchThread, so both threads 1 and 2 can read/write the
FRunning field. But, something doesn’t happen unless ProcessMessages is
called; I don’t know what.David
If you have Delphi, you can install it via GetIt: https://blogs.embarcadero.com/konopka-signature-vcl-controls-version-7/
Embarcadero has been fixing things in the components. You should report bugs to them. See https://raize.com/forums/topic/trzbitbtn-2/#post-2614
I believe some of the components have had problems with high dpi. Has this been addressed?
RSP-29903 was just closed, so it appears that they fixed it.
Is the problem with the TRzCheckBox size fixed (RSP-29903)?
December 17, 2020 at 1:54 pm in reply to: Konopka Signature VCL Controls Problems on Delphi Sydney 10.4 #2307Everyone with an update subscription is invited to the beta: https://blogs.embarcadero.com/delphi-and-cbuilder-10-4-2-beta-invite-for-update-subscription-customers/
September 15, 2020 at 6:48 am in reply to: Konopka Signature VCL Controls Problems on Delphi Sydney 10.4 #2218I reverted to Delphi 10.3.
-
AuthorPosts