You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mouse support is great for quickly exploring a parameter space (2 variables) interactively.
currently the mouse cursor is hidden, I feel this could still be the behaviour, no need to support built-in cursor (if you want to a graphical cursor, you have to draw it yourself)
for good behavior in a browser or window, I think it's important that the coordinate range is not clamped to 320x240. Also, if the mouse is clicked inside the screen ("mouse-capture") and dragged out, mouse buttons should still report as down when cursor is outside 320x240
mouse support is great for quickly exploring a parameter space (2 variables) interactively.
currently the mouse cursor is hidden, I feel this could still be the behaviour, no need to support built-in cursor (if you want to a graphical cursor, you have to draw it yourself)
for good behavior in a browser or window, I think it's important that the coordinate range is not clamped to 320x240. Also, if the mouse is clicked inside the screen ("mouse-capture") and dragged out, mouse buttons should still report as down when cursor is outside 320x240
maybe something like this? (aligns with tic-80):
(Float precision is nice cos it enables subpixel accuracy for higher resolutions)
The text was updated successfully, but these errors were encountered: