[BUG] Small thing - no warning for failed file move operation.

[onehandclapping]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

When attempting to move a mod to another collection where that mod already exists there is no warning when the move fails.

Expected Behavior

Just a dialog that says "Move Failed" or some such.

Steps To Reproduce

No response

Environment

- Mod Assistant Version:4.05
- OS:W10
- Virtualized:No

Anything else?

No response

[jtsage]

which move method? (from a "regular" collection, or from a "favorite" or "holding pen" collection? or drag-and-drop?) The behavior on all of those is slightly different.

For instance, the holding pen one should just do it anyway, overwriting the existing.

From a standard collection, it should sort of warn you - it'll be in the list of things to move, along with a checkbox to overwrite anyway.

But I will do some testing and make sure it is working as intended, thanks!

[onehandclapping]

Sorry for the late update, my 3070 failed and had to be replaced (by a 4070 wahoo).

Just a simple move from one "regular" to another. Selecting one or more mods and then clicking the "Move To" on the right.

[jtsage]

sorry for the delay, been busy. I'm not sure I can replicate this

This is a file that already exists where I want to move it - if I don't hit the check mark, it does nothing. If I do, it overwrites the file as expected. But you are correct that there is no user-facing acknowledgement that (in this case) "1 file(s) will be skipped". I could add something like that text to the button probably

[jtsage]

added a bit that says how many will be affected.

[jtsage]

this is fixed in the testing version, there is visual feedback if anything failed.