Summary: | hardcoded shortcuts in katesearchbar.cpp interfere with applications using katepart | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Thomas Braun <thomas.braun> |
Component: | part | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | thomas.braun |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Thomas Braun
2009-04-05 14:24:24 UTC
How to use KAction and still have actions only bound to this widget? Hmm, to get the actions to show up inside the shortcut config dialog you'd have to add them to the actioncollection of the xmlguiclient (i.e. the view IIRC). However that means that they'll be associated with the view and if you then use the widget-with-children context those actions can be triggered even if the searchbar is not shown and just the kate view is active. So I fear the only way to help the kile people is by bringing back that dreaded "shortcuts" page in the editor config pages and put these shortcuts there. Hmm, perhaps I should just remove them, I don't see the need to switch this modes for searching every 5 secs, that such prominent shortcuts must be taken, or? SVN commit 961399 by cullmann: remove the ALT-1/4 shortcuts even if we later introduce them as actions, remove the hardcoded ALT-* text from the combobox before string freeze BUG: 188879 M +4 -4 dialogs/searchbarpower.ui M +2 -0 utils/katesearchbar.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=961399 Thanks a lot! You are the hero of many kile users :) No Problem, sorry for the regression. Hardcoded shortcuts are no good idea, and for such prominent onces especially :( |