Thread: Windows-XP and 2003 Problem's patch to wxWindows

Windows-XP and 2003 Problem's patch to wxWindows

From
"Hiroshi Saito"
Date:
Hi Dave.

When I examine it so far,
Problem is shown remarkably with Windows-XP and 2003.

Former patch was the thing to indicate the problem place clearly.
Then, a problem is complex though it could be cleared to a certain extent.

First of all I showed the need of the modification.
https://sourceforge.net/tracker/index.php?func=detail&aid=849433&group_id=9863&atid=309863
It is thought to make the most of it as a material to proceed in a solution of a problem.

However,
Application to our wxWindows worries whether I should wait for the result.
any idea?

When patch is applied, a solution is done.
http://cre-ent.skcapi.co.jp/~saito/pgadmin3/comctl32_patch_After.jpg

regards,
Hiroshi Saito

Attachment

Re: Windows-XP and 2003 Problem's patch to wxWindows

From
Andreas Pflug
Date:
Hiroshi Saito wrote:

>First of all I showed the need of the modification.
>https://sourceforge.net/tracker/index.php?func=detail&aid=849433&group_id=9863&atid=309863
>It is thought to make the most of it as a material to proceed in a solution of a problem.
>
>

Nice catch!

For our purposes, we could apply that patch, or simply comment out all
WM_ERASEBACKGND handling in wxNotebook::MSWWindowProc (reducing it to
forwarding all events to wxControl::MSWWindowProc). Final wx solution
will probably look different, but we don't need to care.

My next binary snapshot upload will include this solution, fixing.

Regards,
Andreas



Re: Windows-XP and 2003 Problem's patch to wxWindows

From
"Hiroshi Saito"
Date:
Hi Andreas.

It is completely good.
Hopefully.:-)

I am a little sleepy...

regards,
Hiroshi Saito

From: "Andreas Pflug" <pgadmin@pse-consulting.de>


> Hiroshi Saito wrote:
>
> >First of all I showed the need of the modification.
> >https://sourceforge.net/tracker/index.php?func=detail&aid=849433&group_id=9863&atid=309863
> >It is thought to make the most of it as a material to proceed in a solution of a problem.
> >
> >
>
> Nice catch!
>
> For our purposes, we could apply that patch, or simply comment out all
> WM_ERASEBACKGND handling in wxNotebook::MSWWindowProc (reducing it to
> forwarding all events to wxControl::MSWWindowProc). Final wx solution
> will probably look different, but we don't need to care.
>
> My next binary snapshot upload will include this solution, fixing.
>
> Regards,
> Andreas


Re: Windows-XP and 2003 Problem's patch to wxWindows

From
"Dave Page"
Date:
Thanks Hiroshi, new snapshot built.

Regards, Dave.

> -----Original Message-----
> From: Hiroshi Saito [mailto:saito@inetrt.skcapi.co.jp]
> Sent: 26 November 2003 17:49
> To: Andreas Pflug; Dave Page
> Cc: pgadmin-hackers@postgresql.org
> Subject: Windows-XP and 2003 Problem's patch to wxWindows
>
> Hi Dave.
>
> When I examine it so far,
> Problem is shown remarkably with Windows-XP and 2003.
>
> Former patch was the thing to indicate the problem place clearly.
> Then, a problem is complex though it could be cleared to a
> certain extent.
>
> First of all I showed the need of the modification.
> https://sourceforge.net/tracker/index.php?func=detail&aid=8494
> 33&group_id=9863&atid=309863
> It is thought to make the most of it as a material to proceed
> in a solution of a problem.
>
> However,
> Application to our wxWindows worries whether I should wait
> for the result.
> any idea?
>
> When patch is applied, a solution is done.
> http://cre-ent.skcapi.co.jp/~saito/pgadmin3/comctl32_patch_After.jpg
>
> regards,
> Hiroshi Saito
>