Am 26.12.2011 12:25, schrieb George Gwilt:
I have just used QD to examine a file with the longest possible name. The name
was actually
ram1_abcdefghijklmnopqrstuvwxyz123456_wda. Although QD displayed the contents
of the file correctly, it did so with a purple coloured ink. This ink was set
for all other files read in provided the name was not of maximum length. The
file ram1_abcdefghijklmnopqrstuvwxyz12345_wda1 reset the colour to a rather
fainter, almost unreadable, purple.
Is this a new feature of QD? Has anyone noticed this before?
George
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
George,
looks like you've found a bug in QD - The same for me here (well, the
color is not exacly purple, but some oddly stippled brownish green).
Looks like the long filename overwrites some of QD's internal storage
for the ink color. And I remember there were some discussions in the
past what /exactly/ is the longest allowed filename in QDOSSMSQ (i.e is
the device part part of it or not).
Interestingly, if you start QD with the very same long filename from the
command line (i.e ex qd;<verylongname>) it refuses to save the file
("Not found") in my setup and doesn't produce any other quirk. It looks
to me as if there's a mismatch in allowed filename length between QD and
the Menu extension.
Will try and keep my filenames short enough in the future ;)
Happy new year to all of you
Tobias
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
