Lars Fosdal

We use this model. Works quite well. https://nvie.com/posts/a-successful-git-branching-model/

We do that, but we can do that because our projects are inhouse and closely related, and we have control over the release and upgrade cycles, and we always upgrade all apps to using the latest 3rd party libs. But - if there are 10+ projects that are not really related, they would need repositories of their own, and the shared code would need to have a repository of its own. The question remains whether the shared code should always follow the latest version, or if you pin a version per project and upgrade on need only. The third party libs dependencies will be a challenge here - especially if there is a difference of version of the libs between the projects.

That I did not know. Thank you, Uwe!

As I understand, the APIs are bound at runtime, or am I mistaken? Can it be that your application tries to use an API that doesn't exist in a compatible form on SDK14 / S3? Edit: OR - the API is access restricted and you are not checking for the rights to access the API before use? Edit 2: I want to point out that all of the above are pure speculations on my part.

I agree. NULL = There is no list. Empty = There is a list, but it is empty.

One thing about component names is that you f.x. cannot dynamically add multiple identical frames to a form at runtime unless you ensure a unique name by doing something like this: type TOurFrameBase = class(TFrame) constructor Create(const AOwner: TWinControl); reintroduce; end; constructor TOurFrameBase.Create(const AOwner: TWinControl); begin inherited Create(TComponent(AOwner)); FPanel := AOwner; Parent := AOwner; Align := alClient; Name := ClassName + '_' + Seed.Next.ToString; // Ensure that every frame created gets a unique name I.e. we ensure a unique name for the frame instance. (Seed is a singleton for the class that delivers a unique (incrementing) cardinal (per app life time)). If you don't do this - you will run into duplicate name errors.

I don't mind the braces, TBH - but some of the expression operators still irk me, probably because I don't use them all day.

Sure, that and array[0..n] of Byte; are pretty common. Still, Byte sized variables and constants are used a lot in various APIs. Even nuggets like SizeOf(Byte); can be found sprinkled around the RTL and VCL, although I believe the universal result of that is 1.

AND watcher = currentUser() Add the above to the query

Avoid using short strings. Short string is for backwards compatibility only (typically for older desktop apps migrated to the new). They are ANSI based and do not support Unicode natively, and have been deprecated since 2009 when the Unicode string format was made king of the hill. Byte still is a useful number format when you don't need a large range,

There is also https://uberpdf.org/ by @Joe C. Hecht

foo(Copy(aValue, 1, 20));

That's a pretty impressive map component!

@Stano Did you try the actual navigation feature of it - i.e. goto?

True that, but it depends on the number of rows and if the control keeps the already fetched rows or discard them. I am used to working with tables where fetch all is not an option. Beyond a certain number - a search is a better option than a scroll bar.

That could imply potentially hundreds of queries to the DB while you drag?

Speaking of TChart - I wonder why TChart and DUnit isn't in GetIt instead of among the additional installation options?

Frequently, that turns out to be a myth.

Edit: No problem. I do that all the time 🙂

Odd. They show the same for me.

Ah, ok. Now I recall that incident. With XP no longer getting patches, I am not sure if that qualifies it as more stable?

The number of VS Code users is somewhat higher. About 14 million users in February 2021.

That is not a Windows 10 problem. That is a Kyocera printer driver problem.

Well, to my defense I also posted the native git command that in theory can be implemented in a plugin to the IDE 😉 I want to point out that I do not use multiple working directories for different versions of the same project. Always the same directory, but with the appropriate version checked out. With multiple working directories, it is so easy to accidentally pull up a file from the history list which refers to a file in the wrong directory for the version that you wanted to work on. That said, I can have multiple versions checked out to different folders when I do comparisons in Beyond Compare or VS Code - but I always use the same working folder when working on the code. Hence, I find it sufficient to let the git client show it to me.

Well, yeah, good luck with that.