home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: WPS_PM
/
WPS_PM.zip
/
pc2v210.zip
/
PC2-1.faq
< prev
next >
Wrap
Text File
|
1999-07-01
|
34KB
|
657 lines
******************************************************************************
Frequently Asked Questions Part 1/3
PC/2 - Program Commander/2 Version 2.10 for
IBM OS/2 2.x, OS/2 WARP, WARP Srv. SMP Presentation Manager
Copyright (C) by Roman Stangl July, 1999
Version 2.10 Draft
******************************************************************************
Contents:
1.) How can I configure PC/2 to display the Popup Menu on the Desktop, using
a Mouse Button 1 or Mouse Button 3 singleclick instead of the default
doubleclick?
2.) PC/2 assumes that OS/2 is installed on drive C: , but I use drive H: !
3.) How do I add DOS Settings correctly?
4.) How can I add batch files?
5.) Is HPFS supported?
6.) How do I start a full-screen WIN-OS2 session?
7.) How do I control what mode and session type a Windows application runs
in?
8.) How do I start a VDM from an image?
9.) How do I start a VDM that boots from drive A: ?
10.) Why has PC/2 an option to shut down OS/2?
11.) How do I add commandline parameters at runtime?
12.) How do I install PC/2 as a replacement for the WPS?
13.) How do I add WPS Objects to start them via PC/2?
14.) How do I use Drag'n Drop?
15.) How can I add WPS Objects, and what WPS Object classes are allowed?
16.) Does PC/2 change to the root of all drives except for the working dir?
17.) Which versions of OS/2 are supported?
18.) How do I enable the Virtual Desktop and/or Sliding Focus?
19.) How does the sliding Focus work?
20.) How do I use the enabled Virtual Desktop?
21.) How does the Virtual Desktop work?
22.) How do I start applications on the Virtual Desktop?
23.) What's the name of the Desktop?
24.) What's the name of the Window List?
25.) What about seamless WIN-OS2 support, without a corresponding WPS object?
26.) How many applications can I start within a seamless WIN-OS2 session?
27.) How do I define a program's priority?
28.) How do I define a Hotkey to switch to a session?
29.) How does the Hotkey feature work?
30.) Why should I use the Hotkey feature?
31.) I have defined some Hotkeys - now these keys are not available on other
32.) I switched to an application - now some keys don't work as when not
running PC/2!
33.) I defined a Hotkey but the wrong window is activated!
34.) How to I define a Hotkey for a certain window (e.g. Drive C object)
even if it wasn't started from PC/2?
35.) Do I need to completely fill in the Program Installation dialog to
define a new Hotkey?
36.) I have 2 OS/2 windows with the same name. Will the Hotkey work?
37.) How do I access the Window List on PM?
38.) What is the feature "Button 2 Titlebar click lowers Z-order" useful for?
39.) Can a Hotkey defined for PC/2 itself?
40.) When switching to a Virtual Desktop with a Hotkey, how is the window
aligned?
Questions, Answers:
1.) How can I configure PC/2 to display the Popup Menu on the Desktop, using
a Mouse Button 1 or Mouse Button 3 singleclick instead of the default
doubleclick?
First, you may select the Configure Desktop dialog on the Popup Menu to
select the type of default mouse click action. This information is
written to the PC2.INI profile.
Second, use the commandline option "-SingleClick" or "/SingleClick" to
overwrite the default behavior read from PC2.INI. If you run PC/2
as a WPS replacement, you can't use any commandline option, since
OS/2 seems to dislike commandline options on programs run as the WPS.
However, this doesn't prevent you from setting the default behavior using
the Configure Desktop dialog.
2.) PC/2 assumes that OS/2 is installed on drive C: , but I use drive H: !
Either start with a blank Menu and add your programs, or use an editor
such as EPM.EXE to change all " C: " occurrences to " H: " in the
profile.
The profile is named PC2.CFG by default.
3.) How do I add DOS Settings correctly?
If you wish to do this using your text editor, ensure you use the
exact same spelling as found in the settings of a typical DOS
program. They have usually ON/OFF or numbers as possible
selections. For ON/OFF, you add =1 or =0 to the setting, e.g.
HW_TIMER=1. For numbers, add =xxxx, e.g. EMS_MEMORY_LIMIT=1024 or
DOS_VERSION=DOSPROG.EXE,5,0,255. But the really easy way to do this
is to use the standard DOS Settings dialog, which is displayed when
you click on the DOS Settings pushbutton.
4.) How can I add batch files?
Batch files aren't executable files, so they need a command
processor to interpret them. Therefore, you have to select a
command processor, (e.g. CMD.EXE) and add /C filename.bat or /C
filename.cmd to the parameters entry field. You may wish to look at
the command reference of CMD.EXE and COMMAND.COM for more details.
If you use the standard file dialog to find the batch file you want
to add, PC/2 automatically add this batch file as an argument to the
command processor.
5.) Is HPFS supported?
Yes, PC/2 fully supports HPFS. However, if a filename contains spaces,
you have to place it in double-quotes, e.g. at a command prompt you
would type DIR "[d]\OS!2 2.0 Desktop\*" /s to list all files of the
Desktop directory. The same is true for PC/2, e.g. if you want to start
a batchfile that conforms to HPFS-filename conventions, you may create
an entry like this : (Note: Replace [d] with a drive letter, e.g. E: )
Program Title: HPFS-Test
Path and Filename: [d]\OS!2 2.0 Desktop\Prompts\Command Processor.exe
Working Directory: [d]\OS!2 User Applications
Parameters: /C ""[d]\OS!2 2.0 Desktop\Run Me.cmd""
Note: Passing HPFS-filenames to command processors may require two
double-quotes (e.g. CMD.EXE does). Also take a look at the help pages
for CMD.EXE to get more details. Open up an OS/2 command line prompt, and
enter: help cmd.exe - this should get you to the right section.
6.) How do I start a full-screen WIN-OS2 session?
The easiest way is to select the Session type of Fullscreen WIN-OS2 and
specifying the WIN-OS2 executable on the Application notebook page in the
Program Installation dialog.
Alternatively create a full-screen DOS command prompt that uses
WINOS2.COM as the executable's name. (e.g. [d]\OS2\MDOS\WINOS2\WINOS2.COM
where [d] is the drive letter you installed WIN-OS2 onto, e.g. C: ).
Then add the required DOS Settings (e.g. the following settings greatly
improve performance on a 8514/A adapter and probably on other adapters
too (thanks to Timothy Sipples for them!):
VIDEO_8514_XGA_IOTRAP=0
VIDEO_RETRACE_EMULATION=0
VIDEO_SWITCH_NOTIFICATION=1
XMS=64
EMS=0
DPMI=4 (or more than 4, if you run a lot of Win apps)
HW_ROM_TO_RAM=1
IDLE_SECONDS=2
IDLE_SENSITIVITY=100
SESSION_PRIORITY=32 (for WARP only)
However, modern hardware should be fast enough so that I suggest you to
start with the following values instead:
IDLE_SECONDS=1
IDLE_SENSITIVITY=95
SESSION_PRIORITY=1 (for WARP only)
7.) How do I control what mode and session type a Windows application runs
in?
Just enter the application's data and select the mode the seamless
WIN-OS2 session should run. This includes realmode, standard or
enhanced 386 mode, both in separate sessions or in a common VDM.
Of course you may select a fullscreen WIN-OS2 session.
Caution! Sliding Focus does not work well, when running seamless
WIN-OS2 sessions. To temporarily suspend Sliding, just hold
down the SHIFT key while moving the mouse.
8.) How do I start a VDM from an image?
First create the image, then create an entry of a fullscreen or windowed
DOS session. Then add to the DOS settings:
DOS_STARTUP_DRIVE=[path]DISK.IMG
where [path]DISK.IMG is the path and filename of the image you want to
start. Caution! On OS/2 2.0 (2.0 GA) it doesn't work; I don't know why.
9.) How do I start a VDM that boots from drive A: ?
Same as item 8.) says, only adjust the DOS settings to:
DOS_STARTUP_DRIVE=A:
Caution! On OS/2 2.0 (2.0 GA) the system traps, I don't know why.
10.) Why has PC/2 an option to shut down OS/2?
Some people use PC/2 as a replacement for the WorkPlace Shell (this saves
up to 4 MB memory!) and they can't click with button 2 to get the WPS
Popup Menu, from where shutdown is usually selected. So, it is provided
on PC/2's Popup Menu. PC/2 requests OS/2 to clear all file buffers. After
all disk activity has been stopped, it is safe to power off your system.
PC/2 don't close the programs, but after the disk activity has stopped,
all processes are frozen (you can not switch to or select programs
anymore).
If you set up "Normal Shutdown" in the PC/2 Desktop Menu, when you click
Shutdown OS/2 on the PC/2 Popup Menu, PC/2 will act just as the WPS does,
when doing a normal shutdown. In other words, apps are notified they are
about to be shut down, and, depending on the application, you may get
several questions asking something to the effect "Do you really want to
do this?"
11.) How do I add commandline parameters at runtime?
E.g. assume you created a Menuentry that starts the editor EPM.EXE.
After you selected EPM, just before it is started, you can request
a dialog box from PC/2, where you can enter any commandline parameter
by adding a [...] construct in the parameters entryfield of the Program
Installation dialog. This work similar to the same WPS feature.
12.) How do I install PC/2 as a replacement for the WPS?
First, install PC/2 in the normal way. Second, edit your CONFIG.SYS to
replace the statement (Note: substitute your drive name instead of
[d], e.g. C: ):
SET RUNWORKPLACE=[d]\OS2\PMSHELL.EXE
to
REM * SET RUNWORKPLACE=[d]\OS2\PMSHELL.EXE
SET RUNWORKPLACE=[d]\path\PC2.EXE
or
REM * SET RUNWORKPLACE=[d]\OS2\PMSHELL.EXE
SET RUNWORKPLACE=\path\PC2.EXE
Where [d]\path is the drive and path (e.g. \PMAPPS\PC2 on drive C: )
where you installed PC/2. (The second method can be used to add
PC/2 as the Workplace process of a maintenance partition, e.g.
created by the BOOTOS2 package). Second, ensure that all PC/2
*.DLLs are in the directory PC/2 is running from, or in a path
pointed to by the LIBPATH environment variable in your CONFIG.SYS.
The next time you boot, the WPS will not be loaded (you can verify this
by a blank screen displayed instead of the normal Desktop and objects.
Not using the WPS saves memory and reduces boot time! However, you will
not be able to change your system settings you are able when running the
WPS. Also, if you install applications that create WPS object, these
objects won't be installed and the installation may fail.
Of course, you can also start the WPS later, either by starting
PMSHELL.EXE from a command prompt or from a PMSHELL Menuitem of PC/2.
You can follow the WPS initialization by heavy disk access and buildup
of your Desktop with objects. Once the WPS is running again, you can
change your system settings and installation programs will be able
to create WPS objects.
To allow you to use the Popup Menu on the newly (re)started WPS, PC/2
will detect this change immediately if you have correctly specified the
name of the WPS (e.g. Desktop, Arbeitsoberfläche,...). PC/2 displays the
Window List on PM additionally, just as the WPS does by clicking mouse
buttons 1 and 2 together.
13.) How do I add WPS Objects to start them via PC/2?
The important thing is, that you have to know the WPS Object ID
(Identifier) to be able to add them to PC/2. For preinstalled Objects,
you can find the ID in the file [d]\OS2\OS2_20.RC (where [d] is the
drive you installed OS/2 onto, e.g. C: ).
Alternatively, you may use WPS 2 PC/2 to extract the Object ID from
WPS Objects not being Folders or Program Objects, when available.
The ID of Objects, created as outlined above, may than be added in the
entryfield Path and Filename in the Program Installation dialog, with
the Program Type WPS Object.
Note that this function is not supported when PC/2 is used as the
replacement for the WPS, as it is the WPS that services starting
the Object ID's.
14.) How do I use Drag'n Drop?
In addition to the standard file dialog, you may use Drag'n Drop to
add applications in the Program Installation dialog. E.g. you may
use a drive object, select one (only 1!) application, and then drag
it into the dialog and drop it onto any area that accepts it (any area
that isn't covered by text, buttons, entryfields,...).
You can also drag one WPS Folder Object onto the first page of the
Program Installation dialog, to open it when selecting it from the
Popup Menu.
PC/2 will try to determine the type of the application you added
automatically (programs or folders), but you can still change it.
15.) How can I add WPS Objects, and what WPS Object classes are allowed?
The simplest way is to use WPS 2 PC/2. Just drag the WPS Objects you
want to add to PC/2's Popup Menu, onto the WPS *icon* of WPS 2 PC/2
(Not the open WPS 2 PC/2 application).
Then open the WPS 2 PC/2 application window by clicking on the icon
mentioned before. Now drag the status bitmap (the full suitcase) from
WPS 2 PC/2 onto the Setup dialog of PC/2, and voila, for each WPS
Object extracted, a new Menuentry is created within PC/2's Popup Menu.
WPS 2 PC/2 can extract data from WPS Objects of classes WPProgram,
WPFolder, any WPS Object that has an Object ID defined, or WPShadow
Objects of the classes mentioned previously.
E.g. you can't extract your WPS Printer Object, or a Drive Object,
unless an Object ID is assigned to these Objects.
Note: When running PC/2 as a replacement shell for the WPS, these
functions are inoperative, as they require the WPS to service them.
16.) Does PC/2 change to the root of all drives except for the working dir?
Yes, PC/2 changes to the root of all non-removable drives before the
selected application is started.
17.) Which versions of OS/2 are supported?
PC/2 was developed under OS/2 2.1 GA, 2.11 GA, and WARP GA, but I would
expect it to work under OS/2 2.0 and any Service Level too.
Under OS/2 WARP for Windows, using a tiled background bitmap hangs OS/2
solidly, requiring a reboot.
Under OS/2 WARP Fullpack, using a tiled background bitmap just hangs
PC/2, so in this case, just use CTRL+ESC to terminate PC/2. A defect
(PMR 4X472) has been opened against OS/2 WARP, so a future CSD
(Corrective Service Diskette) will hopefully repair this defect.
This bug is not a PC/2 problem, since selecting a tiled background
bitmap works correctly under OS/2 2.x.
Unfortunately this bug has not been removed for OS/2 WARP 4 also.
18.) How do I enable the Virtual Desktop and/or Sliding Focus?
Start PC/2, click on the Desktop and select SETUP Desktop. A dialog box
will appear, where you can enable these features. Just press help for
further information.
To temporarily suspend the Sliding feature, just hold down the SHIFT key
while moving the mouse.
Caution! Sliding Focus does not work well, when running seamless
WIN-OS2 sessions. To temporarily suspend Sliding, just hold
down the SHIFT key while moving the mouse.
19.) How does the sliding Focus work?
For all pointer movements, OS/2 generates messages that contain the
window where the message originated. PC/2 hooks into these messages
and determines the active window. If the active window is not the
window that originated the message, it makes the message originating
window active.
Of course, PC/2's window, the Desktop and the window list are treated
differently. To preserve the Z-order of the windows, also check this
option.
Caution! Sliding Focus does not work well, when running seamless
WIN-OS2 sessions. To temporarily suspend Sliding, just hold
down the SHIFT key while moving the mouse.
20.) How do I use the enabled Virtual Desktop?
You may know that a VGA-display has usually 640 columns and 480
rows (numbered from 0...639 and 0...479). If you position your mouse
pointer over the surrounding rows and/or columns of your display
(here columns 0 or 639 and/or rows 0 or 479) PC/2 SHIFTs all windows
that exist on your system (with some exceptions like window list) in
the opposite direction. Some windows may slide out, some may slide in
from the other direction.
You may click on any Virtual Desktop on the overview Window to
immediately switch to that Virtual Desktop.
21.) How does the Virtual Desktop work?
First, for all windows, OS/2 tracks their coordinates in data structures.
PC/2 queries and adjusts them according to the mouse movements the
user makes. For instance, if the mouse pointer is over column 0 on the
screen, PC/2 adds to the x-position of all windows for example 50 % of
the x-dimension of the screen. The windows appear to move rightward (out
of the display) because the display SHIFTs leftward within the Virtual
Desktop. Because windows are usually aligned on byte-boundaries, they
may not appear on their original place if you SHIFT one unit in one
direction and one unit in the opposite direction.
22.) How do I start applications on the Virtual Desktop?
In the Program Installation dialog, you can define the size and
position that the application should use. For instance, you can enter
a position of -200 in X, which would position the application to the left
of your Physical Desktop. All coordinates are in relation to your
Physical Desktop. In other words, an x setting of -1 would position your
application 1 pixel (out of a possible 640 in VGA) to the left off of your
Physical Desktop.
PC/2 forces the window to the position you entered, however the
application may determine its size itself. To allow PC/2 to find the
window, ensure that you enter the applications Window List entry or
titlebar text to the Window Name entryfield on the Hotkey notebook page
of the Program Installation dialog. You don't need to enter the complete
Window List or titlebar text or window class name, just any substring that
matches with the text. Use the Spy notebook page in the Desktop dialog to
determine this data easily.
*However*, you must ensure that this substring matches *only* with the
application you want. Results are unpredictable if multiple applications
contain the same substring. For example you may find that a window is not
kept on every Virtual Desktop if you would like to, or a window may be
kept on every Virtual Desktop while you can't explain why.
Some applications are "stubborn", that is, no matter what you do to
specify your xy coordinate position for the application, it refuses to
obey, and starts where it wishes. For instance, a OS/2 or DOS windowed
session that changes from 80x25 line mode to 80x28 line mode during
startup causes just such a condition (even if they would honor the
requested position when no mode change is done).
23.) What's the name of the Desktop?
OS/2 2.0 introduced the name "OS/2 2.0 Desktop" for the Desktop window,
which normally is the WPS. OS/2 2.1 and OS/2 WARP use the name
"Desktop" instead, if you install it over a newly formatted system.
OS/2 2.1 and WARP may use a different name, if you install it over a
previous OS/2 system, so please read the README file provided with your
version of OS/2 carefully.
If you use a non English OS/2 version, you have to translate the Desktop
window's name to your national language, for example you would enter
"Arbeitsoberfläche" when running a German OS/2. You may extract the
exact spelling from either the Window List (where the Desktop is one of
the running programs) or from OS/2's User's Guide.
PC/2 requires the exact spelling of the Desktop window's name to locate
the WPS process under all running processes.
Most easily, just use the Spy notebook page to find out the names of the
Desktop (WPS) and Window List!
24.) What's the name of the Window List?
The Window List (known as Task List in OS/2 1.x) is just named
"Window List".
If you use a non English OS/2 version, you have to translate the Window
List's name to your national language, for example you would enter
"Fensterliste" when running a German OS/2. You may extract the extract
exact spelling from either the Window List itself or from OS/2's User's
Guide.
PC/2 requires the exact spelling of the Window List's name to locate the
Window List under all applications.
Most easily, just use the Spy notebook page to find out the names of the
Desktop (WPS) and Window List!
25.) What about seamless WIN-OS2 support, without a corresponding WPS object?
PC/2 allows you to start seamless WIN-OS2 sessions, as separate sessions
or in a common VDM. This means, if you start a Windows application in a
separate session, a complete copy of the WIN-OS2 environment will come up.
This wastes memory, so I suggest to start Windows applications into a
common VDM whenever possible.
This seamless WIN-OS2 support works also without the WPS installed,
under OS/2 2.1 GA with no problems, but OS/2 2.0 GA hangs during load.
So under OS/2 2.0 GA, only start seamless WIN-OS2 sessions if the WPS is
running.
Under OS/2 2.0 GA you can only successfully start WIN-OS2 sessions in
standard mode. 386 enhanced mode is not supported by OS/2, and real mode
starts to load, but doesn't complete successfully for unknown reasons.
Under OS/2 2.1 and WARP, real mode is not supported, so you can only start
Standard mode and 386 Enhanced mode sessions.
26.) How many applications can I start within a seamless WIN-OS2 session?
For a separate session usually only 1, but you may start the Windows
Program Manager as the first, and any Windows applications as a
commandline parameter, which the Program Manager will start for you.
If you start the Program Manager, you can of course start any Windows
application from it, but make sure that you have enough storage defined
in the DOS Settings (usually DPMI_MEMORY_LIMIT=16 or so).
For separate sessions, the limit is determined by your system
configuration (e.g. how much memory you have in your kingdom. <smile> ).
27.) How do I define a program's priority?
Just select the last notebook page from the Program Installation dialog.
Warning - changing a program's priority may have severe impacts on your
system's performance, giving all CPU time to the application.
You may set a tape backup or image conversion program to a lower priority
or a real-time data acquisition to a higher priority.
For DOS sessions (and WIN-OS2 sessions are DOS sessions), the priority
can't be changed, because this would lock PM for unknown reasons.
You can't change the priority of WPS Object either, because the WPS
actually starts them after a request from PC/2.
On OS/2 Warp, you can adjust the priority of DOS sessions via the DOS
Settings dialog, in the Settings Notebook.
28.) How do I define a Hotkey to switch to a session?
Just select notebook page 4 from the Program Installation dialog.
You may define any key from the pool keys 0 to 9 and A to Z combined with
either with the CTRL or the ALT key. Once a Hotkey is defined for an
application, it is no more available for other sessions. You may define
Hotkeys for 72 different sessions as the maximum.
In the Desktop Configuration notebook you may define the Hotkey to be
detected systemwide (even if the focus window has an accelerator key
defined for the Hotkey) or only when PC/2, the WPS or the Window List has
the focus.
If PC/2 detects that the user pressed a Hotkey and the application the
Hotkey is defined for is not running, PC/2 launches the application,
otherwise, PC/2 will jump to the application already running.
You may temporarily suspend the Hotkey feature by pressing and holding
the SHIFT key while pressing the Hotkey. PC/2 will then ignore the
Hotkey and pass it over to the application that currently has the focus.
29.) How does the Hotkey feature work?
PC/2 knows which Hotkeys are used if you have defined them. However, PC/2
also needs to know at least a part of the application's titlebar text or
Window List entry to switch to, so you have to fill in the entryfield
"Window Name: " (on the Hotkey notebook page) with the session's titlebar
text or Window List entry.
For a session's Window Name either use part of the string that appears
in the session's titlebar, or part of the string that appears in the
Window List for this session. This is most important that you follow
this procedure, otherwise results become unpredictable.
If you press the Hotkey for a session, PC/2 searches all titlebars
and the Window List for the text from the "Window Name" entry and
switches to that session when a match was found.
PC/2 not only switches to the session the Hotkey is defined for, but
also switches to the Virtual Desktop the session resides on.
If neither the Window Name can be found on any window's titlebar nor
in the Window List, PC/2 assumes the application is not running and
launches it. This is why it is important that you ensure your entry in
the "Window Name" entryfield accurately relates to the titlebar name of
the running session's Window List entry.
You may temporarily suspend Hotkey detection, if you press the SHIFT key
simultaneously with the Hotkey. PC/2 then will *not* steal the Hotkey,
but passes it on the the window that had the focus while the keypress.
30.) Why should I use the Hotkey feature?
Well, you don't need to use it, but you may find it very useful to
quickly switch to a certain session, for example a host terminal
emulator and than switch back to a compiling environment residing
on different Virtual Desktops.
31.) I have defined some Hotkeys - now these keys are not available on other
sessions any more!
Once you have defined a Hotkey, this Hotkey will be "seen" by PC/2
when it is pressed, because PC/2 "steals" them, before the application,
the key was pressed in, gets the notification for that key. Hotkeys are
detected systemwide, unless you check the option "No systemwide Hotkeys".
You may allow an application "see" the Hotkey, if you have pressed the
SHIFT key simultaneously with the Hotkey.
For example, the EPM editor has defined an accelerator key for CTRL+U,
to invoke its undo function. You can define CTRL+U as a Hotkey for your
terminal emulator, but EPM will no longer see this key then (and not
showing the undo window). To allow EPM to see CTRL+U then, you have to
press and hold the SHIFT key in addition to the CTRL key while pressing
the U key.
32.) I switched to an application - now some keys don't work as when not
running PC/2!
You have probably defined a systemwide Hotkey in PC/2 for that key. The
Hotkey will not be "seen" by your application, unless you press the
SHIFT key while pressing the Hotkey, as described in 31.).
33.) I defined a Hotkey but the wrong window is activated!
You have probably defined a Hotkey for an application and have
inadvertantly started more than one copy of this same application. PC/2
only switches to the first application window, and ignores all other
sessions containing copies of the same hotkeyed application.
Be sure that you don't start more than one instance of a session a
Hotkey is defined for. A session is a PM, windowed OS/2 or DOS
application that displays at least one window on PM (Presentation
Manager).
34.) How to I define a Hotkey for a certain window (e.g. Drive C object)
even if it wasn't started from PC/2?
Assume that you have opened the Drive C - Tree View object from the
OS/2 System->Drives object of the WPS and you want to define ALT+C
as its Hotkey.
Create a new Menuentry and skip to the Hotkey notebook page of the
Program Installation dialog. Enable the Hotkey feature and select
ALT+C as the Hotkey.
Then select the entry of the Drive C object from the Current Window
List MLE and doubleclick on it. The selected entry will also be
filled into the entryfield Window Name. Now save the changes and
voila, you can now use the newly defined Hotkey.
As the Drive objects are WPS Objects too, Drive objects can only be
opened while the WPS is running.
35.) Do I need to completely fill in the Program Installation dialog to
define a new Hotkey?
No, you just need to fill in the Hotkey labeled notebook page. PC/2
uses the text entered in the entryfield Window Name to compare with
all windows' titlebars and Window List entries. If the text matches
any of these entries, (or subset of the entry) the window the entry is
defined for is activated.
To use the Hotkey feature, just ensure that the text entered in the
entryfield Window Name is part of any window's titlebar or Window List
entry.
36.) I have 2 OS/2 windows with the same name. Will the Hotkey work?
Yes, but only for the first window whose titlebar or Window List entry
matches to the Menuitem Window Name. You have to ensure a unique title
for a window to allow PC/2 to exactly identify a window and activate it
through the Hotkey function.
37.) How do I access the Window List on PM?
If you are positioned over the PM with the mouse pointer, just press
and hold down a mouse button and then click the other while not moving
the mouse pointer. The Window List will appear with the mouse pointer
in center (when the complete Window List can displayed then).
The PM is the bottommost window which you can see as your Desktop's
background, if either you don't run the WPS or you moved the WPS to
an other Virtual Desktop.
Of course pressing CTRL+ESC works too.
38.) What is the feature "Button 2 Titlebar click lowers Z-order" useful for?
Even if you don't use the Virtual Desktop feature, you may find that
sometimes you like to switch to a window which is under the currently
active one, but you don't want to move or minimize the active one to get
the other window to the top. If this option is on, it enables you to
just click mouse button 2 on the active window's titlebar to push this
window to the bottom. The window previously behind the active window now
becomes the topmost window. Note that with this function enabled, you
can't activate window movement with mouse button 2 anymore - however you
can still accomplish this using mouse button 1.
Pressing the CTRL key while clicking on the titlebar only moves the
window to bottom; pressing the Alt key activates the default action
of the titlebar (usually activating the move window tracking frame).
Therefore, the CTRL and Alt key may be temporarily used to suspend
the default PC/2 behavior.
39.) Can a Hotkey defined for PC/2 itself?
Yes, just enter PC/2 as the string to match on the Hotkey notebook
page in the Program Installation dialog and assign a Hotkey e.g.
ALT+P.
40.) When switching to a Virtual Desktop with a Hotkey, how is the window
aligned?
PC/2 moves the Desktop on the Virtual Desktop at the rate you defined
with the Virtual Desktop Scrolling scrollbar on Desktop Setup dialog.
The movement stops either when the middle point of a window becomes
visible on the screen the first time, or a surrounding edge was hit.
If you set the Virtual Desktop Scrolling to 100 % you will probably see
the best results.
--->>> --->>> --->>> Please also read the second part <<<--- <<<--- <<<---