There was a thread on this that was closed and although the OP seemed to resolve the issue I am not having such luck. I am essentially trying to do the same thing he was doing, wherein I have a scripted modifier plugin, and I need to access the object that the modifier is on. I have tried two approaches:
on create do
(
try
(
callbacks.addScript #postModifierAdded "nodeTransformMonitor node:(callbacks.notificationParam())[1] forwardTransformChangeMsgs:false" id:#splineOnGridAdded
)
catch
(
throw()
)
)--end on create
parameters main rollout:params
(
self type:#maxObject
)--end parameters
and any attempt to reference self.node comes back as no node property in undefined.
nodeTransformMonitor node:$ forwardTransformChangeMsgs:false
Trying this on a button pressed event with obviously the object selected yields the same result when trying to access self or self.node.
Am I missing something?
Thanks
What do want to know? Do you want to know the node (or nodes) which the scripted modifier applied to?
If so, you can ask for dependent nodes (refs.dependentnodes this) (see MXS help -> Dependencies -> refs.dependentNodes -> firstonly optional argument). Or you can use on attachedToNode event handler to store the node that the current plug-in instance is being attached to (see MXS help -> Scripted Plug-in Clauses for details).
Ah stupid me, using attachedToNode gave me the object when I needed it, and then I had to actually set self = nodeTransformMonitor node:obj forwardTransformChangeMsgs:false. Now it works. Thanks Denis
OK, now I’m running into a different issue altogether and I can’t seem to even hack it. My scripted modifier currently depends on other objects, it essentially draws a spline from object 1 to object 2, only using the verts from mesh 1 as knot points. This works very well save for the fact that I’m having trouble updating the thing.
In my scripted modifier there is a function that updates the spline, but it doesn’t run unless it’s called. I have tried using change events, but scripted plugins don’t like any clauses other than plugin clauses. So I tried using registerRedrawViewCallback which works great for one spline, but as soon as I add another one it seems like it wants to use the most recent one only. My understanding was that this callback would call the contents of the function and therefor they could share the same name. Also when I remove the modifier and remove the callback it’s still sitting there wanting to update.
What is the proper way to call an update function in a scripted modifier plugin that has dependent nodes?
Thanks guys
First of all I want to say that Viewport Redraw Callback Mechanism is very well documented in MXS Help. The Help gives good explanation how the callback works and illustrates it with good samples.
One of solutions in your case might be to register the function which calls another function, and change that another function on-fly when it needs:
fn redraw_fun = () -- is doing nothing
fn redraw_one = print "one"
fn redraw_two = print "two"
fn main_redrawviews = redraw_fun()
registerRedrawViewsCallback main_redrawviews
-- force to redraw...
-- change to 1
redraw_fun = redraw_one
-- force to redraw...
-- change to 2
redraw_fun = redraw_two
-- force to redraw...
in this case you don’t need to unregister the main (previously registered) function…
another solution might be to use when construct (probably geometry change)…
I would use when construct. Viewport Redraw Event will cause too many updates and memory leaking on script execution.