search

mgear-dev / mgear_dist

mGear v.3.x.x distribution repository
http://www.mgear-framework.com/
MIT License
184 stars 53 forks source link

Make guide / rig nodes unique #49

Open scroll opened 4 years ago

scroll commented 4 years ago

Feature description Currently, when building a rig from a guide, there are duplicate names in both the guide and rig hierarchies. Would it be possible for the built rig to have unique node names not clashing with the already existing guide?

Extra information Currently, we are working around this by using long names in our scripting, but we are wondering if that's at all possible without causing any other problems in the framework?

miquelcampos commented 4 years ago

Hi @scroll

Yep this is something that I was thinking about for version 4.0, I am afraid this will back-compatibility and will be not possible for 3.x

scroll commented 4 years ago

Awesome, thanks @miquelcampos .

miquelcampos commented 4 years ago

@scroll btw are you using long names on custom steps scripts? or are scripts that you run after the rig is built?

Because inside custom steps you can access any object or attribute of any component or previous custom step

ivogrig commented 4 years ago

I work with @scroll, you have a point @miquelcampos but the guide data is only given when the guide was built in the same go. It is probably a first world problem to say but it costs a lot of time when developing/iterating a post-script that relies onthe guide data.

I often rather save/reload a scene where the guide has aleady been built and then run only the post-script that I am working on, to save time.

I was wondering whether there could be a way to make that data persistent for that purpose. The dictionary could be stored as a string-attribute on the guide group.