This forum has been archived. All content is frozen. Please use KDE Discuss instead.

kopete - search in input field

Page 1 of 1 (15 posts)

Tags: None
(comma "," separated)
julkip
Registered Member
Posts
12
Karma
0
OS

kopete - search in input field

Wed Feb 09, 2011 11:36 am
Hi,

i noticed that i am no longer able to type / in the input field in kopete. When i do so i get a search menu. The only way to type it is by using the num-pad, but my laptop doesn't have that. I use the neo2 keyboard layout if it is of any help to you.

Thanks in advance.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: kopete - search in input field

Wed Feb 09, 2011 10:20 pm
If you type "/" in other input fields, such as the Dolphin search bar, Konqueror address bar, or KRunner, do you get context menus appearing or does it function as expected?

KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
julkip
Registered Member
Posts
12
Karma
0
OS

Re: kopete - search in input field

Wed Feb 09, 2011 10:38 pm
Dolphin and KRunner work just fine. Konqueror shows me the same context menu i get in kopete.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: kopete - search in input field

Wed Feb 09, 2011 11:30 pm
Please use a program such as "xev" to ensure that the "/" key is not sending more than one key press event. In addition to the "/" it could be sending another key press which is triggering the menu.

KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
julkip
Registered Member
Posts
12
Karma
0
OS

Re: kopete - search in input field

Wed Feb 09, 2011 11:45 pm
Here is the relevant output from xev:
KeyPress event, serial 34, synthetic NO, window 0x4a00001,
root 0x15a, subw 0x0, time 10016443, (-703,-373), root:(483,279),
state 0x0, keycode 51 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x4a00001,
root 0x15a, subw 0x0, time 10016507, (-703,-373), root:(483,279),
state 0x80, keycode 39 (keysym 0x2f, slash), same_screen YES,
XLookupString gives 1 bytes: (2f) "/"
XmbLookupString gives 1 bytes: (2f) "/"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x4a00001,
root 0x15a, subw 0x0, time 10016563, (-703,-373), root:(483,279),
state 0x80, keycode 39 (keysym 0x2f, slash), same_screen YES,
XLookupString gives 1 bytes: (2f) "/"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x4a00001,
root 0x15a, subw 0x0, time 10016675, (-703,-373), root:(483,279),
state 0x80, keycode 51 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False


I don't see anything wrong with it.
For comparison, here is the output with normal german de layout (which works just fine in konqueror and kopete)
KeyPress event, serial 34, synthetic NO, window 0x4a00001,
root 0x15a, subw 0x0, time 10165491, (452,-276), root:(1638,376),
state 0x2000, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x4a00001,
root 0x15a, subw 0x0, time 10166019, (452,-276), root:(1638,376),
state 0x2001, keycode 16 (keysym 0x2f, slash), same_screen YES,
XKeysymToKeycode returns keycode: 39
XLookupString gives 1 bytes: (2f) "/"
XmbLookupString gives 1 bytes: (2f) "/"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x4a00001,
root 0x15a, subw 0x0, time 10166075, (452,-276), root:(1638,376),
state 0x2001, keycode 16 (keysym 0x2f, slash), same_screen YES,
XKeysymToKeycode returns keycode: 39
XLookupString gives 1 bytes: (2f) "/"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x4a00001,
root 0x15a, subw 0x0, time 10166235, (452,-276), root:(1638,376),
state 0x2001, keycode 62 (keysym 0xffe5, Caps_Lock), same_screen YES,
XKeysymToKeycode returns keycode: 50
XLookupString gives 0 bytes:
XFilterEvent returns: False
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: kopete - search in input field

Thu Feb 10, 2011 9:51 am
Assuming you only pressed the slash key, then what I suspected is confirmed, as two sets of Press/Release events are shown in both.

In the first, ISO_Level3_Shift then slash keys were depressed, then released in reverse order.
In the second, Shift_R then slash were pressed, followed by slash then Caps_Lock being released.

Assuming you pressed only one key for both, and did not include the output of other buttons pressed, both layouts contain bugs.

KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
julkip
Registered Member
Posts
12
Karma
0
OS

Re: kopete - search in input field

Thu Feb 10, 2011 10:36 am
I press 2 keys in both layouts and i intentionally included those in the quotes
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: kopete - search in input field

Thu Feb 10, 2011 10:41 am
It is probable the keycode ISO_Level3_Shift is causing this, as the functional layout uses the Shift_R keycode instead. Please consider adjusting your keyboard layout.

KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
julkip
Registered Member
Posts
12
Karma
0
OS

Re: kopete - search in input field

Thu Feb 10, 2011 10:47 am
no way ;)
that would be like advising to switch to gnome instead. won't happen ;)
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: kopete - search in input field

Thu Feb 10, 2011 9:55 pm
Your only solution then in this case is to hope to find an accessibility or otherwise global shortcut in System Settings > Shortcuts & Gestures or System Settings > Accessibility which allows you to adjust this behaviour.

KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
uiae
Registered Member
Posts
1
Karma
0
OS

Re: kopete - search in input field

Tue Mar 01, 2011 6:04 pm
have you found a solution? i have the same problem... it's really annoying... especially if you are a uncertain guy like me :-/
:-D
julkip
Registered Member
Posts
12
Karma
0
OS

Re: kopete - search in input field

Wed Mar 02, 2011 4:45 pm
no solution yet, sorry
i am still searching

oh and btw
just by looking at your username i can tell that you are using neo :)
julkip
Registered Member
Posts
12
Karma
0
OS

Re: kopete - search in input field

Thu May 05, 2011 11:47 am
Well, its not the most elegant way to prevent this but in the meantime i have adopted the use of mod4+9 for / in kopete…
plc
Registered Member
Posts
1
Karma
0
OS

Thanks

Sat Jun 18, 2011 9:20 am
Ah.. I just shifted to Neo 2 as well, and actually thought that the "/" behaviour was some grossly misunderstood UI feat on QT's behalf or something - But thank you all for setting the matter straight, and pointing out a workaround :-)

(hehe, it also happens in the adressbar and in input fields in the rekonq browser.. pretty distracting for urls :p)
julkip
Registered Member
Posts
12
Karma
0
OS

Re: kopete - search in input field

Wed Aug 03, 2011 12:16 pm
I just upgraded to KDE 4.7 and the problem is gone. In kopete at least!
Konqueror still wants to search when i type mod3+i in the addressbar, but since I don't use konqueror… i'm quite happy ;)

Page 1 of 1 (15 posts)

Bookmarks


Who is online

Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]