Rollo62

That is good news, that releases of Delphi may run on M1. I think we still will have x86 Mac's for a while, so still some time until we really need to move to M1 as debug tool. Hopefully there were no hidden catches in the Rosetta 2, that let us need support more urgently.

https://en.wikipedia.org/wiki/Naming_convention_(programming) here with some examples ... Anyway, it seems that I use sometimes the RadicalMixedPascalCamelSnakeCase, if it makes sense to force visual readability and visual grouping

Yes, thats possible too, and I always wonder why on earth I should ever do it like that ? Oh yeah: Its so much advanced over FError, to have a fancy pig-tail in front

I know its modern nowadays to use all kind of bare names for anything. But those names are very likely to conflict with identifiers, keywords, etc., with a whole bunch of possible hard.-to-find sideeffects. Thats why I still like consequently use the decoration of names: L - for local instance: LError F - for field instance: FError G - for a global instance: GError (nevertheless: global variables are not recommended) This little extra char gives me a lot of extra-info - its not a function or procedure, if you use it with discipline - its not a global, intrinsic function, if you use it with discipline - its a local or field instance, or even global All this just because of the tiny character, I think its still very much worth it.

Don't know about JveSoft, but that looks interesting. JveSoft seems to add a whole lot of critical frameworks, are you sure they were all needed for your function ? How is JveSoft sourcecode structured, can parts of the sooftware be easily separated, or do you need to use all or nothing ? I would always try to minimize the critical frameworks, if possible.

waden = want a damn exclusive name

@Vincent Parrett Nevermind, these were just jokes DPM is fine related to NPM .... (if not yet taken, I would consider that name by myself).

YADPAM - yet another Delphi package manager

To clarify: Its not in the enterprise version either, it was only a time limited test-license, in Rx10.3, until the next version. I wanted to check, but didn't find the time to. Now my test-license is gone, and I'm looking for other options.

Sorry, DOPE is nothing what programmers are aware of. Then better call it COFFEE "clean object file fragmentizer for external entities" .

Maybe so, it came from a text from Goethe, here in a Googled translation

In germany we have a saying: "names are sound and smoke"

How about +vraptor" vincent's rad application package tool open resource" ? Only 18 hits, when using the "+" ...

This "naming pattern" is not limited to the uses alone. I know, most people dislike that decorating of function names, but I do that in some similar cases too, like that: MtIfThen(...

Oh so 20's: Today, I say "Alexa, kill bill" Next year, I think: "GPT-3, optimize Windows and solve my customer Scott's code issues"

Far from that, don't worry I'm sure you're right, as I said, but for different kind of apps or audience maybe. What you refer to is to safe a second, thats only true for the very professionals, like programmers, designers, 3D animators, you name it. Maybe I am talking about the usual "normal" user, they probably don't care on speed but on clearness of the UI. Startup phase is an important part of the UI IMHO, for example I see many setup programs taking lots of time before showing up. I hate that behaviour, because II always feel unsure if they started, or doing massive trouble, so I have to doublecheck if its running or not.

Well spotted, delivering hard evidence to a hypothetical discussion From a philosophy standpoint I could say: "Be responsive". On desktop you will get away with non-responsive behaviour, but on mobile your app is very likely KILLED. I leanrned that the hard way

Maybe your argument is right for some kind of apps, maybe command-line like, but WindowsTaskManager is probably not a good example IMHO. When I press CtrlAltDel, and then need waiting so long until anything happens, I personaly would prefer the directly responding display, and maybe gradually populating Tast Manager. I think what all people give bad mood at PCs comes from to "trigger any action", and then wait unreasonably long to see any result, giving impression somethings wrong. Very often I press buttons twice, just because of that, and ran into other nasty issues then. This is what we try to target by responsiveness, by keeping things in threads instead of UI. I prefer the full responsiveness over saving some seconds here or there. Imagine the Windows Task Manager, gradually populating, this by chance has listed your desired process immediately at the top, and you can work with that already, while the others are still populating. If your not lucky, and your process is the last in the list, at least this is understandable, and you got a nice progress display. I find this less annoying.

I focused a lot to mobile development, but those concepts were also good for desktop IMHO. Since many years I use "lazy initialization" on startup, this keeps the EXE slim and fast, no need for ugly splash-screens. Then after FormShow I see the app, and can do some lazy configurations, and provide a nice display, if needed. Most of the time these configurations were faster than the user clicks, so its not recognizable to most users. This way customer see its starting and working fast, and they don't complain, I think big splash screen is more annoying. Even a disabled app, during "lazy configuration" feels a lot faster than if you do this before the app is visible. I think time is relative, if the user sees some reactions from time to time, this is squeezing time&space a lot, like a warp drive. Another advantage of lazy initialization is, your app is already under full control. Errors, exceptions, logs, etc. can be much better debugged in this state, while during the fragile startup phase.

Usually the newer PaServers detect themself when outdated, and can update automatically, when pressing Test in the ConnectionProfileManager.

Jon missed to mention the SVG rendering capabilities, among other features.

Do you need IbTogo ? I recall a case where this was added by some unit, Once removed it compiled, but that was an older Xcode case.

You could remove the flag, by the use of a PointerVariable as pointer to function. In SetFlag, you can switch the PointerVariable to the desired, real function, so that the PointerVariable always willl be valid. Then just calling the PointerVariable will not need any conditional check inside.

I believe so too, but DeepBlue is worth mentioning, isn't it ? Isn't this evolving too, with never versions, or is it a complete dead project now ? At least it was the first beating the human chess wolrd champion, should be a little honoured IMHO.

Have you checked out the functionality with some tools, like https://www.microsoft.com/de-de/p/bluetooth-le-lab/9n6jd37gwzc8?activetab=pivot:overviewtab https://www.microsoft.com/de-de/p/bluetooth-le-explorer/9n0ztkf1qd98?activetab=pivot:overviewtab https://www.nirsoft.net/utils/bluetooth_viewer.html https://www.nirsoft.net/utils/bluetoothcl.html https://sensboston.github.io/BLEConsole/ Of course the Nordic tools should be great too, but thats already developer tools for the MCU's, but they have a lot of helpful tools as well. https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Connect-for-desktop Maybe someone knows better tools for Windows, since I usually work with Android/iOS.