@Swoop
Quote:
Why do I need to use the path command?
Your icon has "TurboCalc" as default tool. Without path.
Then Workbench will search TurboCalc in the current
directory (where the project file is located) first
and fall back to the search path which is defined by
the Path commands in Startup-Sequence and User-Startup.
When it worked before, either your project file was
located in the same directory as TurboCalc, or your
S-S and U-S defined a search path that included the
directory which contained TurboCalc, or your icons
contained the full path to TurboCalc.
Quote:
Why does the assign command not work without it?
The Assign command is something completely different
than the Path command.
Quote:
Why did my previos assign not work?
It worked. It just did not have any effect on the search path...
Quote:
Why did I get an error message when double-clicking on a project icon?
Because Workbench could not find TurboCalc in the current
directory or in the search path.
Quote:
The only way to get the double-clicking to work, with the
same result as previous OS versions, was to add a path
command, and remove the file from the end of the assign.
Yes. Because it has nothing to do with the Assign command.
Quote:
If an assign is (under OS4) not automatically added to the
path, how is that an improvement?
No need to ask for an improvement. It works as before.
Quote:
The whole point of an assign is that AmigaDOS is aware of
the assignment. Regardless, of whether the assign command
was developed for floppies, its main use is by programs
adding an assign to user-startup when they are installed,
to make the OS aware of where they are located.
Right. Partly. Assigns are not only used for locating
programs but also for locating data. There e.g. exist
FONTS: LOCALE: PRINTERS: CLASSES: HELP: LIBS:
Quote:
If that now doesn't work, without using a second (path)
command it seems a backward step IMO.
There was nothing changed. Ergo no step backward happened.
Even OS3 was smart enough to NOT waste time by searching
a program in FONTS: or LOCALE: ...
Quote:
I am not trying to be a pain. I am just trying to
understand why such a change has been made.
No change happened.
Quote:
If it hasn't been changed, what is the correct syntax
of the assign command, that will correct my error messsage
without requiring the use of the path command.
There exists no possibility to use the Assign command
to change the search path for programs. The Path command
is used to specify the search path. Ok, an indirect possibility
exists, by modifying assigns which are part of the search path.