Sherlock

Pesky with overcome by wits.

I agree with @Rollo62. The TreeView is a bit cumbersome on mobile devices. I have sidetracked this issue for now. As soon as I come up with a solution I'll post it here.

Done..

@ihxPlease, explain what you mean. Is it safe to assume, you want the previous post deleted?

I get all the logging I need in the PAServer using the regular built in log.d. Just out of curiosity: Why the dylib? If it is your own, just compile it into your program and make it monolithic...the good old Delphi way.

Wouldn't it be easier to render everything on the client side and just transfer the data needed from the server? Some form of JSON should suffice. All controls and their states should be listed and you can build the form accordingly. The hardest part would be the communication between client and server.

Correct. Apparently I am still hung over and party mode wont shut off. Sorry about that.

@Dalija Prasnikar:The context was "simple test programs". No regular users around those...I hope.

So can the language be switched in the running application?

https://stackoverflow.com/questions/17158300/how-to-get-set-folder-type-in-c-sharp This should nudge you in the right direction, but it seems a bit...off putting.

When you edit your post, just place the cursor before the <OT> then press Backspace (<-) till the empty quote is gone.

You are aware of TStringLists DelimitedText property? StrList := TstringList.Create; StrList.Delimiter := ','; StrList.StrictDelimiter := True; AddValuesToList(StrList); CSVString := StrList.DelimitedText; // No trailing comma, no hassle, easy to read, not hard to explain..even 10 years from now Have not measured time on this yet, but unless you are processing strings in the millions, no worries.

This is very old, but should still be valid (at least the connection part): https://www.youtube.com/watch?v=zORe2voUHIU Please note that the prices may be outdated. And a first glance showed, they have an XE8 PAServer preinstalled, nothing newer.

For a start this should be right for you: https://www.macincloud.com/ Later on you may find that a Mac Mini for 900€ is not half bad. It can be put in some rack or closet and just host your PAServer, or you can use it work with and host a windows VM.

You probably mean VersionInsight and VersionInsight+ Sherlock

It is always good to try and be better than the hosting OS, and if the service is that vital, I'm sure you made risk assessments leading to counter measures for DLL-injection and the overall adverse effects of DLL-Hell. If you did it just because you could...I strongly advise to reconsider. But we are drifting away from the topic. Sorry for that.

Considering you'll have to compile all the DLLs with every new release anyway in order to avoid at least part of DLL-Hell I fullheartedly agree. Furthermore DLLs are quite a security issue: https://www.youtube.com/watch?v=HVigruKph74

https://cc.embarcadero.com/item/30870 Clearly the more, um, agreeable source.

We are a peculiar kind, that expects simple but prefers to do complicated.

Oh, thanks. I thought there was an article on FMXExpress. I'm sad to say I don't have time to inspect code that comes without any explanations regarding purpose, function or instructions. So I wont be looking into this, but thanks anyway.

Do you have a link for the original? Can't seem to find it on FMXExpress.com. Thanks.

OT: JSON is cool and all, but it also promotes dropping all kinds of junk in it without thinking. Well maybe a little: "Let the next guy take care of this" Sherlock

While I believe performance benefits to be true, I wonder how often this is checked and verified. The compiler team may indeed have sped up things in the more recent releases.

Correct! Luckily I have very few records and if I need a list of them I use generic lists and the readability is just fine. Edith also feels the need to mention I have no legacy code to deal with aside from Delphi (hahaha, small joke). So, of course Thomas' method is a very good and simple way to increase readability in such problematic code segments.

And I would identify the type behind @SomeArray[SomeStructure.SomeIndex] which you would have to do for that typed pointer you're using anyway and gotten a variable of that type. Making this just as readable without explicit use of pointers: Element := SomeArray[SomeStructure.SomeIndex]; Element.bla := 5; Element.blub := 10; // and 10 more lines like this I am very well aware, that there are pointers floating around behind the scenes all the time. But I prefer developing with a high level language also because I wont have to deal with them.