How do you like working with tonegodGUI?

@loopies said: I would prefer keeping the uids, even if they can only be set through a setter method, but, it wouldn't be a huge problem if they were totally removed. So feel free to change if you feel it's better.

I didn’t think the question was whether to keep them or not but whether to require them or not. At least my post was trying to help figure out if there is a use-case that prevents them from being optional, ie: required for all elements. I believe it’s provable that a UID is not required since the object reference itself is already a perfect UID.

Whether an optional String-based UID for some elements is convenient for some use-cases was not in question. (from me anyway)

@pspeed said: I didn't think the question was whether to keep them or not but whether to _require_ them or not. At least my post was trying to help figure out if there is a use-case that prevents them from being optional, ie: required for all elements. I believe it's provable that a UID is not required since the object reference itself is already a perfect UID.

Whether an optional String-based UID for some elements is convenient for some use-cases was not in question. (from me anyway)

Agreed… like you mentioned before, at a minimum, it will be very helpful when XML layouts are implemented. Guess it’s time to ask what people are using them for specifically.

I’ll chime in by saying I do use UID plenty of times to fetch instances of a control because they’re declared as method-local so I don’t end up with a class-global accessible instance to use. I guess this is a bad habit coming from Nifty. I could very well make all those controls that I reference class-global and be done with it.

@madjack said: I'll chime in by saying I do use UID plenty of times to fetch instances of a control because they're declared as method-local so I don't end up with a class-global accessible instance to use. I guess this is a bad habit coming from Nifty. I could very well make all those controls that I reference class-global and be done with it.

And again, you could always still optionally use UIDs in these cases. But all elements would not be required to have them. Kind of like JME uses the name field of Spatials.

Thanks for all the feedback and insight! I’ll be looking into to trying this some time soon I hope.

And thanks t0neg0d for building and supporting it so well!

1 Like

My points are:

1 - Nifty made me used to do it that way.
2 - I don’t care if it stays or not, that it’s optional or not because I still have an alternative either way.