Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Devkit, devtools and developer experience improvements #796

Merged
merged 4 commits into from
Jan 2, 2025

Conversation

majaha
Copy link
Contributor

@majaha majaha commented Dec 21, 2024

A few patches that:

  • Fix an issue with websockets when running vite
  • Fix the web runtime fps counter
  • Fix the web runtime devtools palette viewer

When we're developing the wasm4 web runtime itself, there's no w4 CLI
websocket to connect to. But trying to connect anyway fights for the
Vite websocket, which causes hangs on reload occasionally.
Frame timings are now averaged in a mathematically sound way, and
with more samples.
On Wasm-4, palette colours are in the order `0xAARRGGBB`,
where `A` represents unused/alpha. On the web/css however, the order
is `#RRGGBBAA`. This meant that previously, if the most significant byte wasn't 0,
the colours in the devtool's palette viewer were garbled.
@aduros
Copy link
Owner

aduros commented Jan 2, 2025

Thanks!

@aduros aduros merged commit fa5b273 into aduros:main Jan 2, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants