roScreen is not compatible with standard components. Its a bit tricky to use both roScreen and the standard components in the same application. If the roScreen is on top of a standard component then there is no problem. Just invalidate it to return control to the component stack. But to place a standard component on top of an roScreen yields unpredictable results. You generally will use a liaison-facade or go-between to close (invalidate ) the roScreen and keep the channel from exiting. This could be an imagecanvas or paragraph screen. In any event there is a flickering between changing the two stacks. You see roScreen has its own window stack that is maintained apart from the component screen stacks. Would be nice if there was complete API control over things like the channel store that woukd circumvent their built in dialogs and allow 2D programmers to provide a complete 2d experience
My Channels: 2D API Framework Presentation: https://owner.roku.com/add/2M9LCVC
Updated: 11-11-2015 - Completed Keyboard interface
The Joel Channel ( Final Beta )