Message 1 of 2
MLockMessage.setNodeLockQueryCallback : callback runs after the event
Not applicable
07-04-2008
01:37 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Maybe I just didn't understand what these callbacks are for.
I was expecting the registered callback would run before the actual execution of the event that triggered it, but it's running after.
For instance, if I try to delete a node, the callback would be triggered and would allow or deny the deletion of the node.
Well, it's a little more complicated that that but that's the overall idea.
Isn't that what the callbacks are for?
What I'm getting is the node gets deleted, then the callback run, and it run 4 times, evidenced by 4 sets of textual output.
I tried setting the callbacks via Python plugins as well as via the Python script editor (using the same API).
I haven't tried the C++ API yet.
Thanks
dado
I was expecting the registered callback would run before the actual execution of the event that triggered it, but it's running after.
For instance, if I try to delete a node, the callback would be triggered and would allow or deny the deletion of the node.
Well, it's a little more complicated that that but that's the overall idea.
Isn't that what the callbacks are for?
What I'm getting is the node gets deleted, then the callback run, and it run 4 times, evidenced by 4 sets of textual output.
I tried setting the callbacks via Python plugins as well as via the Python script editor (using the same API).
I haven't tried the C++ API yet.
Thanks
dado