Sherlock

@Dalija Prasnikar Huh, will give that a go, next time. Thanks

Have you really been able to debug on an iDevice running anything above iOS10?

1) Don't use it. Secondly: Don't use it like that. 😉

Don't worry, a lot of those AIs seem to pass the Turing test, because they are not....AIs, that is. Read here for more: https://ghostwork.info/

That was no "Oops", that was an "Aaaaaaarghh". For further explanation see this excerpt of the excellent Torch Song Trilogy

Delphi 10.3.2, XCode 10.3 (coincidence?) and MacOS 10.14.6 So, I was trying to update an old demo project to run with iOS 12. Last time it was successfully compiled and installed was with Tokyo and iOS 11. But today it is just giving me a really hard time with the strangest errors I never saw before (details below). So I started a minimal App to get get things rolling again, and this at least runs on the simulator, but not on my iPad. Another App, in constant development, does both perfectly fine, btw. And I already "turned it off and on again". With the new App I started from scratch, compilation is fine, but deployment results in: I found a TesterApp.app in my Macs scratch-dir so I decided to add it to my device manually, which gives me And there really is no info.plist, and no executable. It baffles me. I have no idea how to get those things into the App. Delphi should take care of that. As for the older App I'm trying to revive, compilation seems fine as well, but this is what I get when running it (F9) with Dev-Settings: Leaving me with a seemingly half finished .App file without an executable in my scratch-dir.Setting to Ad-hoc build gets even stranger messages in the IDE and still no executable: Any ideas?

Thanks, will give that a try and come back to you later today. As I said, it's an old Demo project, and time is pressing on the important ones....

We might have to readapt our priorities 😉

And the most reliable way to concentrate on creating the best product with a "no need to learn how to use" UI.

I beg to differ. Naming a property/function more explicitly for the sake of with is...how do I put this politely?...not helpful. Say I have a class TCar with properties Wheel and Engine and functions Drive and Park. If I understand you correctly you would expect me to call those properties and functions CarWheel, CarEngine, CarDrive and CarPark, to be explicit enough for the rare case when someone uses with on my TCar...

One compiler to rule them all and in darkness bind them...

I actually have not noticed that search thing yet 😄

Check out the "Language" part of that list...you should find "Formatting" very quick.

I'm guessing they are discussing to drop the with statement altogether once a new release is on the horizon, but chicken out in the last minute. So nothing is done to fix anything broken by with.

Aha, I understand. It would be more flexible if the IDE would stay on the monitor it was last seen on. OK. I have a rather static setup with my two monitors, so I don't have that issue.

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.