[codenameone-discussions] Re: LayeredLayout and interactive component issue
Please re-read my first response. It can if it's focusable but only one component in the hierarchy gets these events so it will block the functionality of the components within or be blocked by them. We have "lead component" to enable a lot of these use cases. -- 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 codenameone-discussions+unsubscr...@googlegroups.com. 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/0a6d2f41-e2b9-4e21-9bbb-56ed35065e5b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[codenameone-discussions] Re: LayeredLayout and interactive component issue
The complexity of the hierarchy has nothing to do with it. Overriding pointer events in a Container is generally problematic. -- 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 codenameone-discussions+unsubscr...@googlegroups.com. 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/b7a98887-3727-472c-8e6e-16f6705b2605%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[codenameone-discussions] Re: LayeredLayout and interactive component issue
No my hierarchy is pretty simple. Using the component inspector I have my form, that contains my parent container P1 (+ the toolbar) that itself contains the child component C1, that contains 3 components (its layer components). So I really don't get it. On Wednesday, August 8, 2018 at 6:30:10 AM UTC+2, Shai Almog wrote: > > A layered layout takes over all the space whereas flow layout will leave > some areas untouched. I'm guessing you have a different component within > the hierarchy that is grabbing events. > Notice you shouldn't handle events in a Container. It's problematic as > most events won't deliver to a container and instead go directly to the > applicable child. A better approach would be to bind an event listener on > the form in initComponent() and release it in deinitialize(). > > -- 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 codenameone-discussions+unsubscr...@googlegroups.com. 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/1f7b2257-45bb-4238-a518-e1b4a787ca09%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[codenameone-discussions] Re: LayeredLayout and interactive component issue
A layered layout takes over all the space whereas flow layout will leave some areas untouched. I'm guessing you have a different component within the hierarchy that is grabbing events. Notice you shouldn't handle events in a Container. It's problematic as most events won't deliver to a container and instead go directly to the applicable child. A better approach would be to bind an event listener on the form in initComponent() and release it in deinitialize(). -- 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 codenameone-discussions+unsubscr...@googlegroups.com. 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/5cb9b734-62b5-4ad1-9521-14197d26c392%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
