Trey Stout wrote:
> Well my most simplistic need for it is having JS pagination widgets at
> the top and bottom of a table. Both of them send a NEW_PAGE signal, but
> it would be nice for the table to just listen to any NEW_PAGE signal,
> not explicitly from one of the widgets.
>
> Anywhere you have duplicated control elements I could see this being an
> advantage.
true, although a global "listener" would not (IMHO) be the most
appropriate for that particular scenario, either. Provided you have a
reference to the table at the time you raise the signal, it's a simple
raising of the signal on the table:
signal("myTableId", "NEW_PAGE");
... should work no matter where you call it from, whether it's 2 or 10
different controls.
I agree that the converse isn't necessarily true, that is, a
hypothetical control may want to raise a signal to "anyone who cares"
(I think that's what one of the other posters mentioned). I could
potentially see this being both useful, and seriously abused. :P
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~----------~----~----~----~------~----~------~--~---
