Der schöne Günther

That's not harmful, it's just unnecessary code. What really rustles my jimmies is something like this: try doSomething(); except ShowMessage('There was an error'); end;

This is just an idea, maybe it matters whether the executable is being debugged, started from IDE or started from explorer? Maybe it inherits some settings from its parent process (the IDE).

Interesting option, I never knew. Anyways, I suppose this should only affect applications from Delphi environments that are over a decade old?

That's usually how I can spot if an application has been made with Delphi - They forgot to make dialogs close with [Esc] or the tab ordering is completely random 🙃

The IDE offers to relocate a class to another unit by right-clicking under "Refactoring" but - surprise! - it never works. Does MMX have this feature? I see it has elaborate ways to add to an existing class or even move things around within the class declaration. But so far, I have not been able to find anything that allows me to move a class (declaration and implementation) to another unit. Is that correct?

Just tried it out, thank you so much 😍

Do you have plans for incorporating the "real" thing as this would be possible with "XAML Islands" [1] [2] or will you stick with mimicking? [1] https://docs.microsoft.com/windows/uwp/xaml-platform/xaml-host-controls#uwp-xaml-hosting-api [2] https://github.com/Microsoft/Windows-appsample-Xaml-Hosting

Hard to imagine, given that the result of TRestClient.Create(..) is not known at compile-time. This would not be a "const", but a readonly variable. Maybe one day Delphi will also have that?

I believe the modifiers are lost when translating a hotkey to a string: Raw hotkey value = 0x0646 ShortCutToText() = F TextToShortCut() = 0x0046 program Project1; uses System.SysUtils, Vcl.Menus, Winapi.Windows, Winapi.CommCtrl; procedure p(); const VK_F = $46; HOTKEYF_CTRL_ALT = (HOTKEYF_CONTROL or HOTKEYF_ALT); // Ctrl+Alt+F var hotkey: Word; asText: String; begin hotkey := VK_F or (HOTKEYF_CTRL_ALT shl 8); WriteLn('Raw hotkey value = 0x', IntToHex(hotkey, 4)); asText := ShortCutToText(hotkey); WriteLn('ShortCutToText() = ', asText); hotkey := TextToShortCut(asText); WriteLn('TextToShortCut() = 0x', IntToHex(hotkey, 4)); end; begin p(); ReadLn; end.

Moreover, your "SLI" record that appears to wrap IShellLink fails to check the return value of SetHotkey

As far as I understand, this would serve as a "bridge" from Object Pascal code - via "LangServer" - to IDEs that support "LangServer stuff". The page lists example IDEs such as Emacs or VS Code. The latter already has an excellent plug-in OmniPascal.

Settings for automatically following threads you create or reply to: https://en.delphipraxis.net/notifications/options/

2018-10-26_16-51-53.mp4 What can I do to prevent this?

He even talks about it right here: