On 02/07/2018 at 06:05, xxxxxxxx wrote:
Hello,
great that you found a solution.
BaseList2D.GetData() only returns a copy of the internal container. So if you edit that copy you would have to set the data again with BaseList2D.SetData(). Alternatively one can - as you did - operate directly on the object.
best wishes,
Sebastian
On 02/07/2018 at 17:39, xxxxxxxx wrote:
Originally posted by xxxxxxxx
BaseList2D.GetData() only returns a copy of the internal container. So if you edit that copy you would have to set the data again with BaseList2D.SetData().
Thanks, S_Bach,
Always great to get around an issue, but much better to understand it.
While I've got your attention - I have another question... The plugin I'm working on will be accessing/affecting several axes of an articulated model. Not all axes are always active and/or present, depending on the state of the plugin or user project.
Is there a way to "grey out" some elements in a cycle button group? So that only the "active" ones are selectable? Or should I go a different way about it, and only populate the cycle button group with the active axes? It would be preferable for my use if I can have all axes always present, with only the active ones "selectable"...
On 02/07/2018 at 23:51, xxxxxxxx wrote:
Hello,
I don't think there is such a thing as "disabling" individual cycle elements. Typically one either disables a whole parameter or just fills the list with valid values. Depending on your type of plugin you could define what happens if the user selects an "invalid" value.
For further questions no longer related to this thread's topic please open a new thread.
best wishes,
Sebastian