Dmitry Timoshkov writes:
> Alexandre Julliard wrote:
>
>> > I looks like the default clip region created by ExtSelectClipRgn() uses
>> > the dimensions of the selected bitmap, and it's not large enough.
>>
>> That's a window DC, it doesn't have a selected bitmap.
>
> You are right. The app crea
Alexandre Julliard wrote:
> > I looks like the default clip region created by ExtSelectClipRgn() uses
> > the dimensions of the selected bitmap, and it's not large enough.
>
> That's a window DC, it doesn't have a selected bitmap.
You are right. The app creates very large child window to fit th
Dmitry Timoshkov writes:
> I looks like the default clip region created by ExtSelectClipRgn() uses
> the dimensions of the selected bitmap, and it's not large enough.
That's a window DC, it doesn't have a selected bitmap.
--
Alexandre Julliard
julli...@winehq.org
Alexandre Julliard wrote:
> > If there is no current clipping region ExtSelectClipRgn(hdc, hrgn, RGN_DIFF)
> > creates its own default clipping region which in most cases doesn't match
> > neither a visible region nor the window extents attached to the DC.
>
> It will get intersected with the vi
Dmitry Timoshkov writes:
> If there is no current clipping region ExtSelectClipRgn(hdc, hrgn, RGN_DIFF)
> creates its own default clipping region which in most cases doesn't match
> neither a visible region nor the window extents attached to the DC.
It will get intersected with the visible regio
