On October 21, 2003 09:00 am, Rein Klazes wrote:
> See? You are looking for an if-else-statement yourself. Perhaps there is
> not one. And if there is, it may test numerous other things then the
> Windows version.
I am not. But knowing is various Windows versions are consistent in
certain behavior
On Tue, 21 Oct 2003 00:12:20 -0400, you wrote:
> On October 20, 2003 02:55 am, Rein Klazes wrote:
> > I cannot imagine the conformance here to be accidentally "lost". I am
> > not against conformance tests in general, but to protect such simple
> > one-line functionality seems to me a waste of the
On October 20, 2003 02:55 am, Rein Klazes wrote:
> I cannot imagine the conformance here to be accidentally "lost". I am
> not against conformance tests in general, but to protect such simple
> one-line functionality seems to me a waste of the effort.
Right, but the test would also tell us if all
On Sun, 19 Oct 2003 12:19:10 -0400, you wrote:
> On October 19, 2003 11:10 am, Rein Klazes wrote:
> > Now I spent some time creating EDIT windows, varying parameters (with or
> > without text), varying styles including multilines even tested the edit
> > part of a combobox. In all cases the WM_CRE
On October 19, 2003 11:10 am, Rein Klazes wrote:
> Now I spent some time creating EDIT windows, varying parameters (with or
> without text), varying styles including multilines even tested the edit
> part of a combobox. In all cases the WM_CREATE message return value
> turned out to be 1. So at th
Hi,
Sent to wine-devel as well: this might break some odd edit controls that
I did not catch.
This fixes masked edit controls used by applications created by Power
Builder, it fixes bug #807.
Power builder depends on the return value of the WM_CREATE message by
the EditWndProc to be != 0.
Now I
