Open Stinkfist0 opened 11 years ago
Configuration wouldn't hurt I'd guess. Could be optionally implemented as tooltips.
I think if we are talking about EC editor UI capabilities it will get complex quick if everything is shown by default. What I'd like to see:
Sort by...
-> with name, id, attribute type (get all boolean attributes in a row, not mixed all around the attribute view, imo this should be the default not alphabetical ordering) etc.Most things here also apply to the scene struct window.
edit: I think tooltips in EC editor would be a bad idea. It would then constantly show a tooltip on top of ~everything and using the widget would get a lot more harder/unpleasant. More data columns might be a better idea.
@jonnenauha's ideas sound good. Don't know how well QtPropertyBrowser can be adjusted to our needs, so it might be convenient also to accomplish #637 while enhancing the EC Editor.
If we can get the QTreeWidget ptr or whatever its using we can modify the headers and install event filter for UI actions. But yeah sure making our own at some point would be ideal.
Would this be a toggleable option? Might be inconvenient if those are always shown, though they are very useful info.