I just did a trunk update and now the TTreeView has an exposed Property of SHOWLINES that already exists in the Option properties.
Why are these being duplicated?
Do you understand how hard it is to manage this kind of riffraff?
So, the Property of SHOWLINES will show at Design time and Runtime whereas the Property of SHOWLINES in the options only shows at runtime, where is the value of this? I only need it to show at runtime and it looks ugly, btw.
There is already related issues like this in things like the combobox where duplicated Options verses single properties collide!
On top of this, the OP method requires only one entity in the LFM resource for the complete set of options, whereas the single properties require an entry for each.
And how about the other items like that, that exists in the OP property and also as a single entity?
I have no problem with using sets to crunch the code and file space, maybe I am special.
QA has been thrown out the window.
EDIT:
I see, just because its Delphi Compatible. So if Delphi jumped off a cliff, there are many that will follow?
I have no problem with removing items from the Option property, i know how to fix between releases.
But really, do we have to live with duplicating functions and try to ensure they don't collide ?