On Sat, Jul 6, 2019, 1:21 PM likage wrote:
> Thought I placed my files here as I could not really figure out the undo
> or the graph editor selection...
>
> main.py - https://pastebin.com/aQL9Fvue
>
Your scriptJob that tracks selection changes ends up calling your
plane_selected() function which
Thought I placed my files here as I could not really figure out the undo or
the graph editor selection...
main.py - https://pastebin.com/aQL9Fvue
refplanes.py - https://pastebin.com/zzKkFYxc
utils.py - https://pastebin.com/SXidXLTH
refplanes_ui.py - https://pastebin.com/qCGGqZEF
Appreciate in ad
On Sat, Jul 6, 2019, 12:26 PM likage wrote:
> Could you kindly elaborate more on `rename wasn't wrapped in an Undo
> group`? I am not quite understanding here...
> I did not create any 'groups' (cmds.undoInfo) if you are referring to
> that...
>
Yes that is what I meant (or through the API as we
Could you kindly elaborate more on `rename wasn't wrapped in an Undo
group`? I am not quite understanding here...
I did not create any 'groups' (cmds.undoInfo) if you are referring to
that...
And unfortunately, there seems to be another issue where - when trying to
select any keys in the Graph
On Sat, Jul 6, 2019, 10:14 AM likage wrote:
> Thank you Justin. Will try out your method.
> I have 2 questions here:
>
> 1. For the approach I have adopted - 'using scriptJob to track tool
> closure' , is that still applicable/advisable?
>
If it works, it works. Generally when it's your own UI y
Thank you Justin. Will try out your method.
I have 2 questions here:
1. For the approach I have adopted - 'using scriptJob to track tool
closure' , is that still applicable/advisable?
2. And one more question - For the `undo` that I have implemented, eg.
perform an un-renaming process, I notice
