How to truely identify an item?

Hi,

I like the property grid but as far as I can see it lacks a way to truley identify an Item in the ValueChanged Event, without writing a workaround code, or have I missed something?

There is the Caption which in the example codes are used much as a Collection Key, but that is not a satisfying solution if writing multilanguge code. The Caption value will obviously change depending on langue used.

The only way I can see now is to create an Enum for the grid marking up each item in the tag property, but then you lose the posibility to store extra data. Although it feels like a more robust solution that the checking on the caption agains an language dependant string valiable.

Can we expect to see some improvements on this to the next version?

Sorry, I been away for a while...

This was one of the very first things I noticed after I had purshased the Xtream suite, and I sent in a feature request report on it, but never got any feedback on it... and then went on diving into the other parts of the suite to return later with more knowledge about it. Unfortunately, I found more knowledge didn't help

I hope my report was acknowledged after all and something is done about it to the next release, and I hope it's in good time before christmas or I can't release my own app and loose bucks

It would be a nice gesture by codejock to give some feedback when giving in a report as else you don't feel so motivated next time...

Yes that was good news, thanks, and when (approx.) can we expect to start enjoying this?

An other thing as well, I feel the constrains kind of suffer from the same problem, will they also have an ID or at least an index? A tag property would also be good as sometime you may like to filter the collection shown depending on something else, and then an index wouldn't be of much help as it wouldn't be consistent so you need to set a fixed value to check agains. The value as such is not always good to check against as it changes if your app is multilingual.

:-( I'm no big fan of workarounds, I like properly equipped controls.  I consider that part inconsistent as a combo box should have an index as minimum. There is a better workaround though, although it affect the appearance a bit, "enum" each constrain like "1-First Item", "2-Second Item" etc. and then read it iResult = Val(Left$(sConstraint,1) ), but this doesn't work currently as there is no way to checkthe identity of the Parent.

But ok, the good thing is I can prepare my code for this now - and have it work later