The BottomEdge component is decided to be available per Page, that means that it will be available if the Page is active. Now there can be situations when more than one BottomEdge will be available at a time, and the logic described above does not deal with that. Also, the edge tutorial does not seem to take into account the convergence: I guess it won't render across the entire screen then, only above the window chrome :)
For the phone case, I think shell should not even be involved, it's all about the app itself. Or maybe the only time the shell should be involved is when requesting a full screen view overlaying the app's surface. To be honest I do not see the reason to cover the indicator area, especially if we think the same logic should work on convergence, i.e window mode. So, my suggestions: 1) UITK will have the BottomEdge component 2) apps will know when the education view has to be launched and will do so per page, but a Tutorial framework (or component) should be provided, preferably by the shell 3) the Tutorial component will follow the position if the BottomEdge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1499845 Title: Expose whether an app has a visible BottomEdge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1499845/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
