Attila Kovacs

The other way around. Sometimes you just have to send the values you want to change and if you send a "null" for a field the servers clears it's value on the server side too.

I don't know, I don't think that it was in Seattle, as I said, it's not in Berlin. At least I can see now, that you can pass converters. I could not figure it out before, no time to check it now either. But it looks good, there are only two more things coming to my mind which is necessary to handle all kind of json rest services. -To be able to suppress the null values from the nullables (or a shouldmarshal callback/wallpaper) -To be able to send and receive pure arrays "[]" , some php api's are working that strange way Then it will be a really really nice allrounder.

@Delphi-Laie This is really cool man! A suggestion, don't know if it's possible, when the column count is reduced it should not shrink the window width but widen the columns. (Maybe some value would also fit in the columns.) PS: if you delete the "0" in the field "Rotation" the app AV's and dies.

TJsonDynamicContractResolver.SetTypeConverter Okay, everything clear now. This unit is based on the very same called in .net. But .net has nullable types and they also have: Well, and what do we have? Yet Another Useless Serializer. I'll stick with my modified REST.JsonReflect.pas where I can register converters and reverters on PTypeInfo base.

This is it. You don't have to. System.JSON.Serializers has a JsonConverter() attribute for it. You can even easily implement that only the fields which are - changed or not null or whatever - should be marshalled. Brrrrr. Looks like I was wrong on that. Looks like it's still a decorating-horror. I'll need more investigation on the code.

Either they forgot to ship System.Json.Serializers.pas for Berlin, or was not finished to the time, I've checked 2 installations and it's missing in both! I'm still fumbling around with REST.JsonReflect.pas I'm freaking out right now, the header says "Copyright(c) 2016-2018".

"but it is likely to work on several previous versions, probably XE7 or newer" I don't think so as I can't find System.JSON.Serializers under Berlin but under Tokyo. (Also lacks from the lib dir) Am I missing this from my installation or is it first appeared in the Tokyo release? Is it possible to decorate the custom nullable fields that this internal serializer/reverter can translate them? A one-time-registered type converter/reverter would be even better.

No, it's still present if a form takes more than 5 seconds to display. But that doesn't mean you have to make the main form as popup parent always (I guess). I would set it to the caller form.

Yes, or a small IDE expert could do it for you too.

Yes it's a bit annoying, they should fix that instead! 😉

There is. On the other hand, I like the way it is, I can have my object selected meanwhile changing units. Why on earth should the selection be cleared? On what occasion? Nonsense.

Rather not. It would unnecessary slow down changing between units. A lot. An unusable way lot.

what a coincidence, if you look at Remy's answer, you will get the idea.

It's a bogus message. Did you check the project search path? Also the root dir of the project.

project options search path

shift-f9 if it doesn't help, you have an older/different dbgrids.dcu in the search path fix the search path or remove the file and build the project (shift-f9)

@Angus Robertson Thanks for your work, I really appreciate it. A small remark, you left a bunch of: <DllSuffix>20</DllSuffix> 'es in the new project files. Should match the product version.

@Andrea Raimondi Interesting. One would think it would be a debugging horror and one could easily break a lot of things without compiler errors, but if you and your team are successful with that, then it must be ok. Anyway, I was really happy when I saw this post. Thread-safe and async, I'll add an UDP gateway to it and will try to set up some communication between client apps / services and between brokers on the LAN. Sounds fun!

@Remy Lebeau ah, right, I missed that part, I just read the title.

A TForm or descendant has an event OnClose. Thats it. No further interaction needed.

in OnClose Action := caFree;

@Andrea Raimondi At first sight this hocus-pocus has not much to do with System.Messaging at all and could be be easily create the same with this lib. By the way, what do you mean with Are you writing message driven apps? By the way 2 initialization begin MsgMgr := TMessageManager.DefaultManager; end; What is your purpose with begin/end? Is this also some readability thing?

I also have some issues with these clown selling-platforms. I wen't through the check-out 2 times but all they ask is a name, company name and an email address and no word about invoice or anything. Are you selling it only to private persons?

It's your font. It's completely different as my and I did not change it.

No, never, but I have to admit, the first thing I do after a Delphi install is to dump every fancy skinning (and other) bpl's from it.