On 05.09.2005 14:49, Michael Kaufmann wrote:
> I've found another problem: Reading the window proc address with
> GetWindowLong won't work for subclassed windows. We need to pass the
> window proc as a parameter to UnmapMsg32ATo32W (and probably also to
> other mapping functions).
>
> Maybe it's e
But apart from that, why is the patch not CVS-worthy?
Due how the WM_GETTEXT is "dispatched" (ie calling the proc) - but that
would be solved with SendMessageW().
I've found another problem: Reading the window proc address with
GetWindowLong won't work for subclassed windows. We nee
On 05.09.2005 11:23, Michael Kaufmann wrote:
> Hi,
>
> Does Windows XP use Unicode controls too if theming is on?
Yes. (Technically, it uses Unicode controls when comctl 6.0 is used.)
-f.r.
On 05.09.2005 11:23, Michael Kaufmann wrote:
> I think you could use SendMessageW instead of calling the window proc
> directly.
Yeah... since UnmapMsg32ATo32W is used for both in-process and
inter-process communications, just using SendMessageW() is more correct
and less hassle than messing wit
Hi,
Does Windows XP use Unicode controls too if theming is on?
Because the Delphi edit controls are now in Unicode mode, the messages
sent to them have to be translated from ANSI to Unicode and back. When a
program reads the "Text" property of a TEdit control, Delphi sends a
WM_GETTEXTLENGTH me
On 04.09.2005 16:47, Michael Kaufmann wrote:
> Hi Frank,
>
> One of your theming patches (
> http://www.winehq.org/hypermail/wine-cvs/2005/08/0313.html ) has caused
> a problem in many Delphi applications. The edit controls of Delphi
> applications are now created in Unicode mode. I hope you have
Hi Frank,
One of your theming patches (
http://www.winehq.org/hypermail/wine-cvs/2005/08/0313.html ) has caused
a problem in many Delphi applications. The edit controls of Delphi
applications are now created in Unicode mode. I hope you have an idea
why this happens... Of course Delphi applica
