Re: [dcplusplus-devel] catching the enter key

[poy <po...@12...>]

i did it all in MDIChildFrame, with the same kind of way the backgroundcolor 
message is added to every widget.
the patch includes fixes to PublicHubsFrame to make the filter work.

poy

----- Original Message ----- 
From: "Jacek Sieka" <arn...@gm...>
To: "poy" <po...@12...>; "Patches & development discussion" 
<dcp...@li...>
Sent: Monday, November 26, 2007 10:34 PM
Subject: Re: [dcplusplus-devel] catching the enter key


> Hm, maybe winutil makes sense in this case since this is only needed if 
> IsDialogMessage is called
> and it's dc++ that decides to call isdialogmessage...
>
> /J
>
> poy wrote:
>> the "pressing enter in search wasn't working" issue was solved by adding 
>> the
>> following in answer to WM_GETDLGCODE in SearchFrame:
>> static HRESULT allKeys(WPARAM wParam, LPARAM) {
>>  if(wParam != VK_TAB)
>>   return DLGC_WANTMESSAGE;
>>  return 0;
>> }
>>
>> now there are several other parts of DC++ where such a thing would be
>> needed, eg in many list views, or the public hubs filter, pressing enter
>> isn't working.
>> so i was wondering wether i just copy-paste that everywhere i need it, or
>> should it rather be somewhere in smartwin?
>> or have the function in a place like WinUtil so that any class can have
>> access to it, thanks to tr1::bind. :)
>>
>> poy
>
>