|
»
»
« Return to Thread: emit_stop_by_name
Re: emit_stop_by_name
by Steph Fox
::
Rate this Message:
Hi,
>> What exactly are you trying to do? - I ask because there may well be a
>> workaround in amongst the existing code base.
>>
>
> I was facing a situation similar to "tab key/field order problem" which
> you
> have helped to answer in Feb 2005:
> http://marc.theaimsgroup.com/?l=php-gtk-general&m=110962563019541&w=2
>
> As noted there, "the emit_stop_by_name is needed to prevent other handlers
> in the chain
> from handling the event (without it, the focus changes, but a tab gets
> inserted as well)"
What happens if you simply have the function/method return TRUE where you
would've called emit_stop? This should propagate, so long as it's an event
signal you're dealing with.
That technique seems to have been used successfully in place of both
emit_stop_by_name and its newer cousin throughout the GTK+ source, so
depending on the nature of the signal you're dealing with, it could be worth
a try.
- Steph
>
> Regards,
> /kksou
>
>
>
> --
> View this message in context:
> http://www.nabble.com/emit_stop_by_name-tf2513138.html#a7011790
> Sent from the Php - GTK - General mailing list archive at Nabble.com.
>
> --
> PHP-GTK General Mailing List (http://gtk.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
> __________ NOD32 1.1380 (20060125) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>
--
PHP-GTK General Mailing List (http://gtk.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
>> What exactly are you trying to do? - I ask because there may well be a
>> workaround in amongst the existing code base.
>>
>
> I was facing a situation similar to "tab key/field order problem" which
> you
> have helped to answer in Feb 2005:
> http://marc.theaimsgroup.com/?l=php-gtk-general&m=110962563019541&w=2
>
> As noted there, "the emit_stop_by_name is needed to prevent other handlers
> in the chain
> from handling the event (without it, the focus changes, but a tab gets
> inserted as well)"
What happens if you simply have the function/method return TRUE where you
would've called emit_stop? This should propagate, so long as it's an event
signal you're dealing with.
That technique seems to have been used successfully in place of both
emit_stop_by_name and its newer cousin throughout the GTK+ source, so
depending on the nature of the signal you're dealing with, it could be worth
a try.
- Steph
>
> Regards,
> /kksou
>
>
>
> --
> View this message in context:
> http://www.nabble.com/emit_stop_by_name-tf2513138.html#a7011790
> Sent from the Php - GTK - General mailing list archive at Nabble.com.
>
> --
> PHP-GTK General Mailing List (http://gtk.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
> __________ NOD32 1.1380 (20060125) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>
--
PHP-GTK General Mailing List (http://gtk.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
« Return to Thread: emit_stop_by_name
| Free embeddable forum powered by Nabble | Forum Help |
