Fast find in panels window - strange behavior
Fast find in panels window - strange behavior
I have found some strange behavior when fast find window is closed by clicking mouse outside this window (on panel...). After closing this window, space character is inserted in command line, I must press Escape or Backspace to delete it. I have found older version 4472 and everything is ok there.
-
- Posts: 949
- Joined: Mon 04 Apr, 2005 13:41
- Location: San Ramon, CA / Kharkov, UA
- Has thanked: 3 times
- Been thanked: 12 times
Fast find in panels window - strange behavior
Confirmed. Looks like it is not actually a space character, it is more like a character with code #0.
Far 3.0 build 5312 x86 / Windows 10 x64
Far 3.0 build 5312 x86 / Windows 10 x64
Мы не можем ждать милостей от Фара, взять их у него — наша задача! (C) Мичурин
-
- Posts: 5682
- Joined: Thu 23 Mar, 2006 21:36
- Location: Israel
- Has thanked: 21 times
- Been thanked: 199 times
Fast find in panels window - strange behavior
Probably this:
Code: Select all
drkns 21.07.2018 18:41:29 +0100 - build 5241
1. Null character could not be entered in command line for some reason.
- DrKnS
- Posts: 5125
- Joined: Thu 04 Aug, 2005 06:44
- Location: Kyiv
- Has thanked: 5 times
- Been thanked: 187 times
Fast find in panels window - strange behavior
Ineed, now it could be entered!
The true question, however, is why the fast find emits it in the first place.
Fast find in panels window - strange behavior
Thanks for the quick correction. But there's another very bad thing. When I display the fast find window and type several characters, cursor in panel moves correctly to typed folder. But when I press Enter, fast find window disapears, but Enter is ignored, instead of the change directory. I must press Enter two times. This is the difference in new version and old version. Because of it, some macros stopped working. There are two possibilities - I may rewrite macros and press Enter two times or you take back older behavior.
Fast find in panels window - strange behavior
Far 5319, the problem has arisen again. Or am I doing something in a wrong way?