"Erroneous" node being automatically produced

[Happy Expat]

WIN XP(SP3) 32 bit - LBC 1.137.01
If I attempt to add (DRAG) Shortcuts for documents held in another user account directly into a FOLDER node on the active LB in the currently active user account, it produces an "Access violation at address 00417236 in module 'LBC.exe'. Read of address 0000008E." I assume this is correct because I shouldn't really be able to do it - the shortcut should go into the target folder to which the node refers - I realised I was actually making an erroneous attempt in the first place. However, if the same shortcut is dragged to the same FOLDER Node in the opened Configuration pane, which would also be the same error, then it produces a new Node which is a copy of the node immediately below the target including all the elements within the "copied" node. This "NEW" node being inserted between the erroneous target and the copied node. In this instance the copied node was a MENU node, I haven't tried to simulate the error with all possible node permutations.

[mouser]

Hmm, sounds like we have a bug somewhere.. An Access Violation error is never the correct behavior
I may have to try to send you a debug version to help me pinpoint the issue.
I didn't fully understand what you were saying happens in the second case..

[Happy Expat]

Ok. I'll also run the whole scenario again taking screen dumps to illustrate. Or would you prefer a desktop video like some of the ones I have seen posted by you?
What package did you use for yours?

[Happy Expat]

The access violation error never occurred again so it's probably a local environment glitch.
Just tried twice to attach a video demonstrating the feature but the forum server keeps dropping me.
The .avi file is 24.6 MB, could that be some kind of file size violation? Is there another way to get it to you?

[mouser]

yeah that's too big for a forum attachment.
can you upload it to one of the free hosting sites or maybe http://www.screencast.com ?

The access violation error never occurred again so it's probably a local environment glitch.

More likely it's a bug in the program that is just hard to trigger.

[Happy Expat]

As a newbie I messed up the link. See below for the replacement

[Happy Expat]

I've just noticed from watching the video again that the second cut & paste - with the node open "picks up" the attributes from the the second node below in addition to replicating the erroneous node.
That is it contains both the active utilities objects and the active software objects.
Now that's pushing the envelope!

[Happy Expat]

Let's try again - here's the download link. Let me know if I should embed the video instead.

[mouser]

Ok I watched the video -- thank you for taking the time to make that -- that makes things quite clear.

What a strange bug -- and one i need to fix immediately -- I'll try to have a new release out this week.

By the way, that's an awesome accent and speaking voice -- I almost felt like i was listening to David Attenborough narrate a wildlife documentary.

[Happy Expat]

It was my first attempt so it felt like I was facing down a tiger.

[mouser]

It was my first attempt so it felt like I was facing down a tiger.

[mouser]

Can you try this beta and let me know if it solves the problem:
https://www.donation...arCommanderSetup.exe
https://www.donation...ommanderPortable.zip

ps1.
if it's any comfort, the bug you found only effects the DISPLAY of the tree of nodes until the next time you open the options.. it doesnt actually corrupt the internal data.

ps2.
it seems like the bug is actually quite a bit more commonplace than your one case suggests -- it actually seems to happen whenever you drop in a child file item in the middle of a parent's children, above another child which is expandable.

[Happy Expat]

 I can confirm my case is fixed.

Now that you're simply creating a new appropriate node I can't imagine you need me to test for any further combinations that might cause exceptions. And of course, if a newbie  does it wrong I can just delete the surplus node without fear of tragic consequences

ps1 Phew, that was lucky, can you imagine the fix effort if it was corrupting the data as well.

[mouser]

ps1 Phew, that was lucky, can you imagine the fix effort if it was corrupting the data as well.

i have nightmares about such scenarios.

no further testing needed.

thanks again for the report and video