Re: Re: Tk bind mouse down question

Thanks ... that's what I needed CanvasBind. Here's what I changed my code to ...

my $root = "BLAHBLAHBLAH";

$can->CanvasBind( '<Button>', [ \&my_test, $root ] );

MainLoop;

...

sub my_test {
    shift;    # don't know why I have to do this, but ...
    my $msg = shift;
    print "[$msg]\n";
}
[download]

Plankton: 1% Evil, 99% Hot Gas.

Comment on Re: Re: Tk bind mouse down question Download Code

Replies are listed 'Best First'.
Re: Re: Re: Tk bind mouse down question by graff (Chancellor) on Jun 02, 2004 at 01:58 UTC
`sub my_test { shift; # don't know why I have to do this, but ...` [download] You have to do that because when you bind a sub to an event, and that event occurs, the sub always gets the widget handle that received the event as its first arg. It's done this way so that you can bind a sub to a given even in all widgets of a given type (or any bunch of widgets that are supposed to invoke the same behavior), and when the bound sub actually gets called, you have the reference to the particular widget that received the event, just because that may come in handy in a variety of different cases.	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: Re: Tk bind mouse down question
by graff (Chancellor) on Jun 02, 2004 at 01:58 UTC

sub my_test {
    shift; # don't know why I have to do this, but ...
[download]

You have to do that because when you bind a sub to an event, and that event occurs, the sub always gets the widget handle that received the event as its first arg.

It's done this way so that you can bind a sub to a given even in all widgets of a given type (or any bunch of widgets that are supposed to invoke the same behavior), and when the bound sub actually gets called, you have the reference to the particular widget that received the event, just because that may come in handy in a variety of different cases.

[reply]
[d/l]