J
James Salter
Hi all,
I have encountered what i suspect to be a bug in the compact framework. I
am running the following code:
Region clipRegion = new Region();
_bufferGraphics.Clip = clipRegion;
i.e. I am initialising an in memory graphics object with what should be an
infinite clipping region (as documented). However, nothing draws.
Similarly, calls to MakeInfinite seem to have no effect. I assume this is
where the problem lies, and the default constructor is calling
MakeInfinite.
Examining _bufferGraphics.ClipBounds in the debugger reveals that the
clipping region is being initialised to height 1.0 and width 1.0 - clearly
not infinite.
I have worked around the problem by explicitly initialising the region to
the size of the bitmap but presumably this is less efficient for the
clipping mechanism than a simple check for IsInfinite().
I have not reported a bug before, so would appreciate guidance in finding
out a) where to report it or b) where to check if it has already been
reported.
Incidentally, the program runs on WinXP using the full framework and CF.NET.
On WinXP, there is no such problem.
Thanks,
James
I have encountered what i suspect to be a bug in the compact framework. I
am running the following code:
Region clipRegion = new Region();
_bufferGraphics.Clip = clipRegion;
i.e. I am initialising an in memory graphics object with what should be an
infinite clipping region (as documented). However, nothing draws.
Similarly, calls to MakeInfinite seem to have no effect. I assume this is
where the problem lies, and the default constructor is calling
MakeInfinite.
Examining _bufferGraphics.ClipBounds in the debugger reveals that the
clipping region is being initialised to height 1.0 and width 1.0 - clearly
not infinite.
I have worked around the problem by explicitly initialising the region to
the size of the bitmap but presumably this is less efficient for the
clipping mechanism than a simple check for IsInfinite().
I have not reported a bug before, so would appreciate guidance in finding
out a) where to report it or b) where to check if it has already been
reported.
Incidentally, the program runs on WinXP using the full framework and CF.NET.
On WinXP, there is no such problem.
Thanks,
James