excellence! 3.0 buglet
15 messages in this thread
I found an excellence 3.0 buglet that was "added" since 2.0. When I go to
open a file using the requester, and the file is in a drawer whose name
contains and apostrophy (e.g. Joe's) the file fails to load and the file
requester clears all files from its window except the one originally
selected for loading.
Note that the same file (having been created with excellence 2.0 or
earlier) loads up just fine if I double click its icon. I don't believe
this problem exists with ASL, Khalid's FR, or the older MSS file loading
routines.
wmc
Yes, we know about that. It's any non alphanumeric character (we discovered
it while working on the french version. The biggest problem it causes is
with GVP hard drives since they've got some kind of brackets in their
default names.
I need to find out what we're going to do about it, I'll post here as soon
as I know.
Well, actually it's not non-alphanumeric, it's character which also serve
some purpose in AmigaDos. And yes, though hardly anyone uses it, the
apostrophe is an official AmigaDos character. So are parenthesis, not
symbols ~,vertical bars, etc. I don't even remember what the apostrophe
does, but Steve remembered it. It's the routine that decides if you're
entering in a file or a pattern from the file field. You can enter patterns
(just type in #?.asc, for example. But this means that you can't name your
files weare#1, tobe|nottobe, etc…
Andrew,
Actually…AmigaDOS will gleefuly accept a filename with #? in it.
I goofed up on an LZ command line last night and created a file called
#?.lhz. Luckily I had no other .LHZ files in that directory so a delete
#?.lhz got rid of it.
Don
Yeah, it'll accept it, but using them can cause trouble. Anybody out there
remember what purpose the apostrophe ' character serves in AmigaDos?
Andrew,
I don't recall the apostrophe meaning anything to AmigaDOS, but
could certainly be wrong. Somewhere around here, I've still got the
original AmigaDOS reference manuals (the white ones from Commodore…not
from Bantam). I'll see if I can dig them up and see if they mention
anything.
Don
It's one I had never heard of until discovering it while doing the french
version (you can imagine how common apostrophes are in french filenames),
and asked him about it, and he dug up some obscure manual and showed me
what it was supposed to do. He pulled it from the french version, but at
the time we hadn't realised that the situation also applied to volume
names, which is the cause of most of the problems, since GVP hard drive
names default with parenthesis, which can be used in patterns.
Andrew,
I found it…in the original AmigaDOS User's manual, under the LIST
command, it lists the special characters '()?%#| and then goes on to
explain that the apostrophy removes the special meaning from the other
characters…thus a '# means a literal #.
It's also in the Bantam version of the AmigaDOS manual for v1.x,
but I don't find it in the Bantam version for AmigaDOS 2.0
Don
Yeah, but we had to write it for 1.3 and 2.0. It IS a problem, though, and
will be addressed. That list of characters is the same list (with the
addition on ~, I think, that the routine checks for to determine if it is
looking at a pattern.
We need to allow these char's, but still have some way to signal a pattern.
We looked at using a text gadget for the pattern, but much preferred the
cycle gadget…. Any suggestions?
Andrew,
Look at file requesters that have a separate text gadget to
indicate what patterns (if any) should be looked for. Then, of course,
honor only files that match that pattern, else show everything.
Don
Yeah, I guess we're going to have to do something like that. Thanks for the
info.
"Any [FILE REQ] suggestions?"
Andrew –
Yes. Dump the custom FR and use the ASL. That way users, if they choose,
can run KD_FREQ or MAGIC_FR or any file req they choose!
Michael
…..from the north coast
We didn't use ASL itself for several reasons, including look, gadgets, and
workbench 1.3. I'm not familiar with KD_FREQ or MAGIC_FR, where can I find
out more about them?
Andrew,
Out of curiosity…I just tested it. In RAM: I created the file #
via the ECHO ># command.
I then tried a DELETE # command and nothing was deleted. So I
tried a DELETE '# and the file was removed (and only that file <grin>).
Don
Great. I knew it was in there somewhere.