Studio 8.1.6 - page pane overtop existing objects

Doug Easterbrook doug at
Tue Nov 20 11:33:57 EST 2018

While it might seem complex,  moving into a paged pane is one of the right ways to do it.  hide and show of pane makes things really go away,     before, you were just putting something over top —  which doesn’t make them go away.

we frequently use a ‘scrollbox’ container and
- turn off the scroll boces
- use the same background as the parent 
- adjust the resize to be left, left/right, posnclient or what have you

which makes it effectively invisible

and we just drag our individual fields into the scrollbox making it quick and easy.

you don’t haveto chnage any other code, but it make hiding and show easy.

you can even take the scrollbox and put it in a page pane, tab pane and use it  for all sorts of gui resizing tricks.

highlyrecommended.  it willsave you lots ofcode and lots of time.

Doug Easterbrook
Arts Management Systems Ltd.
mailto:doug at
Phone (403) 650-1978

> On Nov 20, 2018, at 7:56 AM, Andrew Stolarz <stolarz at> wrote:
> Hello Everyone,
> I have a few particular windows with many entry fields, dropdowns etc in
> them. We also do a lot of things to those fields via notation.
> I need to have a second "tab" on this window without moving everything into
> a tab pane right now due to the complexities of this window.
> The quick fix/solution right now is to overlay a paged pane over the entire
> window for what I need and hide/show it as required.
> The problem is if users tab in this overlayed paged pane, the entry fields,
> dropdown fields etc behind the page page then come to the forefront. Is
> there any way to prevent this from happening? To me this seems like a UI
> bug, but wondering if anyone has dealt with this before? is using $enabled
> for every object the only workaround?
> Andrew
> _____________________________________________________________
> Manage your list subscriptions at
> Start a new message -> mailto:omnisdev-en at 

More information about the omnisdev-en mailing list