[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 297458] dolphin in KDE 4.8.2 keyboard search cannot be reset easily as before
From:       Weng Xuetian <wengxt () gmail ! com>
Date:       2012-04-05 14:01:50
Message-ID: bug-297458-17878-8wJXVwGA6I () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=297458

--- Comment #9 from Weng Xuetian <wengxt@gmail.com> ---
@Frank Reininghaus 
For this, I think move cursor is a bad idea.
Move cursor is not a usefull case, since people can still use backspace to fix
there error. Left and right should always use to move the focus on the selected
item. If there is no blink cursor, people will not think left and right can be
used to move cursor.

There is a bad case in gnome-shell, gs overlay search field is kinds of line
edit, so left and right can be used to move cursor, but how to navigation among
different item? the item is list by horizontal order, but only up and down is
free to use.

And by the way, CJK input method is still a problem here, since they need to
"Compose" before search. If you guys want to replace this function with the
CTRL+I one. CTRL+I have no problem with input method, while the normal one
cannot be used with input method. But for nautilus, the case will be different,
people cannot use keys similar ctrl + i to trigger the input field, so they
must type a useless key to trigger search, and then enable input method with
hotkey, for example ctrl space.

What in my mind is like this: merge two search, both direct key, and the ctrl +
I one. put a visible current search string somewhere, don't make cursor
movable, use qlabel or something similar to display. Normal character key can
trigger it, or ctrl + I can also trigger it. Make sure it accept input method
event, otherwise it will be a drawback for CJK user. For input method, there is
a similar case in mangonel, and I already propose a patch to make input method
preedit works right: http://paste.ubuntu.com/666967/. I think it can also
applied to this case. Left Right, Up and down can be used to move to next match
item on different direction.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]