Sherlock

I've never used that before, but to me it looks pretty clear, that IsFirstInstance is not a stand-alone function but a class function of TogFirst. So when you want to use it, you must use it through its class (or in this case record): if TogFirst.IsFirstInstance then begin ShowMessage('Yay!'); end;

That looks like tedious work, how come that has not been done on the distributors side, or why is it undocumented?

The prefixes suggest that possibility very strongly

If that were the case we should at least be getting some decent burgers...

I can't stress enough, that it's only a hunch, that GExperts might be the culprit here. So, I installed Rio.1 on Wednesday and piled all the nice tools on to it. All seemed well. Now I started to use it more and get this AV every time I end it: At first I used the expert manager to disable all the other experts, but to no avail. Then I uninstalled GExperts (GXRS10.3-13C-experimental-twm-2018-12-22) and the AV is gone. It might be the mixture of experts, but it is a rather common one (I hope): GExperts CnPack Parnassus Bookmarks and Navigator MMX Explorer DDevExtensions All newest versions as of today. Could this have anything to do with GExperts? Or should I look somewhere else?

I should have thought of that myself! Thanks! It is not GExperts that has a problem here...it is FixInsight. Here is the call stack: So I should create a call there. Thanks for your help!

I would expect it to be the other way around. In general I would calculate one build per form factor. Unless the app is highly flexible size wise. So considering the very large Android biosphere as opposed to the three iphones + 4 or 5 iPads that's 8 iOS builds (tops, I don't build for iPhone and need only one iPad build) plus one macOS build. And you can get all those builds from the same XCode i.e. macOS machine. This is not even counting the version problem with Android. For iOS you currently have to develop for 3 versions to get more than 90% device coverage (https://david-smith.org/iosversionstats/). This also means you only need to create a 64Bit iOS 10 binary. For Android that is a bit more complicated (ignoring the Intel CPUs): You have 5 versions to consider viable for your customers (https://fossbytes.com/most-popular-android-versions-always-updated/). Frankly I don't know the Android build process, but it seems you have to consider a bit more than with iOS.

So...this is what my structure panel looks like... I know low contrast seems to be a cool thing these days, but this is ridiculous. After searching QP for a while I didn't find an existing issue for this and created one: https://quality.embarcadero.com/browse/RSP-23756 On a side note, the panel headers are very large and cost quite some space...sadly not configurable.

Yes, 10.3.1. I have restarted the IDE several time now, never got the effect again. On the other hand I discovered that the Layout is not stored. The panels left and right from the editor or form designer always start out way to narrow. This is costing me some nerves...

So...I don't know what happened. But from yesterday to now, it suddenly looks good. White font over dark gray background. I'll append my call. Weird. I actually just installed the new version of IDEFixPack...I'll try to get the older one to reproduce...

Well, now reality has arrived: https://www.heise.de/developer/meldung/Folge-der-Uebernahme-Idera-entlaesst-offenbar-viele-Travis-Mitarbeiter-4315673.html Or a taste of it in English: https://twitter.com/hashtag/TravisAlums?src=hash

This!

Ooooh, in that case: Rio is getting there. Seriously!

😄 Nah, AEG ceased to be AEG a long time ago.

Everything worked out fine. Took more than an hour, because after upgrading to 10.14, macOS discovered there is something called 10.14.3 available, and installing that took some time again. Delphi-wise I still can't use the 64Bit iOS-Simulators, but apart from that, everything is A-OK.

Please clarify: is this a VCL or FMX issue, or both? Because I can not reproduce for FMX.

I didn't go back far enough...sorry about that.

Sorry for the dumb question, but where should this path be changed? Searching the registry for Parnassus yielded icy shivers down my spine (the bookmarks are actually stored in the registry), but no path that looked anything like yours @Uwe Raabe Never mind, I got it. Thanks for the simple solution.

Can't reproduce with 10.3.1 for FMX.

Move to Rio for Mojave, it just behaves better. And concerning the 64Bit macOS Apps, just wait a little bit longer. I just did the jump to Rio yesterday, iOS Apps and macOS work just fine, at first and second glance. Mojave is up next for me today...wish me luck.

This is what mine looks like, but it is a fresh install (I kind of avoid the first major release...)

Those bugs still have a way better chance at getting fixed than "It's broke, fix it!" or no bug report at all.

That is actually the best way to get the problem ignored...ignoring it on the user side. I wonder which demi gods promoted their bug reports because there seems to be quite some fixing done. Keep in mind, that concise instructions to reproduce an issue may work wonders. They are our peers and great minds think alike. Good bug reports yield fixes. Yada yada yada...

Don't be scared. Actually this is a prime example use case for threads. Just follow the tutorials to get a feeling (http://docwiki.embarcadero.com/RADStudio/Rio/en/Using_the_Parallel_Programming_Library) and then dive right in. You may also want to check out the answers to this SO question: https://stackoverflow.com/questions/44080089/how-to-stop-a-running-ttask-thread-safe For a slightly different approach consider the classic http://docwiki.embarcadero.com/Libraries/Rio/en/System.Classes.TThread. And then of course there is always the OmniThread library, which I have not yet played with so far, but I hear only good things.

Stored Procedures? The work involved is the same. The DB can't guess what default value you prefer.