[Bug v6.01] Cancelling a Drag-and-Drop to a Tab

[Randy]

This bug is consistently reproducable.

Steps to replicate:
1. Select 1 or more files.
2. Drag files to another tab on either pane (do not drop them).
3. Hit the esc key.

Expected Results:
Drag-and-drop procedure is cancelled, files remain selected.

Actual Results:
"Access violation at address 004BCC4E. Read of address 00000224."

Notes:
1. If one continues execution, the bug does not occur again until the app is restarted.
2. Running Windows XP SP1, Athlon proc, 1g PC2700.

[Clo]

2Randy
Hi Randy,
¤ Please, watch there:
http://ghisler.ch/board/viewtopic.php?t=2817 at page bottom,
from which you will can see the same error address, though it wasn't the same handling...
Kind regards,
Clo

[djk]

2Randy
Confirmed. (also XP SP1)

[Lefteous]

Tested on

Win 95: No error message
Win 2000: No error message
Windows XP: error message

[djk]

Windows NT: error message

[ghisler(Author)]

I think that I found the problem: Windows sometimes returns a tab index of -1 instead of the correct tab index. I'm currently investigating and will release a new version when I have fixed the error.

[Ivan Moratinos]

I've found another bug related to tabs. I am running Windows XP Home Edition. These are the steps to reproduce the error.

-Click with the mouse on a tab in the left pane (near the top right corner)
-Drag the tab from the left pane to the right one. If you have clicked accurately, the mouse pointer doesn't show a non-parking sign (as it used to do if you click on the name of the tab in order to drag it)
-When the mouse reaches the right pane an AV occurs. Something like:

Access violation at address 004BCC4E. Read of address 00000224.
Please report ...etc

Can anyone confirm this?

[Ivan Moratinos]

I've found another bug related to tabs.

Well, I should say: I've found another way to reproduce this bug

[Jqn]

Yes, in WinNT it also crashes. CONFIRMED.

But you MUST click near the top right coner of tab name.

Joaquin

[Clo]

2Ivan Moratinos
Hi!
¤ This is the same error address for any handling which causes this access violation; I think that the Author's answer is valid for your case too...
¤ I'd this twice, loading a *.tab file...

Kind regards,
Clo

[ghisler(Author)]

Yes, seems to be the same problem indeed.