Tommi Prami

In .dpr? Yes it does and that has been going on at least few versions now

Seems to me that is not very smart format/standard. If some service produce it and have to use it, then for sure need an parser. But I would steer away from that format if just can. Little bit sketchy. -Tee-

I like your expected Command Line syntax. -Tee-

Could you elaborate bit more? What this means in practise -Tee-

While was walking to work had couple of ideas on this, What if at FormActivate (For example) event of base form, I would do either. 1. Send message to window it self, If I've understood correctly window will not receive that message untill it has processed all the Form initializations of it self, and is able to recveive messages again. 2. Create and start timer and disable and free it on first tick. I think this is essentially same as the method 1. Some codes, me included, are not used to using windows messages too much. Delphi hides the need quite well. When the message arrives or timer fires set the flag that can be queried with other messsage from outside of the app. This should give pretty good starting point. -Tee-

It seems this can happen (On Form) quite common places. Not too many but still. Did not know any of this, Always thought that handle would be totally permanent on it's whole life time... -Tee-

Delayed initialization is an separate problem I think, and that can be handled Case by case, if needed. How, why and when Delphi will recreate the Hvnd for a Form? Never heard of this, this might explain rare weirdness. -Tee-

let's say if I have window Handle (Delphi app form), found by some windows API like FindWindow etc. Sometimes it seems that Window is created and has an handle but not fully functional yet. Is there a way to query with windows API that Delphi form is run all OnCreate etc events amnd is fully visible and all components are ready for user. Reason I as we use AutoIT to automatically test our Apps,, and sometimes Form is not ready yet. No fully visible or still runnin initialization events (OnCreate etc). If not I've suggested to add out base form class an message handler which we could use to quety, then problem would be how the Form it self Knows everything is OK, up and running 🙂 -Tee-

That is not all, there are also Embarcaderos inhouse fixes. -Tee-

https://en.wikipedia.org/wiki/Fast_inverse_square_root There was code samples long time ago for Delphi. With different constants, to spread error to positive , negative or +/- Also pure pascal version so routine could be inlined. It vas pretty fast Used in odl company. No need for me right now, but would be still cool to have it around and put into the Wiki and so on, also Delphi version of the code. -Tee-

That works also. -Tee-

If this works well would be nice if final code would be published in Github etc. I think many would need it and if there would be ready to run code, it would help community. -Tee-

Yo, Does anyone have 10.3.1 and 10.3.2 available? Would be cool to see some diff and/or analysis of RTL and/or VCL changes between the two, -Tee-

Hope all start to contribute. When the FastCode was alive and kicking I suggested some kind of online server where benchmark/validation app could post results. Now hosting such a thing would be way easier. This could be good new contribution, to start with https://github.com/davidberneda/FastDateTime (Not my code, just to be clear) -Tee-

Drop in placements of RTL and/or VCL routines would be most beneficial for most. And maybe something as a bonus that are not in the Delphi as a standard. Hope this project attracts lot of coders. -Tee-