Sherlock

Aside from performance I have never considered pointers to be an improvement for readability, it's something that's messed up in my brain I guess. And the way it was taught back in the day: Calling it "pointer arithmetic" really did not help understanding the simple things that are going on there. Luckily there is no syntactical need for pointers in Delphi anymore. Been living free of ^ and @ for years now. Of course sometimes some API smuggles in PBytes or PChars, but its nicely encapsulated.

My 2Cents: Storing all kinds of (overall) useless information into the registry is a nuisance. It is like back in the day where everyone stored useless information into the win.ini increasing boot time severely. Which forced MS to up the game and introduce the registry. Of course, the registry is much more performant and flexible, but it still is actually something used by the OS for the OS. It is MSs fault to actually let all the hoodlums in and manipulate it. Nowadays reading and writing registry items can cost a noticeable amount of time. And considering that 90% of the applications that write into the registry don't bother deleting their entries at deinstallation time (at the latest), it is full of dead stuff (hence the registration cleaners, that tend to break stuff). So I applaud the idea to store size and position information into a simple, easy to find and delete, file.

Please consider RSS together with an appropriate App. For RSS details check this thread

As I have understood the licensing statements, the 10.2.3 CE will no longer be working, once the serial expires. As usual, I understood nothing...carry on.

I know how to populate a TListView, I just can't figure out how to collapse all entries for a header. Here is a mock up of what I mean: Clearer now?

In http://docwiki.embarcadero.com/RADStudio/Rio/en/What's_New see the chapter "Fix Pack improvements": So nothing connected to the compiler. Way to go that extra mile, EMBT.

Just gotta love those hi res pics 😄

Simple and great! Thanks for that.

Minor hint on that subject: That is what the heart in the lower right corner is for.

It works for Microsoft, why not for us?

I believe this is the most common problem in our line of work: not realizing what really is the problem. 😄

Guys? Topic? @David Schwartz I am a classic Delphi developer and I can't follow your step from Client/Server to ... well what, really? All I'm reading is that the Client no longer communicates with the database server directly, but via something like REST. So there is an extra layer added. But Multi Tier architectures have been around for quite some time, and Delphi copes just fine. Am I missing something? It still is Client/Server, only with 1 to n middle men. Of course you can toss all DB connectivity components, but who cares? Its just work, and that is what we are paid for. With every new layer between the Client and the rest (no pun intended), there comes change to the Client. As well as any change to that last layer will result in yet more changes to the Client. Again, just work. So what, in essence are you getting at? Does Visual Studio support total immersion of every tier into the IDE? Was that what this was about? If so, wow. Just wow. Gotta look into that sometime. But I would not build DLLs, and I would not use Delphi, nor C#. I would build Python modules that would be run in an Apache or whatever. Also work I know. But do you really want to put us out of work? 😉

Vai ce nebun ești! 😄

157 reports, looks like the product is being used. Nice! I chose to look at the world positively today.

Yes, please!

Oooh, bulk framewok importer... that sound like very useful tool I must have!

At least it is historically founded...

Well, sadly, for me this is expected behavior, and I switch off Error Insight altogether. It is a CPU-time consuming nuisance which (in serious projects) provides only false positives.

In my humble opinion, perfect (no hints, no warnings) projects can not be taken seriously, especially for testing. For testing you need (near) worst case projects like this. Sometimes it seems perfect projects is all the EMBT people work on, they seem to only work on those demos none of which exceed the 500 loc mark.

Hard to write a catchy title for this one. Sorry about that. So, here's the problem: I have a monitoring app, that is supposed to run 24/7 on a wired iPad in guided access mode, user interactions are a rare thing, it's about watching a live trace of heart rates and such. This has been working OK for the last couple of months. But recently I have received reports, that the iPads screen turns black after about an hour, and the iPad has to be manually "turned on" again. Then the app is back and everything is OK. This leads to two questions: Is anyone aware of changes in iOS auto lock behavior since iOS 12? Can an app trigger an event to make iOS think there has been user interaction and it should not lock the screen? Thanks

To answer part 1: It seems to be a known bug https://www.reddit.com/r/iOS12/comments/9ha20y/guided_access_forces_screen_to_autolock/ *sigh*

This.

I'll wait for the https version to come up. No need to jump to that forum any time soon anyway.

As always, there is the easy way and there is the hard way. Incidentally you can also call them the cheap way and the expensive way. And I'm talking short term, that is the only term modern management thinks in (Who cares about long term? I'll be retired by then, or in some other company). It takes no genius to find out which is the easy/cheap way and which is the hard/expensive way, now does it? So I'll be expecting 64Bit long before fixing those other problems, simply because it looks good on a feature matrix. And a good looking feature matrix is what gets customers. So I'll be on EMBTs side for this one, because more customers mean more money which in turn could mean more resources to fix the stuff under the hood. But it's good to keep reminding them of the faults in the tool.

It would seem that by not providing constructors/destructors/assign you would get the "old" behavior.