On Monday 04 of November 2019, Thorsten Behrens wrote:
> Luboš Luňák wrote:
> > Is this some kind of a strange rule that I'm not aware of? Does
> > somebody know a good reason why all graphics libraries would do
> > this?
>
> Yes, essentially all graphics systems fill polygons like that
> (includin
(re-sent due to odd fdo bounces)
Hey Luboš,
Luboš Luňák wrote:
> Is this some kind of a strange rule that I'm not aware of? Does
> somebody know a good reason why all graphics libraries would do
> this?
>
Yes, essentially all graphics systems fill polygons like that
(including 3D ones). The reaso
Hi,
On Fri, Nov 1, 2019 at 9:48 PM Caolán McNamara wrote:
> On Fri, 2019-11-01 at 13:40 +0100, Luboš Luňák wrote:
> > , the second and third rectangles miss their right and bottom edges.
> > The first one is correct, and it is because that one uses drawRect()
>
> There are so many rectangles the
On Fri, 2019-11-01 at 13:40 +0100, Luboš Luňák wrote:
> , the second and third rectangles miss their right and bottom edges.
> The first one is correct, and it is because that one uses drawRect()
There are so many rectangles there that I'm not sure I see the
difference, but I know that the various
Hello,
if I run "SAL_USE_VCLPLUGIN= bin/run visualbackendtest" and hit Space
once to get to the screen that shows filled rectangles (and diamonds), the
second and third rectangles miss their right and bottom edges. The first one
is correct, and it is because that one uses drawRect(), while t
