danni.coy Posted July 19, 2012 Share Posted July 19, 2012 Danni, Ok, now it's clear. That's a pretty sound idea, but I doubt we'll implement it in the current version of the editor. But we'll mind it for the future. For now, you can use non-modal Properties editor. Can I edit a instance of a property attached to a specific node using the properties editor? If not then I don't think that is going to work. Link to comment
manguste Posted July 19, 2012 Author Share Posted July 19, 2012 No, it's for per-property editing. Again, the most memory efficient approach in accordance with which such interface was designed is editing a property in Properties editor, while per-instance editing is to be used very rare, for 1-2 parameters, hence the modal window. Link to comment
danni.coy Posted July 19, 2012 Share Posted July 19, 2012 We use per-instance properties a lot. 1) storing persistant data and state information for WorldEpression Objects. 2) extending the node system without writing new node types in C++. 3) We produce a lot of different projects that have a common codebase. We use an instance of property to store job specific settings. I am open to suggestions on alternate ways of doing this. Link to comment
manguste Posted July 25, 2012 Author Share Posted July 25, 2012 Danni, Ok, that was convincing, added to the wish list :) Link to comment
steve3d Posted August 7, 2012 Share Posted August 7, 2012 ah... big announcements at late this summer, I suppose it should be after this years SIGGARPH, so, It's time to make the announcements ;) Link to comment
Recommended Posts