@DATABASE English.guide *************************************************************************- @NODE MAIN "ActionPrefsEdit V1.3 © 1997-98 Jan Hendrik Schulz" @{b}ActionPrefs Edit@{ub} @{b}© 1997-98 Jan Hendrik Schulz@{ub} @{b}Version 1.3 (3.10.1998)@{ub} @{" Introduction " LINK INTRO} What is it? And Why? @{" Requirements " LINK NEEDS} Required hard- and software @{" Legal " LINK LEGAL} Please read this! @{" Installation " LINK INSTALL} How to install @{b}ActionPrefsEdit@{ub} @{" Startup " LINK START} and how to start it (->tooltypes) @{" Menu " LINK MENU} @{" Main Window " LINK MAINWIN} The main window of this program @{" Menu Edit Window " LINK MENUEDIT} Windows to edit menus @{" Action Edit Window " LINK ACTNEDIT} Windows to edit actions @{" FileID List Window " LINK FIDWIN} List of available FileIDs @{" Window Positions " LINK WINPOS} About the Multi-Window-System @{" Drag & Drop " LINK DAD} What can be done with Drag & Drop? @{" Known Bugs " LINK BUGS} @{" History " LINK HISTORY} @{fg shine}New!@{fg text} What's new since the last version? @{" Future " LINK FUTURE} What is planed for the future? @{" Author " LINK AUTHOR} How to contact the author @{" Thanks to " LINK THANKS} @{fg shine}New!@{fg text} = Here is something new or changed since the last version. @ENDNODE ********************************************************************** @NODE INTRO "Introduction" @{u}Introduction@{uu} If you are a registered user of @{"ScreenTab" LINK SCREENTAB}, you will have the DirWalker PlugIn. This PlugIn needs a so called ActionPrefs file to specify what action should be available with what filetype and what image should be displayed in front of the files and the actions. As this ActionPrefs file is a simple textfile, it's of course possible to edit it with a texteditor, and maybe you have done that allready. But it is not much fun to edit such a (complex and maybe long) file with a texteditor, so I decided to write a special Preferences Editor to make it easier to edit those ActionPrefs files. First I called this program 'DirWalkerPrefs' as the ActionPrefs file is only used by the DirWalker PlugIn until now. But the information in the ActionPrefs file can be usefull for other PlugIns or programs too, that's why I decided to call this program @{b}ActionPrefsEdit@{ub}. @ENDNODE ********************************************************************** @NODE NEEDS "Requirements" @{u}Requirements@{uu} · AmigaOS 2.04 (or better) · @{"MUI" LINK MUI} 3.8 (or better) · FileID Library 2.0 (or better) · @{"ScreenTab" LINK SCREENTAB} with DirWalker PlugIn, or any other program that needs an ActionPrefs file. @ENDNODE ********************************************************************** @NODE LEGAL "Legal" @{u}Legal@{uu} This version of @{b}ActionPrefsEdit@{ub} is freeware. Redistributing of @{b}ActionPrefsEdit@{ub} is only allowed, if all files are included and unchanged. It's not allowed to make any profit in any way by redistributing @{b}ActionPrefsEdit@{ub}. Including @{b}ActionPrefsEdit@{ub} on CD-ROMs is allowed as long as the CD-ROM costs not more than 30 DM / 20 US$. Before including @{b}ActionPrefsEdit@{ub} on coverdisks you have to ask @{"me" LINK AUTHOR} to get a written permission. @{b}ActionPrefsEdit is © copyright 1997-98 Jan Hendrik Schulz@{ub} @{b}ActionPrefsEdit@{ub} is provided as-is, without warranty of any kind. You are using @{b}ActionPrefsEdit@{ub} on your own risk. I'm in no way responsible for any damage or data loose, which may result in any way, directly or indirectly out of the usage of, or the impossibility to use @{b}ActionPrefsEdit@{ub}. @ENDNODE ********************************************************************** @NODE INSTALL "Installation" @{u}Installation@{uu} The installation is very simple. Just copy the program and its icon to where you want it and set the Tooltypes (see @{"Startup" LINK START}) to the correct values. That's it! See also: @{" Startup " LINK START} @ENDNODE ********************************************************************** @NODE START "Startup" @{u}Startup@{uu} You can run the program either from the Workbench by double-clicking on its icon, or from a Shell. The following Tooltypes/Shell arguments are available: @{b}PREFSFILE@{ub} Filename (incl path) of the ActionPrefs file. If you don't use this Tooltype/Shell argument to specify the ActionPrefs file, a filerequester pops up to ask for the file. If you cancel the filerequester, no file is loaded and you can create a totally new ActionPrefs file. Note: If you allready have a hand-made ActionPrefs file, you should be able to load it into @{b}ActionPrefsEdit@{ub} to modify it, but better make a copy of your file first, just in case! @{b}IMAGEDIR@{ub} Corresponds to the @{"ScreenTab" LINK SCREENTAB} IMAGEDIR Tooltype and should be set to the same directory! @{b}IMAGEHEIGHT/N@{ub} This value is necessary to correctly display images in the lists. Set this Tooltype/Shellargument as exactly as possible to the real height of the highest used image. If the value is to small, some images may be displayed cut off on the bottom; if the value is to big the lines of the lists are unnecessary height. The default value is 17. @{b}IMAGECACHE/S@{ub} Without this tooltype the data of an image(-file) is removed from memory as soon as it isn't needed anymore (eg. because the window where the image was displayed in, is closed). So, if the image data is needed again later, it has to be loaded again. Whith this tooltype the data of an image stays in memory until the program ends, and is re-used if needed. In every case the data of each imagefile is hold in memory only once, even if the image is used more than once and is displayed more than once at the same time. @{b}FILEIDSHOWALL/S@{ub} @{b}FILEIDSORTBYID/S@{ub} @{b}FILEIDPATTERN@{ub} With this Tooltypes/Shellarguments you can specify default values for the @{"FileID list window" LINK FIDWIN}. See there for more infos. @{b}SHOWCOMMAND/S@{ub} See @{"Action Test Function" LINK ACTNEDIT} @ENDNODE ********************************************************************** @NODE MENU "Menu" @{u}Menu@{uu} @{b}ActionPrefsEdit@{ub} has a Project menu, which contains the following items: @{b}Open...@{ub} Open an ActionPrefs file for editing. @{b}Note:@{ub} Only one ActionPrefs file can be edited at a time. So, if you made changes to an ActionPrefs file, don't forget to save it before loading another file, or all changes are lost! @{b}Save@{ub} The same function as the Save button of the @{"Main Window" LINK MAINWIN}. @{b}Save as...@{ub} Save the ActionPrefs in a new file. This function will not quit the program, but it will close all edit windows! @{b}Use@{ub} The same function as the Use button of the @{"Main Window" LINK MAINWIN}. @{b}About...@{ub} Show some information about the program. @{b}About MUI...@{ub} Show some information about @{"MUI" LINK MUI}. @{b}Quit@{ub} The same function as the Cancel button of the @{"Main Window" LINK MAINWIN}. @ENDNODE ********************************************************************** @NODE MAINWIN "Main Window" @{u}Main Window@{uu} The Main window contains the following elements: @{b}Menu list@{ub} This list contains all the menus. (A menu is a list of actions associated to a group of file types.) Every menu is represented by a name and the image (if defined) that will be shown by the @{"DirWalker PlugIn" LINK SCREENTAB} in front of the associated files. One menu will be the default menu, which is used for at least all those files without a special menu associated to them. Additionaly you can tell the DirWalker PlugIn to show this menu with all files, in this case the name of the default menu is used as its titel. The names of all other menus are not used by the DirWalker PlugIn. To indicate which menu is the default menu, its name is shown in a different color. @{b}'New' button@{ub} Creates a new menu and opens a @{"Menu-Edit window" LINK MENUEDIT} for it. @{b}'Edit' button@{ub} Opens a @{"Menu-Edit window" LINK MENUEDIT} for the selected list entry or moves an existing window of that entry to front. The same action happens if you double-click on a menu list entry. @{b}'Delete' button@{ub} Deletes the selected menu list entry. Note: The default menu can not be deleted! @{b}'Open/Close FileID list window' button@{ub} Opens or closes the @{"main FileID list window" LINK FIDWIN}. @{b}'Save' button@{ub} The (changed) settings are saved to the ActionPrefs file that was previously loaded and than the program ends. If no ActionPrefs file was loaded, a filerequester pops up to ask for the filename and path to use for saving the prefs. If the path of the ActionPrefs file starts with 'ENV:', a copy of the file is also written to ENVARC: (by replacing the 'ENV:' of the filepath with 'ENVARC:'). @{b}'Use' button@{ub} This button is only available if the path of the ActionPrefs file starts with 'ENV:'. The Use button has the same effect as the Save button, but without writing a copy of the file to ENVARC:. That leaves the file in ENVARC: unchanged and at the next reboot this unchanged file is copied to ENV: and used again. @{b}'Cancel' button@{ub} Quit the program without writing the changed data to a prefs file. Note: Like with every preferences program, there is no requester that asks for confirmation; the program quits immediately! See also: @{" Drag & Drop " LINK DAD} and @{" Menu Edit Window " LINK MENUEDIT} @ENDNODE ********************************************************************** @NODE MENUEDIT "Menu Edit Window" @{u}Menu Edit Window@{uu} Window Contents: @{b}'Name' string gadget@{ub} String gadget to enter the name of the menu. This name is only used in the menu list of the @{"Main Window" LINK MAINWIN} to specify the menu. The name is not used by the @{"DirWalker PlugIn" LINK SCREENTAB} and is stored in the ActionPrefs file as a comment. @{b}'Image' image select gadget@{ub} Image to be displayed by the @{"DirWalker PlugIn" LINK SCREENTAB} in front of each file this menu is used for. This image is also displayed in the menu list of the @{"Main Window" LINk MAINWIN}, in front of the menu name. A register group with two pages: @{b}'Actions' page@{ub} @{b}'Actions' list@{ub} List of all actions of the menu. @{b}'New' button@{ub} Creates a new action and opens an @{"Action-Edit window" LINK ACTNEDIT} for it. @{b}'Edit' button@{ub} Opens an @{"Action-Edit window" LINK ACTNEDIT} for the selected list entry or moves an existing window of that entry to front. The same happens if you double-click on an action list entry. @{b}'Delete' button@{ub} Deletes the selected action list entry. @{b}'Files' page@{ub} @{b}'Pattern' string gadget@{ub} String gadget to specify a DOS pattern, that the filename of every file this menu is used for should match. @{b}'FileIDs' list@{ub} List of FileIDs of those files, this menu should be used for. Use @{"Drag & Drop" LINK DAD} to move FileIDs from the @{"main FileID list" LINK FIDWIN} or the FileID list of another menu into this list, or from this list to the @{"main FileID list" LINK FIDWIN} or the FileID list of another menu. And if @{b}ActionPrefsEdit@{ub} runs on the workbench screen, you can drop icons of files on this list to add the FileID of the file. The sort order of the entries in this list depends on the sort order specified for the @{"main FileID list" LINK FIDWIN}. @{b}'OK' button@{ub} Accept all changes made to the menu and close the Menu-Edit window. @{b}'Cancel' button@{ub} Undo all changes made to the menu and close the Menu-Edit window. If you have moved a FileID from this menu to another menu, a requester will ask you if you want to undo this too, as therfore that FileID has to be removed from the other menu. @{b}Note:@{ub} The contents of the Menu Edit window is a little bit different if the menu is the default menu. The differences are as follows: · Only the contents of the Actions page of the above mentioned page group is available instead of the whole page group. · The 'Name' string gadget is labled 'Title' because what you type in there is used by the @{"DirWalker PlugIn" LINK SCREENTAB} as the title of the default menu, whilst the names of the other menus are only used whithin this program. See also: @{" Drag & Drop " LINK DAD}, @{" Window Positions " LINK WINPOS} @ENDNODE ********************************************************************** @NODE ACTNEDIT "Action Edit Window" @{u}Action Edit Window@{uu} Window Contents: @{b}'Name' string gadget@{ub} String gadget to enter the name of the action. @{b}'Image' image select gadget@{ub} Image to be displayed by the @{"DirWalker PlugIn" LINK SCREENTAB} in front of the action name. @{b}'Action' string gadget@{ub} The shell command-line that should be executed if this action is used. To set the program to be used, you don't have to type it in (of course you can), you can @{"drop" LINK DAD} the icon of the program onto this string gadget or use the file popup button to select the program via filerequester. In both cases only the first part of the string will be replaced, keeping the arguments unchanged! This command-line can include the following special codes: @{u}Code Function @{uu} {f} Name of the file (with path and in Quotes) the action is used for. {f-} Like {f}, but without quotes. {n;X} Ask for a number. Instead of X type in the question that should be displayed in the requester. {s;X} Ask for a string. Instead of X type in the question that should be displayed in the requester. {p;X} Ask for a file incl. path. Instead of X type in the text that should be used as title of the file- requester. {d;X} Ask for a directory. Instead of X type in the text that should be used as title of the requester. {q;X;Y} Show a requester to confirm the action. Instead of X type in the question, instead of Y type in the answers like @{b}Yes|No@{ub}. Only if the first answer is selected, the action will be executed. (See also the documentation of the @{"DirWalker PlugIn" LINK SCREENTAB}!) @{b}'OK' button@{ub} Accept all changes made to the action and close the window. @{b}'Cancel' button@{ub} Undo all changes made to the action and close the window. @{b}'Test' button @{ub} Use this button to test the action string. @{b}ActionPrefsEdit@{ub} will parse the action string for special codes and if something is wrong, you will get an error message. In this case the cursor of the action string gadget will be placed at the position of the error (as soon as you close the error requester). If the action string contains special codes, a window will pop up to ask for the necessary information. If the action contains the special code {q;X;Y} the 'OK' and 'Cancel' buttons of the window are replaced with the buttons of the {q;X;Y} command. As the action is not assigned to a file here (like it would be when the action is excuted by the @{"DirWalker PlugIn" LINK SCREENTAB}), the window will contain a filegadget to ask for the file to be use for the {f} or {f-} code, if necessary. Or you can drop an icon of a file onto the 'Test' button to test the action with this file used for {f} and {f-}. In this case the filename is displayed on top of the window (if the action contains additional codes) and the gadgets for {p;X} and {d;X} are initialised with this file or it's directory. If you close the window with 'OK' or the positive button of the {q;X;Y} command - or if no window is necessary - @{b}ActionPrefsEdit@{ub} will create the command line and will than execute this command as a new process. You can specify the @{b}SHOWCOMMAND@{ub} tooltype if you want to see the resulting command line before it is executed. @{b}ActionPrefsEdit@{ub} will show the command line in another window and you have to close this window with 'Execute' to execute the command. See also: @{" Drag & Drop " LINK DAD}, @{" Window Positions " LINK WINPOS} @ENDNODE ********************************************************************** @NODE FIDWIN "FileID List Window" @{u}FileID List Window@{uu} This window - which can be opened and closed from the @{"Main Window" LINK MAINWIN} - contains a list of all the FileIDs (ID and description) supported by the installed FileID.library. This list is used as a Drag&Drop source to add FileIDs to menus, or as a Drag&Drop destination to remove FileIDs from menus. (See also: @{" Drag & Drop " LINK DAD}) Additionaly to that list the window contains the following gadgets: @{b}'Sort by' cycle gadget@{ub} With this cycle gadget you can choose whether the FileID list in this window and all the FileID lists in the @{"Menu-Edit windows" LINK MENUEDIT} are sorted by the FileID IDs or by there description texts. By default the lists are sorted by the description texts, but that can be changed with the FILEIDSORTBYID Tooltype/Shellargument. @{b}'Show' cycle gadget@{ub} Here you can choose if you want to see all FileIDs in the list of this window, or only those @{b}not@{ub} used by a menu. If you choose "All" the used FileIDs are shown in a different color and with the name of the menu they are used for behind them. The default is to show only the unused FileIDs, but you can change that with the FILEIDSHOWALL Tooltype/Shellargument. @{b}'Pattern' string gadget@{ub} To make it easier to find a FileID you can type in a DOS stile pattern here to see only those FileIDs with a discription text matching this pattern. The dafault value of this gadgat is #? to show all FileIDs. That can be changed with the FILEIDPATTERN Tooltype/Shellargument. See also: @{" Drag & Drop " LINK DAD}, @{" Startup " LINK START} and @{" Main Window " LINK MAINWIN} @ENDNODE ********************************************************************** @NODE WINPOS "Window Positions" @{u}Window Position@{uu} As you can have several Menu Edit or Action Edit windows opened for different menus or actions at the same time, I made it possible to use the @{"MUI" LINK MUI} snapshot function to snapshot different window positions for up to 32 Menu Edit windows and up to 32 Action Edit windows. (Internally up to 2x32 different window IDs are used.) Everytime a new Menu/Action Edit window is opened, it will use the first of these snapshots (window IDs) currently not used be another window. For example, if there are two windows opened which are using the first two snapshot positions (window IDs) and you open another one, it will use snapshot position three, as that is the first currently unused. But if you first close the window using snapshot position one, the new window will use that snapshot position and not number three. So, if you will - for example - never use more than three Menu Edit windows at a time, open three windows, place them where you want them, snapshot everyone and close them. From now on every Menu Edit window that will be opened will use one of these three positions (no matter in which order you open and close your windows); as long as there are not allready three windows open who are using these three positions (window IDs). As soon as you will open a 4th Menu Edit window, it will use the 4th window ID with a different - still undefined - snapshot position. Note: Even if this feature is implemented for both, Menu Edit and Action Edit windows, they are handled separately. No Menu Edit window will ever use a snapshot position (window ID) of an Action Edit window, nor the other way round. @ENDNODE ********************************************************************** @NODE DAD "Drag & Drop" @{u}Drag & Drop@{uu} @{b}ActionPrefsEdit@{ub} makes heavy usage of @{"MUI" LINK MUI}'s Drag & Drop feature. And if you run @{b}ActionPrefsEdit@{ub} on the Workbench, even Workbench's Drag & Drop (AppWindow) features are used: · Every string gadget can be droped onto every other string gadget to replace the contents of the destination gadget with the one of the source gadget. (Hint: To drag a string gadget use the middle mouse button - if you have a three button mouse - (see @{"MUI" LINK MUI} prefs) or click on the border of the string gadget!) · Use Drag&Drop to change the order of the entries in the @{"menu list" LINK MAINWIN} and the @{"action lists" LINK MENUEDIT}. · Use Drag&Drop to move actions between menus. · Use Drag&Drop to move FileIDs between menus or from and to the @{"main FileID list window" LINK FIDWIN}. · Use Drag&Drop to copy all the data of a menu to another menu by draging the source menu from the @{"menu list" LINK MAINWIN} and drop it on the @{"Edit window" LINK MENUEDIT} of the destination menu. Every data of the destination menu is replaced by a copy of the data of the dropped menu. Exception: The FileID list is not copied, as this would result in double usage of the FileIDs! Instead the FileID list of the destination menu keeps unchanged. · Use Drag&Drop to copy all the data of an action to another action by draging the source action from an @{"action list" LINK MENUEDIT} and drop it on the @{"Edit window" LINK ACTNEDIT} of the destination action. Every data of the destiantion action is replaced by a copy of the data of the dropped action. No matter if the two actions both belong to the same menu or to different menus. If @{b}ActionPrefsEdit@{ub} runs on the Workbench: · You can drop icons of image files onto the image select gadgets of the @{"Menu Edit" LINK MENUEDIT} and @{"Action Edit" LINK ACTNEDIT} windows. · You can drop icons of programms onto the action string gadgets of the @{"Action Edit" LINK ACTNEDIT} windows to set the program of the action. This will only change the first part of the string and keeps the arguments unchanged! · You can drop icons of files onto the FileID list of a @{"Menu Edit Window" LINK MENUEDIT} to add the FileID of that file to the list. @ENDNODE ********************************************************************** @NODE BUGS "Known Bugs" @{u}Known Bugs@{uu} No known bugs. But if @{b}you@{ub} find a bug, please send @{"me" LINK AUTHOR} a bugreport! (Do not rely on someone else doing it! Thanks!) @ENDNODE ********************************************************************** @NODE HISTORY "History" @{u}History@{uu} @{fg shine} @{b}version 1.3 (3.10.1998)@{ub} · NEW: Automatic restart of @{"ScreenTab" LINK SCREENTAB}: To force ScreenTab to use a changed ActionPrefs file, @{b}ActionPrefsEdit@{ub} will now check if ScreenTab is running (whenever you save the ActionPrefs file) and if it is, @{b}ActionPrefsEdit@{ub} will try to quit ScreenTab and than re-run it. To re-run ScreenTab, wbstart.library is required. (@{b}ActionPrefsEdit@{ub} will of course not quit ScreenTab if the library is not available.) · Some changes to the locale catalog handling. @{fg text} @{b}version 1.2 (16.3.1998)@{ub} · NEW: @{"Action Test" LINK ACTNEDIT} function completely rewritten: - No ReqTools library needed anymore - The complete string is parsed before anything is displayed. So if the action string contains more than one special code and the second one is wrong, you don't have to answer the requester of the first one just to get the errormessage for the second one. - You can see the resulting comandline before it is executed, if you want. (See @{"tooltype SHOWCOMMAND" LINK START}) · Some minor code improvements. @{b}version 1.1 (25.1.1998)@{ub} · BUG: Whenever there was no image assigned to something, instead of simply displaying no image the program tried to load a file without name as image - and only because that failed, no image was displayed. · NEW: Improved image handling: Until now every displayed image was handled seperately, so if the same image was displayed twice (e.g. in different windows) the image data was loaded twice and hold in memory twice at the same time. Now an image file is loaded only if the data is not in memory allready. · NEW: IMAGECACHE tooltype/shellargument added. · NEW: Action test function added. See @{"Action Edit Window" LINK ACTNEDIT}. · NEW: Program now localised. German catalog available; if you want to make a catalog for another language, please send @{"me" LINK AUTHOR} an email. · NEW: You can now drop icons on a FileID list in a @{"Menu Edit Window" LINK MENUEDIT} to add the FileID of that file to the list. · Improved error handling. In many situations there was no error message if something went wrong, e.g. if @{b}ActionPrefsEdit@{ub} was unable to load or save the ActionPrefs file. · Some minor code improvements. @{b}version 1.0@{ub} · First public release. @ENDNODE ********************************************************************** @NODE FUTURE "Future" @{u}Future@{uu} If you have any ideas, why not send @{"me" LINK AUTHOR} an email!? @ENDNODE ********************************************************************** @NODE AUTHOR "Author" @{u}Author@{uu} Snail-Mail: Jan Hendrik Schulz Elsässer Straße 19 22049 Hamburg Germany EMail: schulz_j@informatik.fh-hamburg.de or: schulzjan@dame.de @{b}IMPORTANT NOTES:@{ub} · Please @{b}don't@{ub} send your emails to @{b}both@{ub} email-addresses! First try @{b}one@{ub} of them and only if that fails try the other one. @{b}Thanks!@{ub} · If you expect an answer per snail-mail, please send me enough money or (german!) stamps to cover my costs. @ENDNODE ********************************************************************** @NODE THANKS "Thanks to" @{u}Thanks to@{uu} Michael Link for @{"ScreenTab" LINK SCREENTAB} Stefan Stuntz for @{"MUI" LINK MUI} Wouter van Oortmerssen for AmigaE @ENDNODE ********************************************************************** @NODE MUI "MUI" This application uses MUI - MagicUserInterface (c) Copyright 1993-96 by Stefan Stuntz MUI is a system to generate and maintain graphical user interfaces. With the aid of a preferences program, the user of an application has the ability to customize the outfit according to his personal taste. MUI is distributed as shareware. To obtain a complete package containing lots of examples and more information about registration please look for a file called "muiXXusr.lha" (XX means the latest version number) on your local bulletin boards or on public domain disks. If you want to register directly, feel free to send DM 30.- or US$ 20.- to Stefan Stuntz Eduard-Spranger-Straße 7 80935 München GERMANY Support and online registration is available at http://www.sasg.com/ @ENDNODE ********************************************************************** @NODE SCREENTAB "ScreenTab" @{u}ScreenTab@{uu} @{b}ScreenTab@{ub} is © by Michael Link (link@userwst2.fh-reutlingen.de) and can be found on AmiNet. @{b}ScreenTab@{ub} is one of those Windows95 Start-Button tools, but with some very nice features, like: · The task-bar appears only, if you move the mouse to the bottom of the screen. · The task-bar can appear on every screen you want, not only on the Workbench screen. · Instead of tasks (or windows) the task-bar shows the screens and makes it possible to go to another screen. · The Start button can be configured with a nice preferences program and features PlugIns. With those PlugIns it's for example possible to have a list of all commodities (you can use that PlugIn instead of the commodities exchange program), or with the @{b}DirWalker PlugIn@{ub} you can show the contents of a directory as part of the Start button menu structure and you can perform actions on the files, depending on the filetype. And that are only some of the features, offered by @{b}ScreenTab@{ub}. @{b}ScreenTab@{ub} is Shareware, and some of the PlugIns (like the @{b}DirWalker@{ub} @{b}PlugIn@{ub}) are only available to registered users, but it isn't too expensive to become a registered @{b}ScreenTab@{ub} user, and it is really worth the money! @ENDNODE ****END****END****END****END****END****END****END****END****END****END