Re: comctl32: Implementation the WM_GETTEXT processing of datetime control

2009-11-30 Thread Ilya Shpigor
> Or course you can, format a string every time contents change and store > it with SetWindowText(). WM_GETTEXT > will work through default procedure (I've done it that way for IPAddress > control). This is good idea, but SetWindowText just send the WM_SETTEXT message. Your patch "comctl32/dateti

Re: comctl32: Implementation the WM_GETTEXT processing of datetime control

2009-11-30 Thread Ilya Shpigor
Hi, Thanks for reply. > I don't think it's a right way. You probably should use window text > instead updating it on every change, > see how GetWindowText is implemented. GetWindowText work with the server side text buffer. Are you offer to use it? I don't sure that control text and this kind o

Re: comctl32: Implementation the WM_GETTEXT processing of datetime control

2009-11-30 Thread Nikolay Sivov
Ilya Shpigor wrote: Or course you can, format a string every time contents change and store it with SetWindowText(). WM_GETTEXT will work through default procedure (I've done it that way for IPAddress control). This is good idea, but SetWindowText just send the WM_SETTEXT message. Your pa

Re: comctl32: Implementation the WM_GETTEXT processing of datetime control

2009-11-30 Thread Nikolay Sivov
Ilya Shpigor wrote: GetWindowText work with the server side text buffer. Are you offer to use it? I don't sure that control text and this kind of window text are same things. Hmm, I'm not sure. Looks like setting text always goes to server call, maybe it's the same thing (synced somewhere?

Re: comctl32: Implementation the WM_GETTEXT processing of datetime control

2009-11-27 Thread Nikolay Sivov
Ilya Shpigor wrote: +static INT +DATETIME_GetText (DATETIME_INFO *infoPtr, INT count, LPWSTR dst) +{ +WCHAR buf[80]; +int i; + +if(!count) return 0; + +dst[0] = 0; +for (i = 0; i < infoPtr->nrFields; i++) +{ +DATETIME_ReturnTxt(infoPtr, i, buf, sizeof(buf)/sizeof(b