Run-time error 380 when deleting files

[zridling]

In beta version 5.10.0030, I keep getting a persistent runtime error, which forces me to close XYplorer whenever I:

(1) Have the Preview pane open, and
(2) Select files using the SHIFT+End key and then hit Delete.

It happens about 50% of the time which makes me wonder if it's not something specific to my system. However, I don't receive the same error with other file managers. It makes no difference the number of files; sometimes it is as few as 50, and at other times it happens when I'm deleting thousands.



I'm running WinXP-SP2 with 4G of memory and updated VB Runtime files.

[admin]

In beta version 5.10.0030, I keep getting a persistent runtime error, which forces me to close XYplorer whenever I:

(1) Have the Preview pane open, and
(2) Select files using the SHIFT+End key and then hit Delete.

Cannot reproduce. Need more infos. Is any file previewed when you Delete. If yes, what kind of file.

SHIFT+End key ... this will hardly be the cause of it. Can it be you still have the Shift key down when you hit Delete?

(got to leave now --- )

[zridling]

Here is a png with the layout when this happens:

http://www.anova.org/target/xyplorer/xy ... 0error.png

I only notice this happening when previewing photos, namely, JPGs and PNGs. And the SHIFT key is released before hitting Delete. Then XYplorer closes, but I can open it right back to the same folder as if nothing happened (again, which with the slashed lines through the Catalog and Address bar makes me suspect my system — hardware conflict, bad driver, etc.) rather than XYplorer.

If you can't reproduce it, then don't worry about it. It's not a big deal.

[admin]

Zero tolerance for runtime errors! This one was quite tricky to catch but I finally cornered it. Your screenshot helped a lot, because the source of the error was actually the "List" view, which, as you know, I made quite recently so no wonder there are some glitches left.

The 50% crash rate you experienced comes from the complex conditions of the bug where the current column position of the "List" view and the column count after the deletion played a role.

... slashed lines through the Catalog and Address bar ...

Nothing with your system. The slashed lines are a peculiarity of crashed VB programs and shown only over the so-called "UserControls". It's rather meaningless because the app is dead already when the lines appear. Kind of an application body bag I guess.

[zridling]

Wow Don, I'm impressed. I worked around it by merely deleting all but the last file in a folder, and then deleting the last one next. Best of all, the fix works. Thanks!