Re: gdi32: Use the LOGFONT charset field on OEM font creation

Hi, Is this patch incorrect or more tests are needed? Dmitry said that there are needed additional tests, but you wouldn't like to commit these. Please explain my mistakes. -- Best regards, Ilya Shpigor.

Re: gdi32: Use the LOGFONT charset field on OEM font creation

On Tuesday 05 January 2010 17:08:52 Dmitry Timoshkov wrote: > "Ilya Shpigor" wrote: > > Some explanation for this patch: > > > > The fsCsb is bitfield that is used as boolean value. If this is false the > > DEFAULT_CHARSET is using and the real charset is

Re: [TRY 2] extrac32: Create directory tree before extraction

Hi, Why this patch don't have been commited? There are mistakes? I really want to make extrac32 better, but I don't know what to do if nobody answer me. -- Best regards, Ilya Shpigor.

Re: comctl32: Implementation the WM_GETTEXT processing of datetime control

e to test: is the datetime window procedure process WM_GETTEXT? This message must be send to control directly and be processed through CallWindowProc with DefWindowProc parameter. Is this test give right results? > P.S. Also don't forget comments regarding tests part. The second try of test have been send. -- Best regards, Ilya Shpigor.

Re: comctl32: Implementation the WM_GETTEXT processing of datetime control

ntrol text and this kind of window text are same things. Datetime control have own interpretation of data in the self text buffers. Using window text will need some synchronization when this data change. Can I do it? -- Best regards, Ilya Shpigor.

Re: user32/tests: Test edit control to WM_GETTEXT processing after WM_DESTROY

Please don't commit this test. Instead use or comment next try: user32: Destroy EDITSTATE structure in the WM_NCDESTROY message processing -- Best regards, Ilya Shpigor.

Re: [1/2] extrac32: Add command-line parsing

Hi, What about this group of two patches? Is this correct or there are mistakes? -- Best regards, Ilya Shpigor.

Re: [TRY 2] [1/3] programs: initial add extrac32 utility

r some reason but it is not necessary). -- Best regards, Ilya Shpigor.

Re: [TRY 2] [1/3] programs: initial add extrac32 utility

> You need to include patched configure.ac as well with new > WINE_CONFIG_MAKEFILE entry. Are there other troubles in these patches? -- Best regards, Ilya Shpigor.

Re: [TRY 4] user32/tests: Add tests for STM_SETIMAGE and STM_SETICONmessage processing

at nobody doesn't like to answer? :) -- Best regards, Ilya Shpigor.

Re: comctl32: Send the parent notification after the Wine has set the tooltip position (bug #14336)

On Monday 28 September 2009 19:36:05 you wrote: > Could you please add a test for that? Test for this patch has been sent: comctl32/tests: Add test for setting the tooltips position by parent -- Best regards, Ilya Shpigor.

Re: user32: Add check for the need to redraw static control afterSTM_SETIMAGE and STM_SETICON

> First thing to do (as usual) is to add the test to show the drawing > behaviour. Ok. I will make TRY 4 of tests. -- Best regards, Ilya Shpigor.

Re: user32: Add check for the need to redraw static control after STM_SETIMAGE and STM_SETICON

message processing Is there a better way to block this redrawing? -- Best regards, Ilya Shpigor.

Re: user32/tests: Add tests for STM_SETIMAGE and STM_SETICON messageprocessing

Message is called twice to differ this two cases. You are right. There is a lot of SendMessage calls. I will try to fix it. -- Best regards, Ilya Shpigor.