bedrock-pc/src/devices, branch v1.0.0-alpha2Bedrock emulator and assembler for Windows and Linux
https://code.benbridle.com/bedrock-pc/atom?h=v1.0.0-alpha22024-12-16T01:45:21ZUpdate phosphor dependency to v3.2.12024-12-16T01:45:21ZBen Bridleben@derelict.engineering2024-12-16T01:45:21Zurn:sha1:58faa15a909fe849e7e14a26cca85baf40e7598a
This includes a fix to prevent the cursor from being marked as inactive
while at least one mouse button is still being held.
Update metadata and parser to match current specification2024-12-16T00:45:47ZBen Bridleben@derelict.engineering2024-12-16T00:45:22Zurn:sha1:87f8faba2fde2ac4cfa79dbb1f30907b6e48653c
The metadata specification has changed to use '/' as the separator
between the program name and program version in the name string, and
each author line is now no longer followed by the year in which the
author last contributed to the program.
Fix file device cached child issue2024-11-24T03:19:46ZBen Bridleben@derelict.engineering2024-11-24T03:19:46Zurn:sha1:583c961c0158fd44817695225e06d07caa18657e
When opening the previously-visited directory in the file device, the
directory data is read from a cache, preventing the need to have it
regenerated from scratch. The directory data includes the selected
child, which meant that instead of child 0 being selected as per the
specification, the previously-selected child was selected instead.
To fix this, the child is deselected as the directory data is cached.
Increase default page limit in memory device2024-11-19T21:43:40ZBen Bridleben@derelict.engineering2024-11-19T21:43:32Zurn:sha1:b1dbae360b3ed8de5354ffc4677fb3ada1646cfa
This was erroneously set to 0 from before the memory device was
implemented.
Cache transformed sprite data2024-11-19T21:42:57ZBen Bridleben@derelict.engineering2024-11-19T21:42:57Zurn:sha1:39dfe987cbd99f42d85ea1a0c7d5df866fe739e5
In programs where the same sprite is drawn many times repeatedly, a lot
of time is saved by caching the transformed sprite data instead of
having to recalculate it for every draw operation. No testing has been
done on the efficiency improvements this offers, but it doesn't seem
like it could have any downsides.
Fix file device cached write issue2024-11-12T21:55:32ZBen Bridleben@derelict.engineering2024-11-12T21:55:09Zurn:sha1:2bc38ca471cfb37fb6f65740f7a9f0d374183dce
Writing a value to the pointer and length ports wasn't working, because
the cached write was never getting committed.
Fix line drawing issue2024-11-12T21:54:26ZBen Bridleben@derelict.engineering2024-11-12T21:53:52Zurn:sha1:5ca376b56c3a495c9772e546995485159da2e664
An overflow error was causing the line drawing method to loop forever
any time a line of length 0x4000 (16384) or longer was drawn. The issue
was occurring because both e1 and dx (or dy) would have a value of at
least 0x4000, and so on lines 291/292 the sum would exceed 0x8000, the
maximum value of an i16. The value would then wrap and break the
assumptions of the line drawing algorithm, causing it to loop forever.
This was fixed by increasing the size of the affected types.
Fix issue when drawing textured shapes off-screen2024-11-04T00:06:41ZBen Bridleben@derelict.engineering2024-11-04T00:06:36Zurn:sha1:81a6b0da7a507214a01dc3a4513d8b73525e4381
When determining whether or not to draw each pixel of a textured line
or rectangle, the modulo-by-eight operation was being performed on a
signed value, which was returning a negative value when the pixel being
drawn was off-screen. When the negative value was then converted to an
unsigned value, the result was close to usize::MAX, and was causing an
out-of-bounds array access.
To fix this, the value is converted to an unsigned value before taking
the modulo.
Suppress errors when flushing file and stream data2024-10-31T04:44:28ZBen Bridleben@derelict.engineering2024-10-31T04:44:28Zurn:sha1:d31a97811b94fa4403939c289eaf98eaca237b0e
File and stream data is flushed on drop, and if flushing fails a panic
is thrown, which prints a crash message to the terminal. Since we can't
do anything if the write fails, and because file and stream writes are
approached with a best-effort attitude, we suppress the errors to
prevent the user from seeing them and getting concerned.
Don't clear input stream queue when starting transmission2024-10-31T03:59:39ZBen Bridleben@derelict.engineering2024-10-31T03:58:11Zurn:sha1:043d6dbfb2859d5102e459337329e8eea0a328ae
Writing to the input transmission port of the standard input stream no
longer clears the input queue. The only way to clear an input queue is
to write to the associated queue port.