update 2 - found a regression in copy

[Raziel]

The "copy" dialog window on WB (when i drag&drop files)
(I'm not sure if it's ASyncWB or C:Copy or something else)

When i copy large files/directories i get artefacts of the drop shadow of the copy dialog window, most visible on the top right drop shadow (the windows upper border).

Another problem is the intermittant activation of the window (even if it *is* already active), the whole window keeps "flickering".
This seems to cause the drop shadow artefacts.
You can even see the whole dropshadow becoming a black "block" aroundthe window for a short time.

One other thing is, that even if the same file (big one) is copied and the name in the top border stays the same, the name is also constantly updated, as is the progress bar, the whole window is constantly "flickering".



ASyncWB 53.33 (22.12.2020)
C:Copy 54.5 (05.03.2021)



My GUI settings are (if that helps?)
- Compositing on
- Optimize for Performance
- Syncronize with vertical refresh

drop shadows
X 6 Y 6
Smoothness 6
Active 75
Inactive 50

Any advice?

[TearsOfMe]

Wrong Forum for your bug report, when you use the Enhancer copy and not the OS one, like it seems.
Try the original copy and look if the problem go away.

[Raziel]

Heh, indeed

edit:

otoh...
is C:Copy responsible for opening the copy *window* when i drag and drop stuff (i thought it is only used for shell copy stuff)?
Or is it rather part of ASyncWB/DOSLib (which would be back at Hyperion then)?

[TearsOfMe]

Okay, i try your gui settings here on my X1000 with latest Update and can not reproduce it.
Here all looks fine, no flicker.

[nbache]

is C:Copy responsible for opening the copy *window* when i drag and drop stuff (i thought it is only used for shell copy stuff)?
Or is it rather part of ASyncWB/DOSLib (which would be back at Hyperion then)?

The d&d copying process of Workbench is handled by ASyncWB (if that commodity is started, which it normally will be). It has nothing to do with C:Copy.

Artifacts like the ones you describe can be caused by other components, though, e.g. the graphics driver. Which graphics card are you using, with which driver/version, and on which machine?

Best regards,

Niels

[Raziel]

@nbache

Thanks for the answer

Found it, caused by the screen updates of CANDI

[nbache]

Why am I not surprised ...

Best regards,

Niels