http://twitpic.com/5oi0xq

Clicking on the “home” button calling screen main() results in the screen being loaded inside the tabSet instead of replacing the tabSet.

Submitted by Terje Pedersen on 11 July 2011 at 10:41

Is this new in 0.4.5?

It might been before aswell. I just added those buttons before I left work on friday.

The behavior has always been to load the screen in the inner-most visible screenContext. But I agree that we really need a way to specify where to load it. Here’s an idea. Every screen already has a few implicit arguments (such as animate). How about I add an extra argument target that can be either ‘_top’ (like HTML) to load the screen at the top level (entire screen), or another name specified using the screenContext menu.

For instance:

screen about() { … }
…
screenContext(“mycontext”) {
}
button(“About top”, onclick={
about(target=“_top”); // loads it full-screen
})
button(“About my context”, onclick={
about(target=“mycontext”); // loads it within the screenContext container
})
…

Similary, a tabSet would have a (custom?) name for its own screenContext.

@Zef Hemel: I would be very happy with this extra argument too. Hope it will be added in 0.5.0 and that 0.5.0 will be released soon :-)