For what it's worth, I've noticed that MG3 isn't very strict about xml definition at all. For example, I think that when you add values to your views, and then generate an event, the resulting XML has renamed your "value" tags to "name" tags:
<name name="someVar" value="foo"/> instead of <value name="someVar" value="foo"/> I would think this would be a problem, except MG appears to handle them just fine. If I had taken the time to pay close attention and verify this behavior, I would have reported it as a bug. (hence the bold & underline on "think") Adam On Thu, Oct 9, 2008 at 12:42 PM, cfCharlie <[EMAIL PROTECTED]> wrote: > > I had defined a couple of custom events and only one would work. No > major errors reported the application just ignored the second custom > event. Turns out that I had put the second custom event type > mistakenly after the closing tag </event-types> but oddly no errors > were being thrown because of XML tag violations etc... In my defense > it was one those "all-nighters"! So just in case you run into the same > thing, you've been warned. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 . -~----------~----~----~----~------~----~------~--~---
