|
|
Sample Programs from NeXSTEP 3.3
{\rtf0\ansi{\fonttbl\f2\fswiss Helvetica;\f1\fmodern Courier;}
\paperw11780
\paperh9540
\margl120
\margr120
{\colortbl\red0\green0\blue0;}
\pard\tx1140\tx2300\tx3440\tx4600\tx5760\tx6900\tx8060\tx9200\tx10360\tx11520\f2\b0\i0\ul0\fs36\fc0 Floating Panels
\fs28 \
\
\fs24 A panel should be allowed to float above standard windows only if it passes all of the following tests:\
\
\pard\tx240\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\fi-240\li240\fc0 � It's oriented to the mouse rather than the keyboard. Thus a panel that can become the key window should not be made a floating panel, unless it only becomes key when the user is ready to type.\
\
� It's important that the panel remain visible while the user works in the application's standard windows. This test is passed if the user must frequently move the cursor from a standard window to the panel and back again (e.g., a tool palette) or the panel gives information relevant to the user's actions in the standard window (e.g., some inspector panels).\
\
� It's small enough not to obscure much of what's behind it.\
\
� It doesn't persist (remain on-screen) when the application is deactivated.\
\pard\tx1140\tx2300\tx3440\tx4600\tx5760\tx6900\tx8060\tx9200\tx10360\tx11520\fc0 \
Thus, panels float for some of the same reasons that menus do.\
}
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.