Re: Java and avoiding software piracy?

On Jul 20, 5:25 am, Andreas Leitgeb <a...@xxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
Oliver Wong <ow...@xxxxxxxxxxxxxx> wrote:
It's easy to reproduce. Make two dummy directories with a load of
dummy files in each and drag files back and forth for a while. Within
20 or so you should get an instance of one jumping to the bottom of
the list instead of going where you dropped it and where the I beam
indicated it would go.

Can you produce a screencast demonstrating the problem? I can't
reproduce your bug on my WinXP SP2 machine.

I think to remember that Windows tends to show just-recently-modified
files at the end of the list. So if you copy (or move between
different logical disks) largish files, it might happen that while
copying is still in progress, the file's name might be moved to the
end of the list in explorer.

1. This occurs moving files within a single logical drive.
2. Regardless, Explorer isn't supposed to drop files anywhere but
where the I beam indicates; the I beam is a UI promise to the user
that the inserted item will appear at that location, and any deviation
from such behavior is therefore ipso facto a bug.
3. Files go at the end when they are not dragged and dropped, but
instead were moved by an asynchronous process (e.g. a program moved it
in the background; the user moved it via DOS box command; the user
moved it to another window open on the same directory, which should
drop it where dropped in that window and cause it to appear at the
bottom in the other). This makes me suspect that Explorer is sometimes
losing track of the fact that the move was caused by a drag operation
to the affected window. In any event, random and inconsistent behavior
is a bug wherever it's not explicitly a feature instead. Undocumented
such behavior is therefore ipso facto a bug.
4. UI behaving differently depending on how much time an operation
takes is bogus, save where the difference consists solely in whether a
progress dialog/bar is shown, how fast a progress bar moves, and how
long the UI takes to display the state expected after successful
completion of the operation.
5. Even supposing the directory is sorted by modified date, a) moving
a file isn't supposed to change the modification date! and b)
automatic resorting isn't supposed to happen anyway. If it were, it
should presumably do so consistently i) always or ii) when and only
when some relevant box somewhere was ticked, as opposed to iii)
whenever it felt like it

I'm a dedicated windows-hater, but frequently notice that I still
know it better than most self-entitled windows-lovers/experts.

Probably because you know the bugs and the lovers turn a blind eye to
the same.


.

Relevant Pages

  • Re: How did you learn your debugging skills?
    ... > trace points in the program, and use them to narrow down where the bug is. ... A common manual debugging technique is a temporary trace statement, ... A window controlled by a Test Case is the same kind of thing - a simple I/O ... the window-the fixture that usually suppresses it. ...
    (comp.programming)
  • Re: Outline pane STILL clips text horizontally in 2004
    ... I just wanted to add that I created my own web page for this bug. ... > views so that the window pane sizes can be adjusted to your own personal ... > will find a point at which the text in the outline does not flow the way you ... > leave things as they are since it's easy to adjust the frame divider. ...
    (microsoft.public.mac.office.powerpoint)
  • MoreDesk version 1.16 available
    ... MoreDesk version 1.16 is now available to try or buy from the 7th software ... Added the Socket Manager's 'keys' window to the Ignore list. ... Bug fix: dragging directories/applications to MoreDesk for the desktop ... interactive help for the statistics window was incorrect. ...
    (comp.sys.acorn.announce)
  • *Another* MoveDown bug in Word?
    ... I think I have come across another MoveDown/MoveUp bug in word. ... The Word window height less than 1/2 the height of the vertical screen ... resolution. ...
    (microsoft.public.word.vba.general)
  • Server Crash (2.6.17-1.2157)- BUG: soft lockup detected on CPU#3!
    ... I just installed Fedora Core Kernel 2.6.17-1.2157_FC5smp and immediately got a "BUG: soft lockup detected on CPU#3!", I've never had this on any other kernel version before, but on my desk top PC and now this server with this specific kernel. ... isg-dev7 kernel: CPU: 3 ... kernel BUG at include/linux/list.h:185! ... MEM window: dd200000-dd3fffff ...
    (Fedora)