[Prev][Next][Index][Thread]
Re: E/D 1.99l bugs (mostly browser)
>>>>> "Ernst" == Ernst J Oud <ernstoud@euronet.nl> writes:
Howdy Ernst,
Everyone: it turns out that it's fairly easy to corrupt .hfv files
when using the browser. One way that I know is to try to move a
folder into one of its ancestors. As such, you should be very careful
when using the browser under 1.99l. These bugs are top priority over
here and they are one more reason why we'll be working hard to get
1.99m out soon (we've already fixed some other annoying bugs).
The mail software we use over here automatically rewraps paragraphs,
which in general is nice, but i fyou have separate points adding a
blank line between them makes it easier for us.
Ernst> Apart from bugs that have been reported already I noticed
Ernst> the following, mostly browser related:
Ernst> - when using HFS_Xfr to copy files, E/D 1.99l crashes when
Ernst> HFS_Xfr is exited
Logged as Problem Report (PR) #876
Ernst> - twice I have corrupted a volume; this has not happened
Ernst> to me a long time
The only way we know how to reproduce this is by moving a file into
its ancestor or sibling (Logged as PR#933). If you come up with any
other way of doing this, please let me know. Obviously there
shouldn't be *any* way to do this.
Ernst> - I managed to copy a folder with the browser between
Ernst> volumes. it did not show up on the new volume so I guessed
Ernst> I had done something wrong. I did it then again and
Ernst> suddenly i had two identical copies of the folder on the
Ernst> destination drive! I tried to delete one and then both
Ernst> where gone.
This could be a result of doing something that normally would work,
but doing it on a corrupted filesystem. If you can reproduce this
type of problem on a filesystem that you haven't done any moves on,
then this is an additional bug for us to track down and we need to
know about it.
Ernst> - when copying I get a lot of ERRORs -43 (File or Folder
Ernst> not found)
Some may be caused by HFV corruption. It also turns out that you'll
get these when you delete files, even though the files will delete
successfully (PR #936).
Ernst> - when I have accessed an icon it gets squares surrounding
Ernst> its graphic and its text; this looks very ugly
We're open to suggestions on nicer ways to hilite the currently
selected object.
Ernst> - when the ribbon is selected; a sort crashes the browser
Ernst> and E/D
I couldn't reproduce that one. If you can supply an exact set of
things to do, starting with a fresh copy of E/D 1.99l, that will
produce the crash, we can probably fix it.
Ernst> - the ribbon-ends do not tell in which direction there are
Ernst> more icons
PR #930
Ernst> - one can ask 'Get File Info' of a folder; it then gives
Ernst> nonsense
Noted. PR #937
Ernst> - why do windows open with the size of their parent and
Ernst> why are they positioned just below the menu bar of the
Ernst> parent? I don't know but to me it looks so ugly. The
Ernst> Windows idea of opening a child a bit down and to the right
Ernst> of the parent is much nicer.
We used to do things that way, but Bill changed it at the last minute.
He's not around to ask right now, but if people want it changed back,
we can do that.
Ernst> - the intensity difference between normal and dimmed menu
Ernst> entries is on my machine barely visible; I lighther grey
Ernst> for dimmed should be used
I haven't logged this as a separate problem yet, since it may just be
a manifestation of an existing problem (colors being too dark in
general; wasn't logged, but is now PR #938).
Ernst> - AuthorWare Working Module used to work; it now crashes
Hmmm... is there a shareware or demoware copy of this that we can look
at? I know a GIF viewing program broke (and has since been fixed)
between 1.99k and 1.99l, but if we can't get a copy of this software,
we may need to have you send in a traceback.
Ernst> Will test a lot more this evening but first I have to make
Ernst> some dummy volumes; I am not letting E/D loose on my
Ernst> existing volumes since they might crash.
Right. Good plan. Thanks for the bug reports.
Anyone who is interested in problem reports can query our bug report
database by sending e-mail to "query-pr@ardi.com". Your subject line
should be the arguments to "query-pr", "--help" gives you a list of
what arguments you can give query-pr. Problem report numbers reflect
the total number of problem reports ever sent in, not the number of
outstanding problem reports. Most problem reports that have easily
repeatable directions are closed out by the time the next release
comes out.
--Cliff
ctm@ardi.com
Follow-Ups:
References: