uligerhardt

I'd compare your original docx before and the one after the user pressed "Yes". Maybe you can see what you have to change in the differences.

That's only true for the uses-clause entries that the form designer manages. (Which is a tiny fraction in my development.)

If I'm not missing anything, Oxygene didn't "reverse" it, but kept it consistent with Pascal.

There is http://docwiki.embarcadero.com/RADStudio/Sydney/en/Writeable_typed_constants_(Delphi). It's just off per default for some years now.

https://blogs.windows.com/windowsdeveloper/2021/01/21/making-win32-apis-more-accessible-to-more-languages/ Sounds very interesting.

Ok, then I misunderstood you. 😎

This is about generating wrappers for classic Win32 API, Not some WinRT stuff. Autogenerate Windows.pas! 😎

Hello! I want to show a MessageBox from inside a TL21_.OnViewerButtonClicked event handler and need the window handle of the preview form for that. Any idea how to get there?

I tried it just now, and it works AFAICT - I used GetWindowText(gPrintReportWnd, ...) to verify. Thanks a lot.

Here is the relevant code, a bit condensed: type TPrintLLReportEventHandler = class public procedure OnViewerButtonClicked(Sender: TObject; Button: TViewerButton; var PerformDefaultAction: Boolean); end; { TPrintLLReportEventHandler } procedure TPrintLLReportEventHandler.OnViewerButtonClicked(Sender: TObject; Button: TViewerButton; var PerformDefaultAction: Boolean); begin if Button = vbExit then begin MessageBox(AWnd, .....); // <= I'd like to get the preview form's window handle here for AWnd end; end; var evh: TPrintLLReportEventHandler; evh := TPrintLLReportEventHandler.Create; try MyLLReportInstance.OnViewerButtonClicked := evh.OnViewerButtonClicked; // Show preview here (using LL_PRINT_PREVIEW) finally evh.Free; end;

Sorry, forgot to mention it in the message body. It's the List&Label report component.

Yes. I guess DevEx wouldn't like us to pass links around, however outdated the components may be.

Very good. 🙂

No, that's "original content" that I just created just for this thread. 😄

Maybe using TApplicationEvents.OnMessage like in the attached project. RerouteMouseDown.zip

There is Visual Forms (http://www.jed-software.com/vf.htm). Never tested it.

That's how TFont is streamed, at least in VCL: Either you leave ParentFont at True or the complete TFont properties are stored. I hate that too.

I'd check the *.dproj for spurious entries.

Regarding dynamic construction: I only know FastReport and List&Label. Both have DOM-like APIs. And FastReport has scripting.

Um - the name Motif is already taken: https://en.wikipedia.org/wiki/Motif_(software).

I wasn't clear enough... Why would you rely on this even if it worked?

Why would you rely on this? Without the tiniest comment?

Thanks! I missed that feature on every Delphi upgrade. Re: clipboard format: Can't you just hand over the text? You can probably even put into a TMemIniFile for reading.

Couldn't you use a normal Delphi enum (i.e. without assignments) for the "main" values and define the extraneous ones as untyped constants?

No, that's why I'm talking about class methods. You can use them like this: type TMyEventHandler = class public class procedure OnError(const AMessage: string); end; Something.OnError := TMyEventHandler.OnError; The method has to be non-static to provide the needed Self parameter.