home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Windows Shareware 500 (First Edition)
/
disk2.img
/
FILECMDR
/
FILECMDR.MA$
/
filecmdr.ma_
Wrap
Text File
|
1992-08-26
|
17KB
|
786 lines
File Commander User's Guide
Wilson WindowWare, Inc.
2701 California Ave SW ste 212
Seattle, WA 98116
Orders: (800) 762-8383
Support: (206) 937-9335
Fax: (206) 935-7129
Copyright (c) 1992 by Morrie Wilson.
All rights reserved.
No part of this manual may be reproduced or transmitted in any
form or by any means, electronic or mechanical, including
photocopying and recording, for any purpose without the express
written permission of Wilson WindowWare, Inc. Information in
this document is subject to change without notice and does not
represent a commitment by Wilson WindowWare, Inc.
The software described herein is furnished under a license
agreement. It is against the law to copy this software under any
circumstances except as provided by the license agreement.
U.S. Government Restricted Rights
Use, duplication, or disclosure by the Government is subject to
restrictions as set forth in subdivision (b)(3)(ii) of the Rights
in Technical Data and Computer Software clause at 252.227-7013.
Contractor/manufacturer is Wilson WindowWare, Inc./2701 California
Ave SW /ste 212/Seattle, WA 98116
Trademarks
Microsoft and MS-DOS are registered trademarks of Microsoft
Corporation.
Windows, Word for Windows, Excel, and File Manager are trademarks
of Microsoft Corporation.
WinBatch, Command Post, and File Commander are trademarks of Wilson
WindowWare, Inc.
ii
CONTENTS
CONTENTS iii
INTRODUCTION v
System Requirements v
About This Manual vi
Notational Conventions vi
Acknowledgements vi
GETTING STARTED 1
USING FILE COMMANDER 3
Installation 3
Add-On Limitations 3
Menu Files 4
Menu Titles 5
Restrictions 5
FILE COMMANDER FUNCTIONS 7
Introduction 7
Function List 7
CurrentPath 8
DirExist 9
MsgTextGet 10
Refresh 11
iii
INTRODUCTION
INTRODUCTION
File Commander is an add-on for the Windows File Manager, which
allows you to add your own custom menu items to the normal File
Manager menu.
With almost two hundred functions and commands, File Commander can:
. Run Windows and DOS programs.
. Send keystrokes directly to applications.
. Rearrange, resize, hide, and close windows.
. Run programs either concurrently or sequentially.
. Display information to the user in various formats.
. Prompt the user for any needed input.
. Present scrollable file and directory lists.
. Copy, move, delete, and rename files.
. Read and write files directly.
. Copy text to and from the Clipboard.
. Perform string and arithmetic operations.
. Make branching decisions based upon numerous factors.
And much, much more.
System Requirements
File Commander requires an IBM PC or compatible with a minimum of
2MB memory running Microsoft Windows version 3.1 or higher.
v
About This Manual
File Commander is an application which uses our Windows Interface
Language (WIL). Please refer to the WIL Reference Manual for an
introduction to WIL, as well as for complete documentation of the
many functions available in WIL (and therefore, in File Commander).
This User's Guide includes only topics and functions which are
exclusive to File Commander or which behave differently in File
Commander, as well as additions and changes that have been made
since the WIL Reference Manual went to press.
Note: File Commander is a menu file based implementation of WIL.
Notational Conventions
Throughout this manual, we use the following conventions to
distinguish elements of text:
ALL-CAPS
Used for filenames.
Boldface
Used for important points, programs, function names, and parts of
syntax that must appear as shown.
system
Used for items in menus and dialogs, as they appear to the user.
Small fixed-width
Used for WIL sample code.
Italics
Used for emphasis, and to liven up the documentation just a bit.
Acknowledgements
File Commander software developed by Morrie Wilson.
Documentation written by Richard Merit.
vi
GETTING
STARTED
File Commander is quite easy to install. You will find an
appropriate diskette in your File Commander package. Take the
diskette and insert it into your floppy drive. The File Commander
installation program is itself a Windows application, so make sure
Windows is running.
Start (or activate) File Manager, and click on the A: or B: drive
icon, depending on which floppy drive contains the File Commander
diskette. A directory tree will appear for the File Commander
diskette. You should see a root directory icon. Double-click on
this icon and a list of filenames will appear. Find the filename
WSETUP.EXE and double-click on it. Follow whatever instructions
WSETUP gives you.
WSETUP will copy or create the necessary files in a directory of
your choice.
1
USING
FILE COMMANDER
USING
FILE COMMANDER
Installation
File Commander is not run as a normal executable program. Rather,
as an extension to File Manager, it is loaded automatically when
File Manager starts up. The WSETUP program, which is used to
install File Commander, adds or modifies two sections to your
WINFILE.INI file: [AddOns] and [FileCmdr]. The settings in these
sections determine the start-up defaults for File Commander.
Add-On Limitations
File Commander allows you to attach from one to four top-level menu
items to File Manager, each of which is considered to be a separate
File Manager add-on (and each of which is represented by a
combination of a DLL file and a menu file). By default, WSETUP
configures File Commander to add four add-ons. However, you may
want to use a smaller number, since File Manager allows a maximum
of only four or five add-ons, and you may have other add-ons which
you want to use in addition to File Commander. You can reduce the
number of add-ons which File Commander adds by editing the [AddOns]
section of WINFILE.INI. The default installation adds four add-
ons, as follows:
[AddOns]
WWWFC1=WWWFC1.DLL
WWWFC2=WWWFC2.DLL
WWWFC3=WWWFC3.DLL
WWWFC4=WWWFC4.DLL
3
USING
FILE COMMANDER
(Your [AddOns] section will contain additional lines if you have
add-ons from any other products already installed). To reduce the
number of File Commander add-ons to three, simply delete the
reference to add-on #4 (WWWFC4.DLL):
[AddOns]
WWWFC1=WWWFC1.DLL
WWWFC2=WWWFC2.DLL
WWWFC3=WWWFC3.DLL
You can likewise remove add-on #3 (WWWFC3.DLL) and #2 (WWWFC2.DLL).
Note: Early versions of Windows 3.1 only support four add-on DLL's.
It is expected that future versions will support five add-on DLL's.
Please refer to the File Commander README.TXT file for any updated
information on this.
Menu Files
Each File Commander add-on DLL has an associated menu file, which
defines the menu structure of that add-on. The names of these menu
files are specified in the [FileCmdr] section of WINFILE.INI, as
follows:
MenuFile1=WWWFC1.MNU
MenuFile2=WWWFC2.MNU
MenuFile3=WWWFC3.MNU
MenuFile4=WWWFC4.MNU
Each of these menu files is independent, and is edited individually
(refer to the WIL Reference Manual for information on menu file
structure). Each menu file can contain a maximum of 99 menu items.
4
Menu Titles
The titles of each of the top-level menu items are determined by
the following settings in the [FileCmdr] section of WINFILE.INI:
MenuTitle1=
MenuTitle2=
MenuTitle3=
MenuTitle4=
"MenuTitle1" is the title of the menu defined by "MenuFile1", etc.
Restrictions
File Commander does not support the use of menu hotkeys, as
discussed in the WIL Reference Manual.
5
FILE COMMANDER
FUNCTIONS
FILE COMMANDER
FUNCTIONS
Introduction
This section includes only those additional File Commander
functions which do not appear in the WIL Reference Manual. The WIL
Reference Manual is your primary reference to the functions
available in File Commander.
Note: The functions listed under the See Also headings may be
documented either in this User's Guide or in the WIL Reference
Manual.
Function List
CurrentPath ( )
Returns path of the selected filename.
DirExist ([d:]path)
Determines if a directory exists.
MsgTextGet (window-name)
Returns the contents of a Windows message box.
Refresh (request#)
Updates file window display.
7
CURRENTPATH
CurrentPath
Returns path of the selected filename.
Syntax:
CurrentPath ( )
Parameters:
(none)
Returns:
(s) path of currently-selected file.
When a WIL menu shell displays the files in the current directory,
one of them may be "selected." This function returns the drive and
path of that file, if any.
This is different than a "highlighted" file. When a file is
highlighted, it shows up in inverse video (usually white-on-black).
To find the filenames that are highlighted, see FileItemize.
Example:
myfile = StrCat(CurrentPath(), CurrentFile())
DirChange("c:\word")
Run("winword.exe", myfile)
See Also:
CurrentFile, DirGet, FilePath
8
DIREXIST
DirExist
Determines if a directory exists.
Syntax:
DirExist ([d:]path)
Parameters:
(s) [d:]path directory name, with optional drive.
Returns:
(i) @TRUE if the directory exists;
@FALSE if it doesn't exist.
You can use this function to determine whether a specified drive is
valid by checking for the existence of the root directory on that
drive.
Examples:
wpdir = "c:\wp"
If DirExist(wpdir) == @FALSE Then DirMake(wpdir)
DirChange(wpdir)
:top
drive = AskLine("Run Excel", "Enter a drive letter", "")
If drive == "" Then Exit
drive = StrSub(drive, 1, 1)
If DirExist("%drive%:\") == @FALSE Then Goto top
NetAddCon("\\userapps\excel", "", drive)
See Also:
DirChange, DirMake, DirRemove, DirRename, FileExist
9
MSGTEXTGET
MsgTextGet
Returns the contents of a Windows message box.
Syntax:
MsgTextGet (window-name)
Parameters:
(s) window-name full title of the message box window.
Returns:
(s) contents of the message box.
This function returns the text contents of a standard Windows
message box. "Window-name" must be the full title of the message
box window, and is case-sensitive.
Note: This function will not work with the types of message boxes
created by most WIL functions, since they are not standard Windows
message boxes.
Example:
msg = MsgTextGet("Microsoft Word")
If msg == "Search text not found" Then SendKey("~")
10
REFRESH
Refresh
Updates file window display.
Syntax:
Refresh (request#)
Parameters:
(i) request# see below.
Returns:
(i) always 1.
This function updates the files being displayed in the File Manager
window, as well as the drive icons that are displayed. It is
useful after running an application (such as a DOS program) which
creates, deletes, or renames a file in the directory being viewed,
or connects to (or disconnects from) a network server, and you wish
the changes to be reflected in the File Manager window.
Specifying a request# of 0 causes only the active window to be
updated, and specifying a request# of 1 causes all File Manager
windows to be updated.
Note: This command does not take effect until the WIL program has
completed, regardless of where the command may appear in the
program.
Example:
Run("pkunzip.exe", CurrentFile())
Refresh(0)
See Also:
Reload
11