Sherlock

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.

Awesome, but this sounds ominous. Could you please elaborate?

From a pure linguistic point of view: Where does the need for reintroducing a purely virtual aka non existent thing come from? There seems to be a need for this that is deep in the compiler. Would be a nice research project, or something the experts can explain.

Tokyo really is quake proof 😉

Not sure about the direction this question is actually heading, but does the structure view help?

Now, that would have been some nice information to begin the discussion.

Thanks and welcome!

But how?

There seems to be a tradeoff going on between VCL-flexibility and FMX-platform...ummm...style adaption. I'm pretty sure you might be able to achieve this with the style thingy, but I never quite understood that. Every time I try to use it, it just frustrates me and I end up building quick workarounds like this. Pretty sad. Does anyone have a nice tutorial for the FMX Style Designer?

Tried it, and this is what it looks like: To the edit I added this line of code to the OnChangeTracking Event: procedure TForm20.Edit1ChangeTracking(Sender: TObject); begin Rectangle1.Visible := Edit1.Text.Length > 5; end; That's it.