I was talking about events being handled at the top since they arrive from the canvas so I'm not wrong about that as that's literally the definition of lightweight implementation. Every implementation needs to go from root to child to find the child.
Sending events to every parent in the hierarchy has no valuable use case and can impact performance on large layouts. If you want to listen to an event or broadcast it you can do so easily. However, if we implemented something like that people will always pay the performance penalty whether they want to or not. Web isn't a lightweight framework. It's a great example of SLOW because of various decisions e.g. automatic reflow and generic events. This makes a lot of sense for a high level scripting language but not for performance. You wrote a lot but didn't mention a single programmer visible benefit for slowing everything considerably... Events go to the top most focusable component. You can disable focusability and use features such as lead component to implement typical use cases. If you are building a game where you need to handle complex event logic overriding the event handling at the form level makes the most sense anyway. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/codenameone-discussions. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/8fb0dc08-2f52-4b04-9586-a972aad793c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
