b928: drag & drop operations messed up

[kino]

Hello,

I hate opening an imprecise topic but before I start shooting captures and fine descriptions, I'd like to know if I'm the only one experiencing that :

Drag & drop operations have started to be messed up (without any config changed from my part) as :

• they do not default as before (same disk operations used to move rather than copy, especially if the icon remain the red-backgrounded arrow)

• operation can change between panel and tree (appear as move and becore the blue-backgrounded arrow on tree to become "create shortcut" operation)

• not perform at all or perform other operation: copy instead of move

• etc.

I've suspected it might come from my system/os but Windows file explorer performs normally (if "performs" can be used to speak about Windows file explorer)

Is that behavior identified on your side ? (known issue ?)

Thx.

K.

[Marek]

Please check the release 929.
If you want exactly same behavior as in 926, use the new option "External tool is used for drag&&drop"

[kino]

Hello Marek,
929 fixed it (and I'm fine with FC ops)
Thanks !

[kino]

Hello,
I felt that as a sequel it wouldn't deserve a new topic : I still encounter this faulty behavior -> moving a file to .. (parent folder) doesn't produce any effect in build 929.
Moving to tree panel also is inoperant (a shortcut-alike icon appears at mouse-pointer but nothing happens at the end)
Thx
Xavier

[kino]

Fixed in b930
Thanks !

[kino]

oh well : moving to .. now works but I still have the move to tree panel not working (with some weird "link" alike icon at hoovering in the tree panel)
it produces strictly no effect

[kino]

Problems looks like gone with b931 although not in releases notes.
Either I'm hallucinating or there was a vertuous side effect.
Anyway ; looks good now.
Thanks

[kino]

Hello,

I now have some specifics :

After a while (I haven't identified which event : time ? deep sleep ? ...), move to tree panel folders changes the icon to that small "create link" look alike :

...if I restart FreeCommander, it returns to normal (for a while) :

'hope this helps figuring out what's the cause (?)
Thx
K.