Scriptjob And Undo

[curiouskit]

Hi there,
I was tinkering with scriptJobs and ran into something with the undo queue that I dislike. The scriptJob basically waits for the context tool to change and do something based on what tool it changed to. The trouble is if I undo, it changes the context tool and goes forward... so everytime I change the context tool... I can't go further back in the list of undos. I hope this makes sense. Anyhow is there anyway to tell my scriptjob.. hey if this was done by undoing dont redo the scriptjob?

Thanks

[joojaa]

No! Or well yes you can read the undo queue, butthats hacky. THis said your entire workflow is hacky. Imean the context itself can say what to do in the nesxt step inwich case the undo would work right. Also its easier to just repackage the contexts in a different way so they notify of the change instead of the scriptjob.

Describe a bit more carefully, the scriptjonb is porbably teh 2nd wort way of doing this. Imena this is one of thsoe things that sound like the straightforward i need to do this slutions without thinking for a second.

[curiouskit]

Hiya,
I have a parent object that I want to have the translations done on (but its an invisible object) and a child object I want to have the rotations done on that is visible and the only object I want selectable. I dont want to clutter up the view with 2 control objects but I need to do the two things seperately.
I've never really worked with the context tools (or scriptJobs for that matter), what do you mean by

"Imean the context itself can say what to do in the nesxt step inwich case the undo would work right. Also its easier to just repackage the contexts in a different way so they notify of the change instead of the scriptjob."

Thanks for all your help!

[joojaa]

Ok so youve got a scrijob monitoring selection change then baseed on tool swithhes whats manipulated.

Dont do this its a bit tacky. Its one of those things everyone does just to abandon later. WHat you would be 99% of animators realy liking is adding 3 channels to the child (better one) that are linked to the parent just driven from its ancestor.

Fisrtof everyone can acces the parent manualy WITHOUT being able to se it, yes even stupid animators know this, namely thet you can traverse the hierachy with arrow keys. (Its porbably VERY common for them since they traverse bones thsiway far more than most riggers ever do)

But just in case you will have to bash your head here

Secondly you can use the show manipulator tool here easily... because every shape can specify what obejct is actualy manipulated wich does not need to be it.

3rd if you do need this use

undoInfo -stateWithoutFlush 0; //at the beginning of yourscriptjob
undoInfo -stateWithoutFlush 1; //at end

[curiouskit]

Hi there,
Thanks for all of your insight!