Sherlock

Are those settings really not stored when you save the Debug Desktop?

Those pesky bots overrun our defenses constantly, but combined with the keen eyes of our members we valiantly keep fighting them off. TL;DR: Yepp, we're working on it though.

Considering Delphi is not the only product that can create iOS Apps, Apple will surely have not removed this functionality altogether. Just from looking at the Help you provided I think it is possible to upload our Apps (archives in Help lingo) from there. Maybe uploading wont take forever then? Seeing as that big ole Apploader was a laggy piece of software, it was just about time they overhauled it.

I have an FMX project that is mainly reading csv files and turns the numerical data into plots (more detailed: measurements over time, with 4 measurements per second). It has been performing "so so" for iOS which caused me to not leave beta phase. Windows performance is way better. That was 10.3.1. Now in 10.3.2 I see almost the same performance in the iOS simulator (still iOS 10.3 only, thought that was being fixed in this release), but on the real device (5th gen iPad) it is way, way slower. I will of course enter lots of stopwatches to check what exactly is costing time, but before that I just wanted to check if anyone else has noticed this as well. Cheers

Thanks, guys. I will give those hints a go.

OK, I finally got around to finding out what the problem is. turns out string comparisons got massively slower from 10.3.1 to 10.3.3 for iOS. Here is what I did approximately 6000 times: function QualityToInt(aQuality: string): ShortInt; begin if aQuality = rsPoor then Result := 0 else if aQuality = rsAcceptable then Result := 1 else if aQuality = rsGood then Result := 2 else Result := 0; end; Where rsPoor etc. are defined as resourcestring. This (plus some other stuff) took 100 seconds. Changing that to filling a TDictionary with the appropriate pairs once and doing a if not QualityDict.TryGetValue(aQuality, Result) then Result := 0; instead not only improved iOS performance (now 20 seconds) but the Windows version is noticeably faster too. So...granted the latter is better code. But still: What got broken along the way?

That is indeed a steep price. You should consider using external SSDs via USB3 to compensate for small built in drives. Saves you lots of money. Secondly don't buy it now because the next MacBook Pro is looming around the corner (Sep. 10th). That one wont be cheaper, but this one just might. Then for development purposes only a the smalles Mac suffices. Connect to it through LAN and have it sign your Apps, finished. You don't have to have an expensive MacBook just to develop Apps. Finally I don't expect more competence from the "Geniuses" or the common sales folk at the Apple store than from any other sakes guy at an electronics outlet like MediMarkt and such.

Do you have any numbers on that? Absolute or rough percentages.

The user folder from the Mac environment can be shared into the Windows user folder. Allowing for a more...seamless integration. This also means, that the windows user folder is not part of the VMs disk, it is outside of the VM. Regarding the "compile twice": On the first compile of a project I will always get: The second then works just fine. The cycle then repeats. It is possible to get around this issue by using folders local to the VM, but I prefer this, as it keeps the changes to the VM file at a minimum, which is good for backing up and creating memory saving snapshots.

In my opinion dumming down the security should not be the solution. I would rather say adios to those XP users, and the same to Win7 folks. It makes development so much easier, when you don't have to deal with outdated, discontinued and unsupported OSes.

Got the same setup, only with an older model (2015). No problems here. If you plan on developing for iOS, keep in mind, that you may keep your projects in the "Documents" folder from the Mac-share, but you'll have to compile twice. Every other compile will fail. I have no idea why, and no idea why it works the second time around. I'm just glad it does 😉

Have you tried reinstalling IDEFixPack after applying the patch?

Been using Delphi in a Parallels VM on a Mac for four years now. Now problems, no worries, no special settings. Only iOS compiles need to be done twice, because the compiler or the linker or whatever only likes the shared folders every other turn...

I wonder what folks will do that just paid money for their brand new Delphi and could not get it installed for almost a month. If that happened to me I would have wanted my money back, pronto. The good folks at Idera should consider renaming the thing to "NotGettinIt" O'Neill

All of those informations can be set manually with a multitude of tools, they are nothing to rely on.

I totally understand. That saying should always be delivered tongue in cheek.

There is a german saying: Kaum macht man es richtig,funktioniert es. It roughly translates to: As soon as you do it right, it works. It is all too true for most everything 😄

If it's too slow for you, buy a faster computer™

Off the top of my head: One is an integer the other is a floating point.

Compiler optimization Bug fixing Support for current versions of the supported OSes Finished. That is what I expect from 10.3.3. Looks like some of it is being done. So: Bravo. I really don't need new language features, but that's just old unflexible me. Then there's the trend to issue a major release early in a year and getting it fixed by the end of it, only to start the cycle again a couple of weeks later. That is tedious.

I second that!

Call tree sounds about right. But keep recursiveness in mind.

Mostly for myself, sometimes for the Ant men. This time as a moderate moderator.

Yours

@PeterPanettone Judging by the other answers and to get back to topic: No.