Thank you, that is extremely helpful - not least that it is exactly why I resigned from the forum recently. I have been thinking in the last few weeks that it was wrong of me to continue as a member o

Maybe I'm being particularly slow today (I'm suffering from severe back pain so it's possible) but I'm really having difficulty understanding what you mean. You should not be "putting" code anywhere,

Unless and until one of the aforementioned six members responds, the simplest explanation is that they are not receiving my messages. If it was just one or two of them I could believe that they simply

How much delay did you add? Have you tried adding a silly amount (e.g. a second) so you can see the sequence in which things are happening? One useful diagnostic would be to output the values that are

Hmm. That doesn't explain why those members who were so keen to investigate, and to help me try to fix, the reported 'ellipses' fault last week ('Jon Welch', 'lettersquash', 'gav', 'Ken Orr', 'Lifes V

I'm not really sure what you mean. Are you saying you've already tried my suggested modification but it hasn't helped? If you are wanting to perform a more drastic modification involving an extra PROC

I am very conscious that messages that I have posted here in the last few days are not receiving any replies. I announced the release of BBCSDL v1.00c with a request for feedback: NOTHING. I specifica

However it's most unlikely to be reliable. The underlying cause, I am almost certain, is what I described: the 'window size changed' notification is being generated before the window has 'settled' to

It doesn't do it here, but then I'm running a different version of Linux (Ubuntu 18.04) on different hardware. So unfortunately there's no "normal" when it comes to a cross-platform product like BBCSD

What a strange thing to say. Dialogue boxes are quite well supported in BBCSDL: there's a library ('dlglib.bbc') and an example program ('dlgdemo.bbc') which are supplied with all the desktop editions

I was expecting (or at least hoping for) some reaction to this, for example in respect of what your use case is (were you experimenting with RECTANGLE SWAP out of curiosity or because you have a speci

I have explained before that I view the group using its web interface which does not support attachments. Have you tried version 1.00c and if so what are your findings in respect of the questions I as

I've uploaded BBCSDL v1.00c (Android only) to make it easier for people to do some more testing without needing to edit the ellipse library themselves. In this version I've set the number of line segm

Of course a circle has a greater circumference than the ellipse (and hence the straight-line segments comprising the Bezier curves are longer) so can I assume you tried increasing the number above 4?

That's what I would have expected. It would still be interesting to know whether the 'gaps' through which the flood-fill is apparently leaking are at the junctions between the four Bezier curves, or b

There are eight calls to bezierColor() in the PROCellipsefill section of the ellipse.bbc library: SYS "GFX_bezierColor",@memhdc%,v%%, w%%, 4,3,Z% SYS "GFX_bezierColor",@memhdc%,v%%+6, w%%+6, 4,3,Z% SY

Before or after the change from 3 line segments to 4? Failure on Windows is likely to be unrelated, unless (very unusually) your display is configured for 16-bit colour. You might want to check whethe

I see a post from him, but it's empty so we don't know one way or the other! Sadly we haven't got to the "bottom" of anything! There's no 'science' in increasing the number of line segments, if it has

But via what mechanism? As you know the 2D 'drawing' routines (specifically the bezierColor function in this case) are in the SDL2_gfx library which is statically linked with BBCSDL, not part of Andro

It sounds as though the ellipses are not forming 'closed curves' at those specific angles, allowing the flood-fill to leak through. I'm not aware of similar problems on any of the desktop platforms (W