source: branches/MKIMES/dll/ipf/rename.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: 3.0 KB
Line 
1:h2 res=91400 name=PANEL_RENAME.Renaming
2:i1 id=aboutRenaming.Renaming
3:artwork name='\fm3\bitmaps\rename.bmp' align=center.
4When you rename a file sytem object other than by :link reftype=hd
5res=98200.Direct Editing:elink., or a naming conflict arises, you get
6the Rename dialog. Note that not all the controls discussed appear for
7simple rename procedures -- some are applicable only when copying or
8moving files.
9:p.
10The dialog displays the :hp1.Source filename:ehp1. and proposed
11:hp1.Target filename:ehp1., along with information about both objects.
12:p.
13Below these two fields is an outlined text box that attempts to give you
14directions on what to do (usually to change the target filename -- when
15renaming, the target name is initially the same as the source name). If
16the target file exists, you will be told whether the source is larger or
17smaller, older or newer. You will be told whether the source and target
18are files or directories. Sometimes you may see a warning "cannot
19access source." This means that FM/2 could not open the source file in
20a test, and may indicate that the file is already in use and thus OS/2
21may not allow it to be renamed, moved or copied. You can use this
22information display to make decisions more easily.
23:p.
24After entering the new target name, click :hp1.Okay:ehp1.. If the new
25target name exists, the display will be updated to reflect the new
26information. You can, at that point, enter a new name to avoid the
27conflict or click :hp1.Overwrite:ehp1. (which will destroy the old
28target file, keeping in mind that you can't overwrite a file with
29itself). :hp1.Skip:ehp1. can be used to skip one file when you are renaming
30several in one action; nothing will be done for that file. Click
31:hp1.Cancel:ehp1. if you change your mind and want to abort the whole
32thing.
33:p.
34The :hp1.Rename Existing:ehp1. button allows you to rename (move) the
35existing file system object which is causing a naming conflict. For
36example, if you are trying to copy a file to "C&colon.\MYFILE" and a
37"C&colon.\MYFILE" already exists, you could change the target name as
38desired, click :hp1.Rename Existing:ehp1. to rename (move) the existing
39file out of the way, then click :hp1.Okay:ehp1. to continue the copy
40operation.
41:p.
42The :hp1.Overwrite if target older or same:ehp1., :hp1. Overwrite if
43target newer:ehp1. and :hp1.Don't ask again:ehp1. checkboxes can be used
44in combination to avoid seeing this screen again for naming conflicts.
45Files which have existing targets that do not match an overwrite
46characteristic will be automatically skipped. For example, if you don't
47check either of the Overwrite... checkboxes, all existing files will be
48skipped, but if you check the ...older checkbox, all existing files
49older than the source file will be overwritten, while existing files
50newer than the source file will be skipped. Exception: You will always
51be prompted if you try to overwrite a directory with a file.
52:p.
53Wildcard characters '?' and '*' can be used in the target name --
54behavior is OS/2 standard.
Note: See TracBrowser for help on using the repository browser.