Emulating a frame change "event" handler for 2.56

Noticed I could do this… thought Atom in particular may be interested. Emulate the event using a driver on an empty’s locX (arbitrary) which is driven by a keyframe in its locY (once again arbitrary). It seems as long as there is a keyframed action in the driver variables it fires every frame. The old_frame is kept as a global variable. Could be attached to any property on the actual object i suppose. I couldn’t think of a way to pass the array_index or something from the driver variables.
The Name of the object that you want the event for is passed.

Thinking could make a UI for it using some of the UI elements to select which property to attach it to and what object it’s for with self as default … just pondering.

Interested to hear your thoughts.

Thanks for posting the BLEND file.

This is very similar to the frameChange font copy scene I posted a sort while back. I do like the addition of the name space to simplify the driver call.

The main thing I ran into was that bpycontext.scene would fall out of scope on render. I notice you avoided using any reference to the current scene. This may work in some situations. I do want to give a further test. Currently I am on a Mac and can’t figure out where the print statements go
(Mac noob here).

I’ll try it out on Windows, later, when I can look at the output in the console.

It passes the current_frame of the current scene in the driver… Yeah i remember that thread. What really tweaked my interest was using globals to check if prop has changes works.

Cool script batFINGER.

Atom : Checkout Console.app for statements on OS X.

For 2.6 2.59 is there any class of drivers for which are easy to identify for failure.
Which ones tend to fail?
I started working with a simple operator template from the text editor samples
I have a driver that does something simple taking frame change into account.
I have not tested very much what I have.
It does work so far. 10 minutes.
I would like to know if something bad will eventually happen for any categories.

I had a recursion problem and fatal C library crash.
I had not saved my work
The second time I the typed a few lost statements to driver …
so far the second version has not crashed