VirtualTree from GetIt Package Manager is old and doesn't have the latest fixes from JAM-Software/Virtual-TreeView

[Coldzer0]

I would recommend using the https://github.com/JAM-Software/Virtual-TreeView
As the primary source of the VirtualTree components, it's still up to date and has many essential fixes, etc.

Thanks for your fantastic work. It is very informative and will help many Pascal devs.

[umbrageodotus]

@diversenok Updates?

[diversenok]

Well, ideally I want to make the code compatible with both versions, but I'm not entirely sure how to approach it. The last time I looked into it, there were some breaking changes between versions. The benefit of the revision published on Delphi's GetIt is that it rarely changes, meaning the dependency is effectively fixed and I can expect anybody who has it be able to compile the project. The GitHub repo is more volatile, and given that I cannot fix the dependency onto a specific version (it doesn't make sense to include it as a submodule), there is a higher chance of things breaking. It might require both me and people trying to compile the project to chase the latest versions and occasionally get mismatches.

But I'll revisit this topic to see what changes I need to make it compatible with the latest VirtualTrees.

[umbrageodotus]

@diversenok I'd say it does make sense to include it as a submodule.

[diversenok]

Hmm, maybe. In this case, the question becomes how should it work if the user already has another version installed? I can probably make Delphi prioritize the submodule for compile-time, but design-time requires package installation... Is it even possible to have multiple version of VirtualTree controls installed side-by-side in the IDE?

[c-michail]

My opionion is to add the submodule (aka latest version) from their github and support only that.
Supporting multiple versions of any 3rd party is a headache.

[umbrageodotus]

Agree with @c-michail