Rollo62

I would love that Feature too, but I would also completely drop it, if that debugger cannot even inspect an Integer value correctly all the time. First things first...

What happens when you offset the Top and Left position ?

I wanted to use Jenkins, but since Jenkins X arrived I'm a kind of starred like a rabbit in front of a snake, not konwing the status and future of Jenkins. While Jenkins X is a dockerized version of Jenkins, but not really compatible and not my true favorite, I'm not sure where the roadmap and the developers will move. Will Jenkins dissappear and get less active, or not ? Will Jenkins be replaced by Jenkins X in the long run ? Is Jenkins X just intended for different kind of customers ? Meanwhile still some time has passed by, and Jenkins seemed still normal and active, but I haven't checked the current situation for a least a few months now.

When you start XCode, open the menu Windows/Devices and Simulators/ page, then plug in your iPHone device do you see the iPhones info popping up in this page ? If not, maybe some settings were missing, like the registration of your device in the AppStore, the provisioning files, etc. Not sure if you have a full Apple account already, or if you just first time playing with this stuff ?

You mean these little red thingies ? Not visible enough for me, I use standard lines like this, as my default

@dummzeuch Done. You're perfectly right. At this time of the day my english translation brain sub-module doesn't work so well anymore. I have to wait until next morning, if I'm lucky

I hope that I make my first D11 AppStore Upload soon ... thats usable enough if it works as expected

I prefer 2 as well. But in case of AntiPattern, I like to make "shouting" comments showing me where the problem sits. Make it as as much as "shouting" as you like, its more a question of "taste" ( Ok, I'm overdoing a bit in the upper example ). Are these "shouting" comments another AntiPattern maybe ? 🤔

Another question beside the move to M1, if Apple will also move away from Objective-C to Swift, with more speed now. I think Swift will still be a problem for Delphi, but on the other hand maybe its easier and cleaner too once a bridge is in place. But I'm afraid that it includes more obstacles for Delphi, as Objective-C did (which has maybe not the latest features inside). Will M1 ARM also affect this move to Swift somehow ?

But you have to sometimes, in case of you have to use Android / iOS. Anyway, I find D11 quite stable so far, but I'm still in the process of porting and testing. At least I can say that I have no show-stoppers yet 🙏

Not sure if you mean Cef4Delphi ? This one is always quite actual.

If there is no way to use Win x86 on this nice M1 MacBook Max machine, this will be a showstopper for me. So I will be probably locked-in on Intel desktop then, lets wait and see. I don't believe in Win on ARM and Microsofts x86 emulation that much, so maybe time will tell.

Exactly, the issue was that it always overwrites, no matter what you do, which may drive you crazy soon. After a single checkbox change, it behaves normally again (toggle), but I'm afraid I had never seen the locking of the insert mode.

Yes, when usually toggling the insert key, to change between INSERT and OVERWRITE mode, this is ignored and stays at INSERT ( only in Delphi behaves like that, other apps do change the mode ). The solution is to change above combobox selection.

I still have hope that we will see VmWare or the like on M1 Macos, which is able to support x86 Win10/11. That would leave the problem to VmWare to make it run. I haven't thought too deeply about what that conversion would mean on the CPU virtualization side of an entire OS, but why not its also simply a "program" Yes, maybe a missing hypervisor emulation would be a problem.

That is a very good point, maybe that is not so good news if Wintel is needed, like for Delphi. It would be worth checking that with Apple, and try to get some clear guarantees. On the other hand, this time they are not moving from IBM to Intel, but from x86, which means they will have the chance to catch Wintel users in the long run. Why should they kill a well working emulator solution, which can attract all the Windows users to M1, I think cancelling that would be a stupid marketing decision. At least they had added some more interfaces, like HDMI, etc. this is what their advertising said, not sure in detail how many USB sockets they have. But I'm used to have a short USB-Hub dongle plugged in anyway, so not that big deal for me.

Me neither. Sometimes I recognize that INSERT mode had changed, and this won't get back by normal key, only by changing the mode here. Maybe there is also a hidden catch like that for Ctrl-F, somewhere hidden in the options ?

I only can say: Try to never use XCode "Betas", better always wait until the version is stable. They can cause a lot of issues, and can also make your whole environment unusable, by possibly enforcing further (beta) updates on iOS.

I want to re-activate this old thread, but its still a current topic. Apple launched their new M1 Pro and M1 chips and Max MacBook Pro's https://www.apple.com/apple-events/october-2021/?cid=CDM-USA-DM-P0021510-488761 Well, I'm not an Apple salesman, but I better should be. This really blows all other laptops away, if it works as smooth as desired. It has an tremendous "wanna-have" factor, and the prices are not even that dramatic as I expected, like for example the Intel i9 versions. I think Intel ( Wintel ) will loose even more ground on the chip business, because there are no big reasons to buy large desktop workstations any longer, with such power in a small box. By Rosetta this supports ARM M1 and Intel x86 anyway, with good compatibility and at high performance, so I think Wintel / AMD will see a hard future. Of course you have to move from soft Win-Wonderland to the aluminium-hard Mac-World, which is a little disturbing as a user/developer for some weeks or months. But as always, some things I find annoying everyday, some things I love, but there is nothing which you couldn't get close to. Who's next PC will be a MacBook Pro Max, I'm curious ?

I was also sure that they have been "included", and also I got some for testing. My goal was to get started with 2 or 3 API's, to see how its going. Since I could not find much time for testing, I had to realize one day that my unused licenses had been expired. I've tried to check, to re-acivate the 1-year licenses, but they told me they were intended only for testing only, and once expired cannot prolonged for free. The license terms were always very fuzzy to me ( as usual with Embarcadero stuff ). If I wanted to prolong, I could get a 14-day trial, but thats maximum I could get, after that I should buy them. So I feel screwed a lot, and also I can only say: "Dont tocuh it". Better grab your REST-APIs directly, CDATA is not worth it under such "all-or-nothing" business model.

Why removing BPL parts which maybe cause unknown sideeffects, and risking an unstable IDE as a newly installed tool, while of course still complaining about any instabilities after installation, when closing or ignoring of the Welcome page is just one click in the IDE ( so a no-brainer ) ? 🤔 I would keep IDE as "natural" as is, while exploring its behaviour and stability over a certain time, before I try to remove or install anything harmful with yet unknown results.

Yeeees, HTML/CSS/JS has a really terrible High DPI support

This has changed completely. https://www.ideasawakened.com/post/customize-the-rad-studio-11-welcome-page-for-single-click-activations

Thanks for the insights. I'm wondering if this might cause any problem with memory leaks or AV, when creating/destroying frames at runtime, in changing, random order. If the Application->MainForm is used over several units, inside specific components only, this always leaves a bad taste. This leads me to the question what is the right, intended, official way to use the Application->MainForm and the AOwner of Frames/Components. Shall it be in a strict tree-structure, or does it not matter, to mix tree and direct owenerships as you like ? Does it matter if the relations were mixed by designtime and runtime ? Does FMX behaves differently than VCL in that regard ? Thanks god, the termination sequence on mobile is not that critical, since this is killed by phone mostly

Good question which is using what. https://docwiki.embarcadero.com/RADStudio/Alexandria/en/LLVM-based_Delphi_Compilers Seems that Macos is not yet LLVM, according to above list. But it is acc. to this info https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Delphi_Toolchains https://docwiki.embarcadero.com/RADStudio/Alexandria/en/DCCOSX64.EXE,_the_Delphi_Compiler_for_macOS_64-bit https://docwiki.embarcadero.com/RADStudio/Alexandria/en/DCCOSX64 https://static.webshopapp.com/shops/081736/files/088721693/embacadero-rad-studio-feature-matrixpd.pdf While I thought a long while that only D-Win32 is properitary compiler, and all the Rest is LLVM. Maybe it depends on language Delphi or C++ too. However, it compiles well, so it does its job for me