P
polen.t2006
Hi,
in the past it worked well to send from own program a simulated Key-
press of the Cursor-up key Taste to another program, that in the other
prgram the selection of an item in a listfield moves one step up/down:
sendmessage(wnd,WM_KEYDOWN,VK_UP,0);
sendmessage(wnd,WM_KEYUP,VK_up,0);
Now its not working anymore somehow (software-update), albeit e.g. a
simulated double-click still works by using
sendmessage(wnd,WM_lBUTTONDBLCLK,0,0);
I always used 0 as last parameter.
The MSDN (http://msdn2.microsoft.com/en-us/library/ms912654.aspx)
says
WM_KEYDOWN nVirtKey = (int) wParam; lKeyData = lParam;
lKeyData:
Specifies the repeat count, context code, previous key-state flag,
and transition-state flag, as shown in the following table ...
Does new programs have different handling ("Standards") ? And instead
of using 0 one have to specify lKeyData in detail, that vk_up will be
understood ? I mean, the couble-click is still working as in the past
Any Ideas?
Thanks a lot,
in the past it worked well to send from own program a simulated Key-
press of the Cursor-up key Taste to another program, that in the other
prgram the selection of an item in a listfield moves one step up/down:
sendmessage(wnd,WM_KEYDOWN,VK_UP,0);
sendmessage(wnd,WM_KEYUP,VK_up,0);
Now its not working anymore somehow (software-update), albeit e.g. a
simulated double-click still works by using
sendmessage(wnd,WM_lBUTTONDBLCLK,0,0);
I always used 0 as last parameter.
The MSDN (http://msdn2.microsoft.com/en-us/library/ms912654.aspx)
says
WM_KEYDOWN nVirtKey = (int) wParam; lKeyData = lParam;
lKeyData:
Specifies the repeat count, context code, previous key-state flag,
and transition-state flag, as shown in the following table ...
Does new programs have different handling ("Standards") ? And instead
of using 0 one have to specify lKeyData in detail, that vk_up will be
understood ? I mean, the couble-click is still working as in the past
Any Ideas?
Thanks a lot,