Perhaps my use case calls for something more aptly named "event type groups" instead of "default event type". Again I'm left wondering: Why would I want a default event type?
I'll re-re-read the event types documentation as time permits and ponder this further. Bob Silverberg wrote: > Perhaps, but that might suggest that it cannot be overridden. By > calling it defaultType I think it better describes the behaviour, > which is "this is the default type(s) used if no type is specified in > the handler itself". > > > On Wed, May 20, 2009 at 10:21 AM, Doug Hughes <[email protected]> wrote: > >> If we're grouping events by type, then the attribute on event-handlers >> should not be default, but type. >> >> Doug Hughes, President >> Alagad Inc. >> [email protected] >> 888 Alagad4 (x300) >> Office: 919-550-0755 >> Fax: 888-248-7836 >> >> >> > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "model-glue" 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/model-glue?hl=en For more about Model-Glue, check http://www.model-glue.com . -~----------~----~----~----~------~----~------~--~---
