POINT(x,y) to get pixel color: not working for 16-color (rgba) screen modes

[Charlie Veniot]

The story: 

A month or so ago, I decided to make a little semi-compatibility improvement to the "rgba" modes: gw-basic has 32 choices for colour vs BAM's 16 at the time.  GW-BASIC only has 16 colours (0-15), but duplicates them (16-31).  The first 16 choices are non-blinking colours, and the next 16 are the blinking versions.

BAM doesn't support blinking text.  But to minimise any odd behaviour running GW-BASIC programs that do have blinking text, at least BAM recognises colours  16-31 and shows the non-blinking versions of those colors (instead of not knowing at all what to do with those colour numbers.)

The problem:

I did not think of telling the POINT function that the rgba screen modes now have 32 colours instead of 16, so the function of course started failing in rgba screen modes.

Problem fixed

Well, the problem discovered and fixed while adding a syntax option so that the POINT function can be used to get current graphics X or Y coordinates.