bedrock-pc/src, branch mainBedrock emulator and assembler for Windows and Linux
https://code.benbridle.com/bedrock-pc/atom?h=main2025-09-19T02:43:47ZAllow building Bedrock programs as standalone executables2025-09-19T02:43:47ZBen Bridleben@derelict.engineering2025-09-19T02:43:47Zurn:sha1:014aa3639223e0656834d7d469faad40291dd2aa
This commit adds a run_program() function to the root of the library.
Any Bedrock program can be compiled as a standalone native executable
by creating a thin Rust program that calls only that function, passing
in the bytecode of the program and a configuration object.
Use an error flag for file device errors2025-09-19T00:05:46ZBen Bridleben@derelict.engineering2025-09-18T07:23:56Zurn:sha1:967866ca2ec7d066e510b287522c8f69de2c3232
This was a change that was made in the latest revision of the
specification (revision 2). The action port of the file device had
previously reported successes, but it will now report errors instead.
Gate gamepad support behind a feature flag2025-09-19T00:05:46ZBen Bridleben@derelict.engineering2025-09-19T00:02:54Zurn:sha1:1836ac3c6b2abd5dce487f1d7589cfe7466c0fd2
This is to make it possible to compile bedrock-pc without gamepad
support, which is useful when the target platform doesn't have the
libraries for udev (required by the gilrs dependency).
This commit is a bit of a hack, it'd be nice to implement this better
some day.
Print phosphor event loop errors2025-09-18T23:48:41ZBen Bridleben@derelict.engineering2025-09-18T23:47:43Zurn:sha1:661b4012654c8b41a782adf6a5cc1092b8942803
If the phosphor event loop could not be started, the returned error
will be printed in the error message. This commit also updates the
phosphor dependency to version 3.3.2, which returns the actual error
object when an event loop error occurs.
Add logging for starting and promoting a dynamic emulator2025-07-14T23:39:17ZBen Bridleben@derelict.engineering2025-07-14T23:39:17Zurn:sha1:738dd7801c8213228d39f83553a785f1219929c3
This commit changes the message shown when starting the emulator with
dynamic mode, to make it clear that the window will be hidden initially,
and also adds a message for when the emulator window is made visible.
Fix window not being made visible when input device is accessed2025-07-14T23:03:12ZBen Bridleben@derelict.engineering2025-07-14T23:03:12Zurn:sha1:4e3ee9c9d61ff1e05a7881c92d4414a2ae1da784
This is for when the emulator is started in dynamic mode. Reading from
the input device wasn't making the window visible, because the break
signal was only being fired when writing to the input device.
Change scroll units from pixels to lines2025-07-08T01:30:44ZBen Bridleben@derelict.engineering2025-07-08T01:30:44Zurn:sha1:d14677431988b6ad6bfea1ae004a6a6dd8f504a9
The input device now uses lines instead of pixels as the scroll unit.
Reverts commit 2db5707.
Invalidate the cached directory in the file device after a duration2025-07-08T00:00:23ZBen Bridleben@derelict.engineering2025-07-08T00:00:02Zurn:sha1:f2bcc24eec84c4632c88b5a35821f7e642d41dc5
The most recent directory accessed by the file device is cached to
improve performance when rapidly ascending and descending between
sibling entries. This causes an issue where, in a sandboxed root
directory that contains only files, a program will be unable to
invalidate the cache and any changes to the directory outside the
program will not be seen by the program.
To fix this, the directory cache now only lasts for one second.
Show window immediately in graphical mode2025-07-07T23:55:53ZBen Bridleben@derelict.engineering2025-07-07T23:55:53Zurn:sha1:82a10fb3ae8c935e6c325a1b458e7fe6c0b90df6
This was an omission, the visible argument on the run method was added
for this purpose. When starting the emulator in graphical mode, the
window is shown immediately, without the program first having to access
the input or screen devices.
Document the --trust-files flag in the help string2025-07-07T10:17:28ZBen Bridleben@derelict.engineering2025-07-07T10:17:28Zurn:sha1:f01caf7f4873c9d261477ab5d9d18df624cb5d09