stuck after a mpl_connect - how to disconnect and go on

Hi

thanks a lot for this feedback!

Your example is quite nice indeed. However there is something I may not
have fully understand.
If I use the example you sketch, I of course need to call the displayer
class (right?), by doing something like:

test = displayer()

However, then I hit the same problem again: I would need to define ALL
the commands I wish to go through WITHIN the displayer class (and more
precisely into the "show_next" function), because any command put after
the "test = displayer()" would be executed anyway without waiting that I
finally hit the right mouse button.

Or is there something I didn't catch which would allow me to go around this?

(what my program is supposed to do at the end is to go through a series
of (3xdataframes), and for each dataframe in turn, use the "offset"
trick, then reinitialise everything and start with the next series...
This seems to imply that I need to specify the full set of commands
within the displayer class show_next function)

thanks again

Eric

Hi Eric,

thanks a lot for this feedback!

Your example is quite nice indeed. However there is something I may not
have fully understand.
If I use the example you sketch, I of course need to call the displayer
class (right?), by doing something like:

test = displayer()

However, then I hit the same problem again: I would need to define ALL
the commands I wish to go through WITHIN the displayer class (and more
precisely into the "show_next" function), because any command put after
the "test = displayer()" would be executed anyway without waiting that I
finally hit the right mouse button.

I'm not sure why this is a problem. Yes, you need to put all your code
into the callback routines of displayer, but just think of it as
wrapping your program code inside the class. Your __main__ code then
simply becomes test = displayer()... and away you go.

Also, I realised shortly after sending my email that you can of course
do away with the offset class in this example, and put those methods
into the displayer class too, which will make things a little simpler.

Or is there something I didn't catch which would allow me to go around this?

(what my program is supposed to do at the end is to go through a series
of (3xdataframes), and for each dataframe in turn, use the "offset"
trick, then reinitialise everything and start with the next series...
This seems to imply that I need to specify the full set of commands
within the displayer class show_next function)

thanks again

Eric

Angus.

ยทยทยท

On 23/08/07, Eric Emsellem <emsellem@...419...> wrote:
--
AJC McMorland, PhD Student
Physiology, University of Auckland