stardot.org.uk

Bug fix for VAL - it should ONLY handle decimal numbers (not hex or binary) I think that's unfortunate. That was a pretty nice feature that I used quite a bit. I strongly disagree. It was a bug, and as such broke some of my programs (those that rely on VAL being guaranteed to return zero for any st...

I draw the line at buying a Mac. :wink: I sympathise, but I had no choice in order to create the MacOS and iOS editions of BBCSDL (I bought a Mac Mini so that I could at least share my monitor, mouse and keyboard using a KVM switch). There's also Android to add to the list of platforms I would need...

I just report the error, then siglongjmp() to the error handler (from ON ERROR) or back to the immediate mode loop. Yes, I understand how errors are handled (I do the same), I meant how do you intercept the segfault? Are you using 'sigaction()'? It's this at the man page that scares me: " Applicati...

any illegal read or write will raise Address exception but won't crash Brandy itself. I have mixed feelings about the desirability of trapping segfaults. Raymond Chen, the Microsoft guru and blogger, advises that it's best to let the application crash (I appreciate that you probably aren't using Is...

I see another fpga project coming on - a scan doubler of some sort - any recommendations for video DAC's? If you can find a capture device that will save the 576i 'properly' (i.e. without attempting to deinterlace or otherwise mangling the video) you can do the conversion to 576p50 downstream, eith...

To reiterate, I was the one who merged the pull request, nobody else has access to do that on my branch. So, do not worry about anybody being able to do something unexpected to BBCSDL. Fair enough. I am somewhat obsessive about regressions, for example before issuing a new version of BBCSDL I run '...

A recent merge from @jgharston has removed the offsetting used for Brandy's memory space. I'm surprised that can happen, especially without you knowing. Is it because you are sharing StarDot's github account that he is able to make changes? I'm hoping nothing similar can happen to BBC BASIC for SDL...

dhg2 wrote: ↑

Fri Sep 06, 2019 12:51 pm

Sorry, I forgot to mention that in the case of bb4w, I changed that procedure

Grr. You really don't want to get me started again on those GCOL extensions that don't even have VDU equivalents!

it behaves correctly on ... Richard Russell's BB4W. I don't understand how it can have done, since it includes this code: DEF PROCgcol(c%) GCOL (c%AND&FF0000)>>16, (c%AND&00FF00)>>8, c%AND&FF ENDPROC which has GCOL followed by three parameters. I know about the one-parameter and two-parameter varia...

I was under the impression that some de-interlacers used motion compensation (where it tries to guess the trajectory of moving objects and compensate for this)...something I really don't want. There are indeed motion-compensated deinterlacers, but as you say these aren't relevant to you. It's proba...

I suspect the de-interlace may make my problems worse i.e. does it shuggle lines horizontally to de-interlace to a 25p frame? A deinterlacer shouldn't be doing anything "horizontally"! All good deinterlacers are vertical-temporal filters of some kind; the beauty of Martin Weston's filter is that it...

I was going to ask for some screenshots... I generally work on the basis that virtually anybody can run BBC BASIC for SDL 2.0 , since it is available for so many platforms (including Android and iOS), so if you want to see it in action you can try it for yourself. Perhaps this forum is the one plac...

Here's what the supplied example program aagfxdem.bbc produces, on all the supported platforms:

I have interlace turned off usually on the beeb so I guess that is really 288/50p that I want to capture? With interlace turned off it's a non-standard video format so possibly a capture card won't lock to it at all, it will depend on how tolerant it is. I would recommend leaving interlace on and t...

I have released version 1.06a of BBC BASIC for SDL 2.0 , the cross-platform programming language for Windows, MacOS, Linux, Raspbian, Android and iOS. The changes in this version are as follows: BASIC Interpreter / Run Time Engine Added support for antialiased 2D graphics (extending SDL2_gfx). Incre...

I'd like to be able record my demos to proper interlaced 576i PAL type video for posting up on the net. Support for "proper interlaced 576i" is limited, in formats suitable for streaming from the net, so one thing you could consider is to de-interlace it to 576p50 (i.e. progressive at 50 fps). Now ...

Soruk wrote: ↑

Sun Sep 01, 2019 11:36 am

Unused variables, nothing to worry about.

It's undesirable nevertheless, because if people get used to seeing warnings every time it's compiled they may not notice if a new (potentially more important) one appears.

5: Leave colour on screen unchanged (jgh: implicitly ignoring c) 6: AND colour on screen with (NOT c) 7: OR colour on screen with (NOT c) Had I known about them I could have implemented them in BB4W and BBCSDL because I'm pretty certain there are corresponding codes used by SetROP2() in Windows GDI...

8+k for transparent background, and adds defined actions for k=5,6,7. I've not come across these and they are not implemented in BBC BASIC for Windows or BBC BASIC for SDL 2.0 . Purely for interest what does "transparent background" mean and what are the "defined actions" for 5, 6 and 7? On the top...

You can replace a whole bunch of separate arrays e.g. name$(I%), height(I%), weight(I%) and so forth, where I% is the common index into each of them, with just one array indexed on I% and each element having all those properties in it. Absolutely. In the syntax I devised for BBC BASIC for Windows a...

Somebody has posted this, unbidden, at the BBC BASIC forum (and, no, it's not me posting under an alias): " I just want to let people know that I finally did the effort to use structures in my programs and that this was a revelation. Big words but justified. I know Richard has made the effort to imp...

It's possible that fix was back ported into the drive raspberry pi released to fix libre office. We now have the answer from the horse's mouth at the Raspberry Pi forum. The LibreOffice 'fix' wasn't achieved by implementing glLogicOp() at all, " It was more of a workaround. Something to do with swi...

dp11 wrote: ↑

Sat Aug 17, 2019 5:22 pm

It's possible that fix was back ported into the drive raspberry pi released to fix libre office.

Does that help me?

The fix being talked about is not included in any of the Mesa 19.1.x versions. It should appear in Mesa 19.2, which is still in development. Thanks for the clarification. On that basis I can't be optimisitic that it will be in Raspbian any time soon. The only way to test this now would be to build ...

I'm pretty sure that fix is in the latest driver. So how do you install that driver other than doing 'apt-get dist-upgrade', which seemingly had no effect? Is there something else you need to do to enable it (whilst the VC4 driver on the RPI 3 needed explicitly enabling, my understanding was that t...

I'll ask the user who reported it to update his RPi4 (although it was quite new anyway). He reports that there is no change. Having done: sudo apt-get update sudo apt-get dist-upgrade All the glLogicOp modes he tested (OR, AND and XOR) are still non-functional. Is there anything else he could/shoul...

dp11 wrote: ↑

Fri Aug 16, 2019 11:10 am

I don't know about OR and AND, but I suspect they are also fixed. The driver certainly has had the XOR fix for a while now.

I'll ask the user who reported it to update his RPi4 (although it was quite new anyway).

My understanding is XOR is now supported. Is there another op that also doesn't work ? Since when? I don't have a RPi4 myself and I'm relying on reports from other users. I'm somewhat surprised if they've sorted XOR but not the others (OR, AND etc.) because I thought the fix implemented them all. C...

Also, long double is 12 bytes (96 bits) on i686, 16 bytes (128 bits) on x86-64. That is more an alignment issue than anything else. If the FPU is being used to carry out the long double calculations, which is the only thing that makes sense on those CPUs, then only 10 bytes (80 bits) are actually s...

It depends upon how much work you wish to put in to make sure that the code is (a) portable and, (b) future-proof. None! My code isn't portable (and isn't intended to be); it is full of platform-specific features and compiler-specific features. Within the limited set of platforms and compilers with...