Hi B 9,
Wow, seems you are correct! Execellent find ... this bug has been here
for nearly 20 years without being detected!
In src/display.cpp, line 4916 is:
mask = 0xFE << data;
but it should be:
mask = ~(0x01 << data);
Ken
On 8/6/24 1:00 AM, B 9 wrote:
On Fri, Aug 2, 2024 at 11:43 PM B 9 <[email protected]> wrote:
The only issue I ran into (and it is a minor one) is that it
doesn't work on my Tandy 200 so I had to use Virtual T.
1. There is a graphical glitch in the doorways that causes pixel
debris. It looks like when a horizontal line is erased to
create a north-south passageway, the erasure starts two or
three pixels too far to the left which cuts into the vertical
wall. (See:
https://gist.github.com/hackerb9/459e2192a8fcf9c4af6430598ed098ac).
2. The.DO file cannot be run because the Tandy 200 has only 24K
(per bank) so there is not enough memory to store both the .DO
file and create the .BA file. You may want to consider
offering a pre-tokenized
<https://github.com/hackerb9/tokenize> .BA file for download.
If you use Github Actions, you can set it so that each 'git
push' of the .DO file will automatically create a fresh .BA
file. (For exampe, see the Makefile
<https://github.com/hackerb9/M100LE/blob/main/Makefile> and
Workflow
<https://github.com/hackerb9/M100LE/blob/main/.github/workflows/release.yaml>
for M100LE <https://github.com/hackerb9/M100LE/>).
3. Only half the screen is used.
Problem #1 is actually a bug in the Virtual T emulator!
image.png
Your Mouse in a Maze works fine on my actual Tandy 200.
--b9
