Page 1 of 1

Standard practice - desktop applications

Posted: Mon Mar 25, 2013 7:38 am
by Nakia
Hi,

I am about to start working on my first desktop application
and had a question regarding standard practices.

What is the standard way of creating another view as such.
For example the program preferences that usually open a smaller window
That sits over the main view..

Is this done by simply going to another card? And if so how do I keep the previous card
Disabled but visible in the background..

I have done mobile apps in the past so haven't had to do this before..
Sorry if this is a stupid question...

Re: Standard practice - desktop applications

Posted: Mon Mar 25, 2013 7:59 am
by snm
You must use separate stacks or substacks for each window.

Marek

Re: Standard practice - desktop applications

Posted: Mon Mar 25, 2013 1:49 pm
by Randy Hengst
I just use separate groups... optionsGroup, instructionsGroup, etc... and show an hide them on the card. As part of the call I set the level to top.

be well,
randy

Re: Standard practice - desktop applications

Posted: Mon Mar 25, 2013 3:18 pm
by snm
Randy,

As I understand, Nakia is asking about few windows displayed simultaneously, not changing views in one window.

Marek

Re: Standard practice - desktop applications

Posted: Mon Mar 25, 2013 5:46 pm
by jacque
Typically preference windows and other supplemental windows are substacks of the main stack, with their style set to modeless or palette. The user can put a modeless window behind the current stack, so if you really do want it to always float, use palette.

If you do not want the user to interact at all with the mainstack, use a modal window. Most operating systems are getting away from those though, they limit interaction very severely. Apple HIG now says that preference windows should be dynamic and reflect user changes immediately even while the window is still open.

Re: Standard practice - desktop applications

Posted: Tue Mar 26, 2013 12:22 am
by Nakia
Okay thanks for everyone help...