Fill exceeding bounds

Report bugs. Post bug workarounds or fixes

Moderator: MSandro

Post Reply
SimpleSi
Posts: 330
Joined: Jul 2nd, '17, 13:47

Fill exceeding bounds

Post by SimpleSi » Jul 5th, '17, 11:12

0.png
0.png (10.71 KiB) Viewed 18186 times
filled whole screen whereas I expected it to just fill the circle

JohnM
Posts: 379
Joined: Sep 11th, '15, 14:42

Re: Fill exceeding bounds

Post by JohnM » Jul 5th, '17, 12:15

Thanks for reporting this.

I've reproduced it. WIll fix.

-- John

SimpleSi
Posts: 330
Joined: Jul 2nd, '17, 13:47

Re: Fill exceeding bounds

Post by SimpleSi » Jul 5th, '17, 12:20

JFI The other fill functions do unexpected things as well

JohnM
Posts: 379
Joined: Sep 11th, '15, 14:42

Re: Fill exceeding bounds

Post by JohnM » Jul 5th, '17, 14:25

This bug is a bit strange. The fill example works the second time, so there is some initialization issue I don't yet understand. Do the other cases also work correctly the second time? If so, this is all caused by the same bug.

SimpleSi
Posts: 330
Joined: Jul 2nd, '17, 13:47

Re: Fill exceeding bounds

Post by SimpleSi » Jul 5th, '17, 14:58

I am experiencing repeatability issues with several drawing functions not just this one

And this one gives wierd result - seems to be drawing something within the sprite image rather than the canvas

Image
Attachments
fill.PNG

SimpleSi
Posts: 330
Joined: Jul 2nd, '17, 13:47

Re: Fill exceeding bounds

Post by SimpleSi » Jul 5th, '17, 19:59

aah - the penny drops!

The Drawing and Pixels blocks refer to the image of the instance not the canvas :)

Simon

SimpleSi
Posts: 330
Joined: Jul 2nd, '17, 13:47

Re: Fill exceeding bounds

Post by SimpleSi » Jul 14th, '17, 21:52

Still doesn't seem to work for me in V072 Win10
0.png

JohnM
Posts: 379
Joined: Sep 11th, '15, 14:42

Re: Fill exceeding bounds

Post by JohnM » Jul 14th, '17, 22:57

Interesting! The bug is fixed on other platforms, but not Windows. There's apparently a difference in the how Windows reads textures into bitmaps.

In other words, this bug arises from a low-level implementation issue. GP tries to make things work exactly the same on all platforms but sometimes something subtle slips through.

As a workaround, this works as expected if you set the pen color to any color except pure black. For example, (gray 1) will work and is basically black.

I might might make (gray 1) the default pen color as a workaround. :-)

SimpleSi
Posts: 330
Joined: Jul 2nd, '17, 13:47

Re: Fill exceeding bounds

Post by SimpleSi » Jul 15th, '17, 04:09

Make it the green one that you use as default option in all the colour ops and then no-one will ever know :)

Until they draw a black circle of course :)

Post Reply