Хотелка: добавить убирающуюся панель со списком найденных фраз.
То есть чтобы работало примерно как фильтр строк, а при выборе строки в списке прокручивало к соответствующему месту в документе.
И альтернатива списку – отметки рядом с полосой прокрутки на месте найденного. Пример – реализация поиска в Google Chrome или в Firefox с расширением XUL/Migemo (скрин, вообще говоря, расширение не без глюков, но почти все можно поотключать ).
P.S. Особо наблюдательные могут заметить на скрине еще и регулярки.
Posted: Sun Apr 03, 2011 3:15 pm
by sum1
Hello,
Sorry I don't know Russian.
AkelPad v4.5.6
QSearch v4
I reassigned F4 to "FindNextUp" in Hotkeys plugin:
IDM_EDIT_FINDNEXTUP Command(4160) F4
But once QSearch plugin is called, pressing F4 will do "FindNextDown".
Posted: Thu Apr 07, 2011 8:21 am
by DV
sum1 wrote:IDM_EDIT_FINDNEXTUP Command(4160) F4
But once QSearch plugin is called, pressing F4 will do FindNextDown".
I understand the problem. Will be fixed in new version of QSearch.
Posted: Fri Apr 15, 2011 6:13 pm
by Lain25
Hello,
I'm not sure whether this is the right place for my problem, but most likely it has something to do with QSearch plugin. I'm from Poland and in polish language we have character "ą" by pressing (right) Alt key + letter "a". When I press this combination in QSearch panel at the bottom of the AkelPad window, it erases all letters typed before it, leaving only "ą". So when I try to search for a word, for example, "gorący", I type "g", "o", "r" and alt+a for "ą" and the moment I put it in "gor" vanishes and I'm left with only "ą". Maybe it can be tweaked somewhere and I just don't see it?
I'm using AkelPad 4.5.6 (x86) and QSearch 4.0
Posted: Fri Apr 15, 2011 10:00 pm
by KDJ
DV
I confirm, what Lain25 wrote.
Pressing rightAlt+A, clears the edit control in the combobox.
Posted: Sat Apr 16, 2011 8:21 am
by FeyFre
rightAlt also known as Grey Alt and in term of Microsoft is equal to pressing simultaneously Ctrl and Alt. So it is not miracle if GreyAlt+A could mistakenly thread as Ctrl+A(ie select all text). DV, you should check VK_MENU state also in your editWndProc(and all other modifiers too).
PS. pls, fix 0x41 -> VK_A
Posted: Sat Apr 16, 2011 11:16 am
by DV
FeyFre wrote:you should check VK_MENU state also
Usually all the combinations with Alt key come to WM_SYSKEYDOWN, and not to WM_KEYDOWN. In other words, usually you can not catch key combinations with Alt under WM_KEYDOWN. So I am not sure why and how the hell could I verify VK_MENU under WM_KEYDOWN as it does not seem to happen by design.
FeyFre wrote:PS. pls, fix 0x41 -> VK_A
Are you sure VK_A is present in old header files (e.g. in Visual Studio 6)?
Posted: Sat Apr 16, 2011 2:12 pm
by KDJ
DV FeyFre is right. After pressing RightAlt, we receive WM_KEYDOWN message, not WM_SYSKEYDOWN.
Posted: Sat Apr 16, 2011 4:49 pm
by DV
KDJ wrote:After pressing RightAlt, we receive WM_KEYDOWN message, not WM_SYSKEYDOWN.
Wow, let's applause the official Microsoft documentation:
WM_KEYDOWN Notification
The WM_KEYDOWN message is posted to the window with the keyboard focus when a nonsystem key is pressed. A nonsystem key is a key that is pressed when the ALT key is not pressed.
That's we all love M$ for I think they could say if we ask: yes, we meant ALT and not Grey ALT. Widget is not Gadget, as it was said in a short movie dedicated to comparison of the Mac OS X and Windows 7 user interfaces
OK, can you tell me whether (GetKeyState(VK_MENU) & 0x80) is true when you are pressing GreyAlt+A? Or maybe we should verify (GetKeyState(VK_RMENU) & 0x80)?
Posted: Sat Apr 16, 2011 7:28 pm
by KDJ
DV wrote:Click here to see some stupid comments...
function DialogCallback(hWnd, uMsg, wParam, lParam)
{
//...
if (uMsg == 256) //WM_KEYDOWN
WScript.Echo("WM_KEYDOWN");
else if (uMsg == 260) //WM_SYSKEYDOWN
WScript.Echo("WM_SYSKEYDOWN");
//...
}
Press right Alt -> WM_KEYDOWN.
Press left Alt -> WM_SYSKEYDOWN.
Posted: Sat Apr 16, 2011 7:52 pm
by FeyFre
DV
Are you sure VK_A is present in old header files (e.g. in Visual Studio 6)?
Более того, таких define-ов даже в SDK 7.1 нету. Нужно в ручную делать #define VK_A 'A' либо пользовать 'A'
Значит так, при нажатии GrayAlt+A в польской раскладке(написано что это программистская раскладка) получаем такое:
Имя модификатора - состояние (GetKeyState() & 0x80)>>7
VK_SHIFT 0
VK_CONTROL 1
VK_MENU 1
VK_LSHIFT 0
VK_LCONTROL 1
VK_LMENU 0
VK_RSHIFT 0
VK_RCONTROL 0
VK_RMENU 1
(Точно такое же состояние если наблюдать за вводом других букв других языков с этим же модификатором, например украинская ґ у меня стоит на GrayAlt+U)
Posted: Sun Apr 17, 2011 3:53 pm
by KDJ
You should also check the status Shift key.
To write uppercase "Ą", should press Shift+RightAlt+A.
Thanks for your help. Will be fixed in new version of QSearch.
Posted: Thu May 12, 2011 8:52 am
by DV
QSearch v.4.1
* for AkelPad 4.6.0+
+ AkelPad x64 support
- fixed: without Shift pressed, Find Next Up shortkey worked as Down
- fixed: Grey Alt was processed incorrectly (e.g. for Polish)
Posted: Fri May 13, 2011 11:04 am
by Fr0sT
Пункт меню описан вот так:
"Панель поиска" +Call("QSearch::QSearch")
при этом он всегда отмечен галочкой, и повторные нажатия не скрывают панель, что, кажется, не очень правильно.
).
