source: branches/MKIMES/dll/ipf/config.ipf@ 1036

Last change on this file since 1036 was 2, checked in by root, 23 years ago

Initial revision

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 19.8 KB
Line 
1:h1 res=92000 name=PANEL_CONFIG.Config Menu
2:i1 id=aboutConfig.Config Menu
3
4:artwork name='bitmaps\tweak.bmp' align=center.
5:p.
6FM/2 can be configured as you like it using the commands under this
7submenu. It is highly recommended that you step through the items in
8this submenu when you first begin to use FM/2, both to familiarize
9yourself with the available configuration options and to make FM/2
10work the way you like it to work.
11:p.
12To change fonts and colors, FM/2 uses the WPS Font and Color Palettes.
13The Config menu contains commands to call up these objects for you.
14:p.
15This submenu affects general FM/2 behavior. Each class of container has
16its own configuration menu that allows you to set the type of view,
17filtering, and so on. To get the popup menu that controls the
18container's appearance, request a :link reftype=hd res=93700.context
19menu:elink. while the pointer is over an empty area of the container, or
20select the Views pulldown submenu.
21:p.
22The :hp6.:link reftype=hd res=99400.Toggle quicklists:elink.:ehp6.
23command causes a dropdown listbox to appear below the toolbar (if one is
24being used; below the pulldown menu, if one is being used, or titlebar
25if not) and above other windows. The listbox contains the directory
26names you've assigned in the :link reftype=hd res=91500.Walk
27Directories:elink. dialog. If you pick one, a Directory Container for
28that directory is opened (hold down the Shift key while clicking to
29change an existing Directory Container instead). If the dropdown listbox
30is already present, this command causes it to disappear.
31:p.
32A Drive Finder dropdown listbox also appears with the quicklist;
33selecting a drive in this list causes the Drive Tree container to scroll
34to show the selected drive and make it the current object.
35:p.
36Finally, a Setup dropdown list also appears that contains names of
37setups (Drive Tree location, Directory Container locations and
38associated directory names). Pick a setup name, and FM/2 reopens and
39repositions the windows as they were when you saved the setup. A
40context menu requested on the setup list entry field is used to save and
41delete setup names. To add a name, enter it in the entry field of the
42dropdown, request a context menu, and select :hp1.Save state as
43name:ehp1. To delete a name, put it in the entry field, request a
44context menu and select :hp1.Delete state name:ehp1.
45:p.
46The :hp6.Autoview:ehp6. submenu controls the Autoview window. The
47default for this conditional cascade menu is the :hp6.Toggle autoview
48window:ehp6. command, which causes an autoview window to appear above
49the status line at the bottom of the screen. As you move the cursor
50from object to object, FM/2 displays the first few lines of file objects
51in this window. If the autoview window is already displayed, clicking
52this command causes it to disappear. You can also set the what is to
53be autoviewed -- either the file's .COMMENTS EA or the start of the
54file's contents (similar to the *nix HEAD program). When .COMMENTS EAs
55are being viewed, you can edit them and the changes will be saved when
56you switch the focus from the Autoview window. You can reach this
57editable Autoview window with the Ctrl + Tab hotkey if you are allergic
58to your mouse.
59:p.
60Clicking the contents Autoview window with B1 causes the file to be
61viewed. Clicking with B3 (or chording with B1 and B2 simultaneously)
62causes the extended attributes to be viewed. If viewing .COMMENTS
63rather than contents, you can pick :hp1.View file:ehp1. from the
64context menu.
65:p.
66The :hp6.Toggle bottom buttons:ehp6. menu item turns off and on a row of
67buttons that appear just above the status line(s). The buttons display
68the name, date, and attributes of the currently selected object, and the
69filter status of the current container. If clicked with B1, a command
70is generated (rename, info, edit date/attributes and filter dialog
71respectively). If clicked with B2, a context menu appears (the same one
72you get if you click B2 on the first status line). If clicked with B3,
73the sort changes for the current container: filename, last write date,
74file size and reverse sort respectively.
75:p.
76The :hp6.Toggle drivebar:ehp6. menu item turns off and on a bar showing
77all available drives. You can click these drive buttons to find or
78switch to a drive (depending on the active window when the button is
79clicked), drag objects onto the buttons, request a context menu on a
80button for more commands dealing with the drive, or click B3 to open a
81Directory Container for that window (or surface and activate one that
82already exists).
83:p.
84See also&colon.
85.br
86:link reftype=hd res=97600.FM/2 window layout:elink.
87.br
88:link reftype=hd res=99400.Using quicklists:elink.
89.br
90:link reftype=hd res=91800.Toolbar:elink.
91.br
92:link reftype=hd res=90400.Associations:elink.
93.br
94:link reftype=hd res=90700.Commands:elink.
95.br
96:link reftype=hd res=94200.Edit Archiver Data:elink.
97.br
98:link reftype=hd res=94600.Settings notebook:elink.
99.br
100:link reftype=hd res=100065.Set Target directory:elink.
101
102:h2 res=91800 name=PANEL_TOOLBAR.Toolbar
103:i1 id=aboutToolbar.Toolbar
104
105:artwork name='bitmaps\toolbar.bmp' align=center.
106The :hp1.toolbar:ehp1. is a collection of buttons that invoke some of
107the commands in the pulldown or popup menus. Placing the mouse pointer
108on a button and pressing and holding B2 displays brief help for the
109button on the titlebar.
110:p.
111Some of the buttons will allow objects to be dragged onto them; for
112example, you can drag objects onto the trashcan to delete them. Note
113that the hotspot of the mouse pointer itself should be over the button
114before releasing, not the icon being dragged (icons are slightly offset
115from the mouse pointer to give better target visibility). Target
116emphasis is provided in the form of a black outline around the button,
117and the arrow pointer turns into a hand when above a toolbox icon.
118:p.
119This toolbar submenu is a conditional cascade menu, meaning that if you
120click other than on the boxed arrow a default command is executed (the
121toolbar is toggled off and on), but if you click on the boxed arrow you
122get a submenu of items you can select (the other choices are Text
123Toolbar, which will cause the toolbar to appear as "normal" buttons with
124text on them, or Toolbar Titles, which will cause text to appear below
125the toolbar bitmap buttons).
126:p.
127Toolbar buttons are user-configurable. To change the toolbar, click
128mouse button two (usually the right button) while the mouse pointer is
129over a button to pop up a context menu. You can get the "Load Toolbox"
130dialog by clicking B2 on a blank area of the toolbar, and the "Add
131Button" dialog by chording on a blank area of the toolbar.
132:p.
133For advanced/curious users&colon. Information on what buttons are in the
134toolbar is kept in a file named FM3TOOLS.DAT. This file is an ASCII
135(plain text) file that contains information defining the toolbar. The
136file contains comments that explain its format.
137:p.
138FM/2 allows you to create customized toolboxes that can be loaded as
139required to provide toolboxes for specific activities. Although FM/2
140provides ways to edit the toolbar internally, it's probably easier to
141load the definition files into a text editor and make the changes
142manually en masse.
143:p.
144If you'd like to see a different toolbar layout (and try out the Load
145Toolbox command), right-click on the toolbar, pick Load Toolbox from the
146resultant menu, and pick a toolbox from the listbox. Then you might try
147creating your own and saving it with the Save Toolbox command.
148:p.
149See also&colon.
150.br
151:link reftype=hd res=96300.Reorder Tools:elink.
152.br
153:link reftype=hd res=94400.Edit Tool:elink.
154.br
155:link reftype=hd res=96400.Add Tool:elink.
156.br
157:link reftype=hd res=94000.Save Tools:elink.
158.br
159:link reftype=hd res=94500.Load Tools:elink.
160
161:h3 res=96300 name=PANEL_REORDERTOOLS.Reorder Tools
162:i1 id=aboutReorderTools.Reorder Tools
163This dialog, accessed from the context menu of a tool button, allows you
164to rearrange the order of the toolbar's tool buttons. You take selected
165items from the left listbox and Add them to the end of the right listbox
166with the :hp1.Add>>:ehp1. button. When you've moved everything to the
167right listbox, click :hp1.Okay:ehp1.. Click :hp1.Cancel:ehp1. if you
168change your mind.
169:p.
170In reality, you don't need to move everything to the right listbox. You
171can move only what you want moved to the top of the list, then click
172Okay. Anything remaining in the left listbox is added to the end of
173what's in the right listbox.
174:p.
175The :hp1.<<Remove:ehp1. button can be used to move selected items from
176the right listbox to the bottom of the left listbox.
177
178:h3 res=94400 name=PANEL_EDITTOOL.Edit Tool
179:i1 id=aboutEditTool.Edit Tool
180
181This dialog allows you to change the help and text strings and flags
182associated with a button. Edit as desired, then click Okay. Click
183Cancel if you change your mind.
184:p.
185The :hp1.Help:ehp1. field should contain text to remind you what the
186button's command does. For example, a button that deletes files and
187directories might have help reading "Delete files and directories".
188:p.
189The :hp1.Text:ehp1. field should contain very brief text that will be
190placed on the button (if the tool id has no bitmap associated with it).
191:p.
192The :hp1.Droppable:ehp1. checkbox determines if the tool can have objects
193dropped on it or not. See list below.
194:p.
195The :hp1.Visible:ehp1. checkbox determines if the tool is visible or not.
196:p.
197If the :hp1.Separator:ehp1. checkbox is checked, FM/2 puts a bit of
198whitespace after the button (separates it from the next button).
199:p.
200If you check the :hp1.User-defined bmp:ehp1. checkbox, FM/2 will allow
201you to use your own bitmap. Bitmaps are named after the :hp1.ID:ehp1.
202of the button -- for example, the bitmap file for ID 1005 would be named
203"1005.bmp". Clicking the :hp1.Edit bmp:ehp1. button will cause ICONEDIT
204to be loaded with the bitmap, ready to edit. (Note that bitmaps should
205be 28 x 28.)
206:p.
207The :hp1.ID:ehp1. field identifies the command that is associated with
208this button. See the :link reftype=hd res=96401.Tool IDs:elink. topic.
209
210:h3 res=96400 name=PANEL_ADDTOOL.Add Tool
211:i1 id=aboutAddTool.Add Tool
212
213This dialog is accessed from the context menu of a tool button, or if you
214turn on the toolbar when there are no tools defined.
215:p.
216To add a tool, fill in the fields as appropriate and click Okay. Click
217Cancel if you change your mind.
218:p.
219The :hp1.Help:ehp1. field should contain text to remind you what the
220button's command does. For example, a button that deletes files and
221directories might have help reading "Delete files and directories".
222:p.
223The :hp1.Text:ehp1. field should contain very brief text that will be
224placed on the button (if the tool id has no bitmap associated with it).
225:p.
226The :hp1.Droppable:ehp1. checkbox determines if the tool can have objects
227dropped on it or not. See list below.
228:p.
229The :hp1.Visible:ehp1. checkbox determines if the tool is visible or not.
230:p.
231If the :hp1.Separator:ehp1. checkbox is checked, FM/2 puts a bit of
232whitespace after the button (separates it from the next button).
233:p.
234If you check the :hp1.User-defined bmp:ehp1. checkbox, FM/2 will allow
235you to use your own bitmap. Bitmaps are named after the :hp1.ID:ehp1.
236of the button -- for example, the bitmap file for ID 1005 would be named
237"1005.bmp". Clicking the :hp1.Edit bmp:ehp1. button will cause ICONEDIT
238to be loaded with the bitmap, ready to edit.
239:p.
240The :hp1.ID:ehp1. field should be assigned a number that tells FM/2 what
241the command associated with the button is. See :link reftype=hd
242res=96401.Tool IDs:elink. topic.
243
244:h3 res=96401 name=PANEL_TOOLIDS.Tool IDs
245:i1 id=aboutToolIDs.Tool IDs
246
247:xmp.
248ID Command Droppable?
249==== ================================================= ==========
2501023 View Files Y
2511024 Edit Files Y
2521026 Make Directory N
2531010 Object Information Y
2541005 Rename Files/Directories Y
2551004 Delete Files/Directories Y
2561006 Permanently Delete Files/Directories Y
2571009 Set Attributes and Date/Time of Files/Directories Y
25810002 Walk Directories N
25910008 Select All Files N
26010007 Deselect All N
2611029 Archive Files/Directories Y
2621030 Extract From Archives Y
2631022 Create Objects Y
2641021 Create Shadow Objects Y
2651002 Copy Files/Directories Y
2661001 Move Files/Directories Y
2672003 Kill Process N
2682004 Undelete Files N
2692006 Instant Command File N
2702007 OS/2 Command Line N
2715001 Filter Container N
2723001 Edit Associations N
2731048 Edit Commands N
2745021 Rescan N
2751007 Print Files Y
2761008 Extended Attributes Y
2772001 View INI Files Y
2781027 Save List to Clipboard Y
2791028 Save List to File Y
2801011 Collect Files/Directories N
2811060 Collect Files/Directories from list file Y
2822010 Bookshelf Viewer N
2831017 Open Default Y
2841031 Directory sizes N
2851132 UUDecode Y
2861133 Merge Y
2871111 Exit FM/2 N
2884001 First Command Y
2894002 Second Command Y
290&period...
2914900 First Toolbox N
2924901 Second Toolbox N
293&period...
294:exmp.
295Note&colon. Other Commands can also be used; just add to 4000 as required
296to get the number of the command. For instance, Command 4 would be ID
2974004. Command buttons use the text field; others shown have bitmaps
298associated with them in FM/2's resources. Remember that if you change
299your Commands around, you need to resync the tools to the Commands...
300:p.
301Note&colon. Toolbox buttons on a toolbar cause the appropriate toolbox
302to be loaded from QUICKTLS.DAT (one filename per line, blank lines and
303lines beginning with ";" ignored). The file named on the first line is
304the First Toolbox, and so forth. You can have up to 50 toolbox buttons
305defined (total).
306:p.
307This list isn't complete; ask me if you'd like a command added that
308doesn't appear, and I'll tell you if it can be added and what the ID is,
309if so.
310
311:h3 res=94000 name=PANEL_SAVETOOLS.Save Toolbox
312:i1 id=aboutSaveTools.Save Toolbox
313
314FM/2 allows you to save toolboxes (groups of tools) for later recall
315with the :link reftype=hd res=94500.Load Toolbox:elink. command.
316:p.
317Type the name of the file to hold the toolbox definitions into the entry
318field below the listbox, or select a file displayed in the listbox (it
319will be overwritten). FM/2 saves the toolbox definitions into the file.
320:p.
321The files are given an extension of &period.TLS if you don't specify an
322extension. The listbox shows files in the FM/2 directory that have the
323extension .TLS (which is my way of suggesting that you follow this
324convention).
325
326:h3 res=94500 name=PANEL_LOADTOOLS.Load Toolbox
327:i1 id=aboutLoadTools.Load Toolbox
328
329FM/2 allows you to load toolboxes (groups of tools) which were saved
330with the :link reftype=hd res=94000.Save Toolbox:elink. command.
331:p.
332Type the name of the file that holds the toolbox definitions into the
333entry field below the listbox, or select a file displayed in the
334listbox. FM/2 loads the toolbox definitions from the file and updates
335the toolbar.
336:p.
337This allows you to have groups of specific-purpose buttons which you can
338load for different types of activities. You don't have to use it, but
339it's there if you would like to do so.
340:p.
341Clicking :hp1.Okay:ehp1. without typing in or selecting a filename
342results in FM/2 reloading the default toolbox from FM3TOOLS.DAT.
343:p.
344If I may, here's how I'd recommend using this facility&colon.
345:p.
346First, save the full toolbar under a new name (perhaps ALL.TLS). Next,
347delete any buttons that you don't want in your customized toolbar.
348Finally, add any Command buttons that you do want in the customized
349toolbar and save the new toolbox (as <something>.TLS). By starting with
350the full toolbar, you'll spend more of your time deleting buttons you
351don't want (a trivial task) and less adding buttons.
352
353:h2 res=99980 name=PANEL_FLAGS.Drive flags
354:i1 id=aboutFlags.Drive flags
355
356Here you can set flags for various drives. Command line switches
357override these flags. The flags are stored in FM/2's INI file and
358loaded when FM/2 starts, so this is an alternative to all the
359esoteric drive command line switches :hp1.except:ehp1. the
360:hp2.Ignore:ehp2. switch.
361:p.
362:hp6.No prescan:ehp6. Setting this causes FM/2 to :hp1.not:ehp1.
363pre-scan removable drives. You have to double-click the drive
364before it's checked to see if it has any subdirectories. This is
365handy for those of you with CD carousels.
366:p.
367:hp6.Don't load icons:ehp6. Prevents FM/2 from loading icons for
368files and directories on this drive. If the drive contains only
369DOS programs and data files or is a very slow drive, you might
370want to check this one.
371:p.
372:hp6.Don't load subjects:ehp6. Prevents .SUBJECT EAs from being
373automatically loaded on this drive. Again, if your drive is slow or you
374don't use .SUBJECTs with objects on this drive, you might want to check
375it.
376:p.
377:hp6.Don't load longnames:ehp6. Prevents .LONGNAME EAs from being
378automatically loaded on this drive. You've got the idea by now,
379right?
380:p.
381:hp6.Slow drive:ehp6.. Check this for drives which have extremely slow
382seek times (like ZIP and EZ removable hard drives). The Autoview window
383and associated messages are disabled for this drive, and the "Quick Arc
384find" method is always used, whether on globally or not, which snaps up
385response time. I may take other shortcuts for drives with this attribute
386later (loosen error checking). For such slow drives you may also want
387to check the various :hp1.Don't load...:ehp1. flags listed above.
388:p.
389:hp6.Include files in tree:ehp6. If you check this, files will be shown
390as well as directories in the Drive Tree for this drive. I have no
391idea why you would ever want to check this.
392:p.
393You get this dialog by selecting Edit->Drive flags from a context menu
394requested on a drive (root directory) in the Drive Tree or VTree window.
395:p.
396Note&colon. To set the drive flags on a removable drive, like a floppy
397or CD-ROM, be sure you put a disk in the drive first. FM/2 won't let
398you set drive flags on a currently invalid disk.
399
400
401:h2 res=100065 name=PANEL_TARGETDIR.Set Target directory
402:i1 id=aboutTargetDir.Set Target directory
403
404You can set a default Target directory with the :hp6.Set Target
405directory:ehp6. command, which FM/2 will use whenever you use the menu
406or accelerator key commands to move or copy file system objects.
407Otherwise, FM/2 will attempt to intelligently guess what you'd like the
408target directory to be each time based on open Directory Containers or
409the currently selected directory in the Drive Tree.
410:p.
411If you have a Target directory already set and wish to clear it,
412select this command, click Cancel at the :link reftype=hd res=91500.Walk
413Directories:elink. dialog that appears, and answer Yes to the question
414subsequently asked.
415:p.
416See also the :link reftype=hd res=99950.General page:elink. of the
417internal Settings notebook.
418
419.im assoc.ipf
420
421.im command.ipf
422
423.im notebook.ipf
424
425.im databar.ipf
426
Note: See TracBrowser for help on using the repository browser.