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
In hyperspeedcube/src/gui/tabs/puzzle_view.rs, compute triangle orientation (clockwise vs. counterclockwise) and reverse the twist depending on it
You might try first changing the fill color of the triangle depending on its orientation, to make sure you're detecting orientations correctly.
Test with various 3D puzzles of different shapes, as long as they have twist gizmos at all. "Show frontfaces", "show backfaces", and "gizmo scale" may be useful for testing.
Add a preference. See hyperspeedcube/src/preferences/interaction.rs, hyperspeedcube/locales/en.kdl, and build_interaction_section() in hyperspeedcube/src/gui/components/prefs.rs. Add a default setting in default.yaml. See my comment below for what to call the setting.
The text was updated successfully, but these errors were encountered:
I'd add a "Twists" section in interaction settings, with a checkbox "Back of 3D gizmo does reverse twist" (or similar phrasing, ideally as concise as possible)
Steps to reproduce
Expected behavior: the pieces twist counterclockwise from the user's current perspective
Actual behavior: the pieces twist counterclockwise from the holding-the-face-in-front perspective
Guide
hyperspeedcube/src/gui/tabs/puzzle_view.rs
, compute triangle orientation (clockwise vs. counterclockwise) and reverse the twist depending on itYou might try first changing the fill color of the triangle depending on its orientation, to make sure you're detecting orientations correctly.
Test with various 3D puzzles of different shapes, as long as they have twist gizmos at all. "Show frontfaces", "show backfaces", and "gizmo scale" may be useful for testing.
hyperspeedcube/src/preferences/interaction.rs
,hyperspeedcube/locales/en.kdl
, andbuild_interaction_section()
inhyperspeedcube/src/gui/components/prefs.rs
. Add a default setting indefault.yaml
. See my comment below for what to call the setting.The text was updated successfully, but these errors were encountered: