FredS

I just type garbage for the first two now, then try and read that idiotic picture on the third one..

RSP-35486 TRttiField.SetValue breaks past bevaviour with Null and String

Not if you you code it to respond to the Classes.SyncEvent : https://stackoverflow.com/a/61022449 I use both, in one case I have many threads collecting data and triggering updates to a form while getting ready to launch another Task I don't want to pause the updates so a call gets wrapped in an Async which uses the trick above.. but I try to only do that for single calls that are guaranteed to take a short time.

This scenario doesn't sound like it needs Async at all. Start a thread with an OnTerminate Event Disable all user input and show a busy signal When the thread completes the event fires and all reverts back to normal For the few cases that Async is needed there is `MsgWaitForMultipleObjects`..

Notepad++ next 🙂

Nearly all forms I show modal return a result. At the most basic level all these forms are inherited from one base form which has this code: class function TBaseDialogForm.ShowDialog(AOwner: TComponent): Boolean; begin with Create(AOwner) do try Result := ShowModal = mrOK; finally Free; end; end; class function ShowDialog(AOwner: TComponent): Boolean; virtual;

Maybe looking for a third MVP to help out 🙂

To paraphrase a post; it now takes two MVPs to update a plug-in for D11 HighDPI..

Sure, its only been what.. well under a decade 🙂

Explains some complaints I've heard..

Always loved Flamerobin, one of the best functions in Flamerobin is their quick way to 'Generate rebuild script'..

I also ran a couple of tests and it made no diff; Zero, GetDesktopHandle, GetActiveWindow, Application.Handle and Mainform.handle all appeared as normal.

Be happy with what you've got 🙂

My point was that your user can disable it which is why it may show up as you first described. Secondly, if an option can be set it can be read, that way at least you would be able to alert the user that such a thing might occur..

I wouldn't go as far as that but certainly there have been plenty of high end components where the source didn't compile. This tells me that few or none do this anymore.. used to be the norm..

This setup works for me:

Or offer a Community Edition first? The only problem with that would be that would increase the reported bug count dramatically..

Stopped that after the 'Flow control Highlights' became available, at least in IDEs that support it.

Its a bad feature: Disable Full-Screen Windows 10 User Account Control (UAC) Prompts On Your PC, Here’s How

This version has so far worked well on Win7, but when altering options there is (repeatable) this: Access violation at address 500C4163 in module 'rtl280.bpl'. Read of address 17775000. [500C4163]{rtl280.bpl } System.TypInfo.GetEnumName (Line 1630, "System.TypInfo.pas" + 20) + $4 [5005FAC2]{rtl280.bpl } System.UTF8IdentStringCompare (Line 17746, "System.pas" + 3) + $4 [50CED2C2]{vcl280.bpl } Vcl.StdCtrls.TCustomCombo.GetItemIndex (Line 4276, "Vcl.StdCtrls.pas" + 4) + $11 [500C40FF]{rtl280.bpl } System.TypInfo.GetEnumName (Line 1616, "System.TypInfo.pas" + 6) + $C [170EDFBD]{mmx_bds22.dll} PropInfo.TObjectAccess.GetValues (Line 507, "PropInfo.pas" + 7) + $29 [170ED74C]{mmx_bds22.dll} PropInfo.CopyProperties (Line 198, "PropInfo.pas" + 12) + $9 [1735F78F]{mmx_bds22.dll} PascalOptionsFrm.TMMXPascalOptionsForm.ApplySettings (Line 104, "PascalOptionsFrm.pas" + 1) + $14 [17248612]{mmx_bds22.dll} MMX.Options.Form.TOptionsPage.ApplySettings (Line 720, "MMX.Options.Form.pas" + 2) + $6 [17247CA1]{mmx_bds22.dll} MMX.Options.Form.TOptionsShellForm.ApplySettings (Line 435, "MMX.Options.Form.pas" + 3) + $F [17247BC1]{mmx_bds22.dll} MMX.Options.Form.TOptionsShellForm.ApplyBtnClick (Line 389, "MMX.Options.Form.pas" + 2) + $2 [50CC8223]{vcl280.bpl } Vcl.Controls.TControl.Click (Line 7660, "Vcl.Controls.pas" + 9) + $8 [50CF03F6]{vcl280.bpl } Vcl.StdCtrls.TCustomButton.Click (Line 5875, "Vcl.StdCtrls.pas" + 3) + $2 [50CF1580]{vcl280.bpl } Vcl.StdCtrls.TCustomButton.CNCommand (Line 6510, "Vcl.StdCtrls.pas" + 1) + $B Similar may have happened while altering 'Metrics' but this one is repeatable when changing the 'String Identifier Prefix' and either clicking 'Apply' or 'OK'. It won't save the changes, after a restart if I go in and ONLY change this single option it works. Changing 3 or 4 using 'Apply' a couple of times and coming back to this ends the same way..

Still using MMX 14.05 on Win10 🙂 Which makes it easier to ignore all those parsing errors! That new RED icon makes you look at all those directives which are ignored.. I may just revert to 14.05 on Win7 and leave that alone, if no other users are reporting these issues and you can't reproduce then we may just leave it at that. I am noticing some slow down since installing 15.0.47 in D11.. and LSP issues. Could be those exceptions and a reboot is needed..

Unfortunate History tells me that this is when the real headaches get started.. unlike everyone that wants a bug report with full details from coders, the end user base usually just tosses it out and don't even bother to report those 'unknown' issues..

Sure seems that way, won a bet that we'd have 10.5 before key issues in 10.4 where solved..

So at least one step above 'unusable' 🙂