Thorsten, Yes, that is normal behavior I think - for invisible components we either wrap it in a container which receives the event, or let the page be the coordinator.
Invisible components also don’t receive clicks on links etc, so I think this was done to be consistent. Met vriendelijke groet, Kind regards, Bas Gooren Op 10 mei 2016 bij 19:48:48, Thorsten Schöning ([email protected]) schreef: Guten Tag Bas Gooren, am Dienstag, 10. Mai 2016 um 13:43 schrieben Sie: > This sounds like a good use-case for an event. Thanks for this hint, I totally forgot about it and decided to give it a try. There was a pitfall in my case, though: Component.canCallListenerInterface is asked before an event is dispatched and I'm starting with an invisible panel, so the method returns false, waiting for data to become visible, which is never dispatched... Doesn't seem to be mentioned in the docs or I must have missed it. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: [email protected] AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
