How To Prevent Recursive (Vicious Circle) Events

Thanks Bob for your efforts. I guess that although the events are all esse

ntially at the App/LayoutWindow/Doc level (and NOT PageItem), I could check the app.Selected array as someone here suggested.

Bob - do you know if/when Adobe plans to support PageItem-level events (aside from BEFORE/AFTER_PLACE which already works)?

AGain - thanks,

mlavie

Bob,

It is my understanding that only an App or LayoutWIndow is returned as a target, and not a PageItem, despite what the documentatation says. Am I wrong? And if I am wrong, I'd really appreciate an example of how to write the "addListener()" method for such a case.

Thanks - mlavie

This one would probably be better posted to the CS5 SDK forum!

The events you're listening for are somewhat generic - AFTER_SELECTION_ATTRIBUTE_CHANGED, for example, is fired for all sorts of things, not just the movement of a PageItem.

In your listener you'll have to put some conditions that check to see if you actually want to respond to the event. Now, if a page item moves, and then your listener moves it, you'll have a circular event loop no matter what. To solve that, you'll need to save some state information in the object itself, say with a label. Something like this should do it (not tested in any way).

public function listener( event: * ): void

     // decide if the event it something we want to handle   

     if ( event.target is TextFrame ) {

          var tf: TextFrame = event.target as TextFrame;

          var state: String = tf.extractLabel( "myMoveState" );

          // check to see if we moved it or the user did...

          if ( state == "WeMovedIt" ) {

               tf.insertLabel( "myMoveState", "WeDidNotMoveIt" );

          } else {

               tf.insertLabel( "myMoveState", "WeMovedIt" );

               functionThatMovesTheFrame( tf );

     }

}