Rollo62

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.

Where is DeepBlue in that list ? Is this just an open-source competition, not comparing the leading engines ?

I assume the "Intel" is an integrated BLuetooth, while for the "Braodcom" you used an external USB-Bluetooth stick, is that correct ?

When I try to set different colors in the IDE, this can be used to set "fake" colors, at least for black color. This should be right to set black background color. Like that: results in "float-like" output: { "colors" : [ { "idiom" : "universal", "color" : { "color-space" : "srgb", "components" : { "alpha" : "1", "blue" : "0", "green" : "0", "red" : "0" } } }, { "idiom" : "universal", "color" : { "color-space" : "srgb", "components" : { "alpha" : "1", "blue" : "0", "green" : "0", "red" : "0" } }, "appearances" : [ { "appearance" : "luminosity", "value" : "dark" } ] } ], "info" : { "version" : 1, "author" : "RAD Studio" } } Anyway, the issue with white background while BG/FG is still the same. I assume it has something to do with Styles and TListView, not the storyboard colors.

I have some issues from time to time, with the LauchScreen, but not only the image. Sine this is maybe all related, I think this could be added in the thread too 1. In one app I have a too small launchscreen icon. The base icon is same size, but it appears only 1/3 of the size on its screen. Have tried to reset settings, re-create project, etc., clear the storybook, change the colors, etc. but it stays the same. While other projects icon looks OK, stretching to fit the whole display, I cannot really see any difference. (but since this behaviour was acceptable, I haven't looked into it much deeper). 2. A newer, and not acceptable behaviour is the white background when an app goes background and foreground again, it starts with a white background screen, until "BecameActive", only then I can reset the screen again. Its not showing the LaunchScreen then, but the current display, and this is "white" instead of normal color. To get a better impression, on the fron page there is a TListView: This is how it should look (and it does when first starts) This is how it looks when background/foreground, until "BecameActive", only after BecameActive I can reset, but thats a well visible flicker when starting. It looks to me that the style or the listview is somewhat affected by background foreground change, since I cannot find any other reason for setting the colors like that. I do use the StyleManager, and setting the style once at startup, usually no need to reset again when BG/FG. What I tried is to set the background colors in many ways, also to force a change, but I want to put them "black" in light and dark themes, like that: I think this was a similar issue here. When I change the colors, Apple seems to require the colors as float (0.0 ... 1.0), but in the .storyboard template I can see a white background (color 1 1 1 1) <resources> <image name="LaunchScreenImage" width="96" height="96"/> <namedColor name="LaunchScreenBackgroundColor"> <color red="1" green="1" blue="1" alpha="1" colorSpace="custom" customColorSpace="sRGB"/> </namedColor> </resources> In the compiled storyboard, this is still the same <resources> <image name="LaunchScreenImage" width="96" height="96"/> <namedColor name="LaunchScreenBackgroundColor"> <color red="1" green="1" blue="1" alpha="1" colorSpace="custom" customColorSpace="sRGB"/> </namedColor> </resources> But additionally, there were LaunchScreenBackgroundColor.colorset definitions, looks as HEX instead of 0...1 { "colors" : [ { "idiom" : "universal", "color" : { "color-space" : "srgb", "components" : { "alpha" : "255", //<=========================== HEX instead of float "blue" : "0", "green" : "0", "red" : "0" } } }, { "idiom" : "universal", "color" : { "color-space" : "srgb", "components" : { "alpha" : "255", //<=========================== HEX instead of float "blue" : "0", "green" : "0", "red" : "0" } }, "appearances" : [ { "appearance" : "luminosity", "value" : "dark" } ] } ], "info" : { "version" : 1, "author" : "RAD Studio" } } That looks like an issue with the RadStudio conversion of those flags HEX instead of float , but even when I handcode the .storyboard files, I cannot really see a difference (maybe because of caching). I try to investigate this further. Maybe the launchimage, the too small icon 1.) and this color issue 2.) were all related somehow, but I cannot really spot the root cause. I hope you can spot the issue here, and has some useful hints.

Well, unexpectedly Apple-M1 did not so bad in emulation. I haven't found many reports on compatibility issues yet, so maybe someone knows more about the Do's and Dont's with this emulator: what can be used, what will crash ? I think no Hypervisor, OK, but what restrictions have normal apps ?

Beside that, what are the latest news about the ARM, Softbank, Apple, Nvidia theatre ? I think this will affect us all, if ARM is in the wrong hands. Then I have to move back to good old Z80

Damn, I missed that fact. Apple is really the hottest sh... Does that mean also VmWare Fusion, Win-10 guest and Rx1041 is running as before ? (No, I cannot believe that, its too much utopia for my, Apple runs out of the box ....)

Good decision. Nonworking LSP and all related stuff is the biggest time killer for me at the moment, I'm looking forward to a behaviour as smooth as VsCode. Waiting for the day when Ctrl+Space, Ctrl+Enter, ErrorInside, debug variables, etc. works 100% reliable.

How is that possible ? I thought PAServer is a Macos binary, on x86, not a Java thingy ? At least I can see dylib's in the package content. Or do you found a new, ARM compatible PAServer somewhere ? I don't think Apple is emulating x86 assembler code on M1, or do they ?

Did you also set the location permissions (fine should be enough, but fine+coarse do no harm) ?

Is there a reliable table somewhere, for the references of different components, platforms, tools, etc., which where used in the IDE ? Would be very good to get an overview about that, to see what references especially could be problematic.

Even if it would not results in any fixes in the final launch. At least you could judge the impact of new versions on your own projects, and try to find workarounds early in time.

Waiting for Christmas eve, ..... lots of gifts, presents and good mood 👼