Notifications do not propagate to an AppDelegate event handler

Nobody has claimed this yet.

I'm just starting to experiment with druid and ran into some confusion when trying to handle notifications within an AppDelegate event function. It appears the top-level window eats it after printing out a couple INFO logs.

After running into this issue I came across #1388 that lists a use case of implementing list selection via a notification. I'm attempting to have a Label widget from my list notify my AppDelegate that it's been selected. The delegate will then send commands to the label to change it's background color (and tell any previously selected label to unset its background). Eventually there will be more orchestration commands to different sections of UI.

The AppDelegate seems like a good place to put this orchestration logic. Is this lack of propagation intentional or an oversight?

Thanks for all the effort going into druid. I really like the composability of the various widgets and it feels well designed! Looking forward to watching it mature.

Start by tracing notification handling between the Label widget, the top-level window, and the AppDelegate event function. Determine whether the top-level window intentionally consumes notifications or whether they should reach the delegate; done means the propagation behavior and expected orchestration path are established.

Written by the indexing model from the issue text.