Copy/Move panel: dest filename not focused

[egmont]

A major usability regression is introduced by the (unofficial) UTF-8 patch if mc is compiled with --disable-charset (which is the default).

If you press F5 or F6 to copy or move file(s), it's the "Dive into subdir" toggle that's focused by default, not the destination filename.

Patch attached. Please fix this in the UTF-8 patch. Thanks!

[egmont]

The one-line fix for the problem

[winnie]

This also belongs into the utf8 section and not into 4.6.2.1..

[egmont]

Dear winnie,

Certainly this bug as well as all the other utf8 bugs that I reported belong to the utf8 _section_ (if there was such a field... maybe _component_ but it has no utf8 value), but why the utf8 _milestone_? Maybe I misunderstand what you mean by milestone, but it sounds to me that you've marked the bug as to be addressed whenever mainstream mc is officially going to support to utf8. (Which, according to my knowledge about mc development, is unfortunately quite unlikely to happen in the next few decades.)

Please rest me assured that I misunderstand "milestone" and that you're not going to wait until official support, but will apply my patches to your utf8 patch in the foreseeable future. These patches are so small and trivial that I can see no reason why they couldn't be applied to the very next version of your utf8 patches (4.6.2.1 or 4.6.3).

[Patrick Winnertz]

Hey Egmont,

Please rest me assured that I misunderstand "milestone" and that you're
not going to wait until official support, but will apply my patches to
your utf8 patch in the foreseeable future.

You can be sure that I'll apply your patches in the next future to the utf8
branch. I've switched the branch to get a better look on the release critical
bugs for the next release.. nothing more. If a bug is moved to a later release
this doesn't meant that it can't be included in a earlier one.. it's simply
about not blocking the milestone.
As we doesn't support utf8 currently officially this really shouldn't be a
blocker for the 4.6.2.1 or 4.6.3 release but you can be sure that this (and
the other bugs you've filled about utf8) will be fixed until the next release
happens.. it's only a change to have a better overview about missing things
for the next release.

I hope this helps you :) and much thanks for your work :) please continue ;-)

Greetings
Winnie

[egmont]

Thanks very much Winnie :-)

[winnie]

Patch added into both HACK_utf8 branches

[angel_il]

need check it