If you consider your context menus too crowded, you can tell the WPS to omit displaying those menu entries which are only "doubles" to mouse operations ("Copy", "Move", etc.).
Moreover, you can remove many default menu items individually in the "Workplace Shell" object on the "Context menu" pages.
The folder content functions are helpful, but can crowd your context menus too much also if you declare many folders to be your favorites. On my system, I have created a separate folder called "frequent", which I have declared to be my only favorite folder. In this folder, I can put all those folders which I frequently access, so I only have one context menu entry, but a submenu with all my favorite folders.
Probably a menu ID conflict with some other WPS extension. This is a known problem with Network logins. Go to the "&xwp; Configuration", "Paranoia" page, and raise the "Menu item ID offset". Press "Help" there for details. With V0.9.0, the default offset has been raised to 700, which should help in most cases.
Same thing as above.
Versions prior to V0.82 served as a test for video drivers in this respect. ;-) I have found out that some video drivers do not support transparent background mix for bitmaps, which XFolder used to use. While some drivers silently ignored the transparency, other drivers crashed badly and stopped the whole system (especially Matrox Millenium). With V0.82, I have changed the icon painting for folder content menus to use regular icons instead of bitmaps. Icon painting is still disabled per default in case something should still go wrong. Turn on "Show icons" on the "Context menus" pages in "Workplace Shell" to enable icon painting.
If you still have problems, Ralph Scharpf reported that one could install the IBM GRADD drivers for MGA video cards instead, which appear to be working. Unfortunately, those cards do not support 1024x768 with more than 60 Hz, but if you can live with 800x600, this appears to be a solution.
Because the Launchpad is not a folder. &xwp; can only subclass the default folder window procedure to receive important system messages when menus are being opened, which is when the variable menu items are inserted into context menus. Since the Launchpad does not use the folder's default window procedure, &xwp; cannot easily subclass it either.
Probably no. Since V0.70, &xwp; uses the .ICONPOS extended attributes of the config folder and its subfolders to determine the order of objects in a folder. Trouble is, these are only written by the WPS when the folder is closed, and only if the folder was open in Icon or Details view. So simply open the folder in Details view and close it again. That should work.
Put a tilde character ("~") in front of a certain character in the program object's title. This will underline the following character in the menu entry, allowing you to type this character as a keyboard shortcut when the context menu is displayed.
(This is different from the folder hotkeys which &xwp; adds to open folders.)
Example: &os2; ~command window will make "c" a keyboard shortcut in the context menu.
For this, be sure to check "Suppress ''~'' in window title" in the "Workplace Shell" object on the "Context menus" pages.
You will probably need to put a "%" character into the "Parameters" field of the program object to prevent &xwp; from passing the folder as a parameter. See the context help for the &xwp; Configuration Folder for details.
&xwp; does open shadows of program objects in the configuration folders, but it does not change their directories or parameters. This is not a bug, it's an intentional limitation for security. COPY your program objects to the configuration folders instead of creating shadows. See the context help for the &xwp; Configuration Folder for details.
For commands which are built into CMD.EXE (such as REN, COPY, DEL, CD), put a program object into the &xwp; Configuration Folder. Then specify CMD.EXE in the program object with /C <commands> in the "Parameters" field.
Example for deleting the folder's whole content: put CMD.EXE in the "Path and filename" field and /C DEL * in the "Parameters" field. This is, of course, just a stupid example and NOT recommended.
I have included extra information in the appendices of this documentation, which might be useful to you:
If you're not too familiar with REXX, you can copy and modify the ALWSSORT.CMD file in the &xwp; installation directory to test some of the folder settings. Please see the "Related files" page for more.
In addition, I strongly recommend the INF book "Rexx Tips&Tricks" by Bernd Schemmer, which is available as "rxtt28.zip" (or newer) on Hobbes.
If you create programs objects which need to be opened several times
from different directories (namely for command line objects), be sure to
check the "Create new window" flag on the "Window" tab in the object's
notebook.
Otherwise &os2; will not start a new window but simply resurface
the already opened one.
With V0.9.1, this behavior has changed because many people have complained
about XFolder's behavior when the Configuration Folder was missing. So to recreate
that folder, go to the "Object" page in the
"&xwp; Setup" object and press the respective
button.