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

Disambiguate labels between dynamic scroll info and marked points #36

Open
ComFreek opened this issue Oct 26, 2020 · 0 comments
Open

Disambiguate labels between dynamic scroll info and marked points #36

ComFreek opened this issue Oct 26, 2020 · 0 comments
Labels
formalization-component The underlying formalizations in MMT surface syntax game-engine-UX UX in the game engine needs-discussion

Comments

@ComFreek
Copy link
Member

ComFreek commented Oct 26, 2020

E.g. the OppositeLen scroll has the following description

s"Given a triangle ${lverb A B C} and two known angles, we can deduce the missing angle by the sum of interior angles in triangles always being 180°"

With the partial scroll application A := C, B := A (with RHSs stemming from the situation theory) communicated to the server, the dynamic description reads:

Given a triangle CAC right angled at C, the distance CA can be computed from the angle at A and the distance AC

Here, the original C remaining C and looking like the assigned C is confusing. What can we do here?

  • simple solution: use 𝔸, 𝔹, and ℂ for point labels in scrolls as to not clash with point labels for points marked by the player. This does not scale to any more complex scrolls, say with lines.
  • complicated and robust solution: communicate some more formatting to the game engine (e.g. italics) and use that
@ComFreek ComFreek changed the title fas Disambiguate labels between dynamic scroll info and marked points Oct 26, 2020
@ComFreek ComFreek added formalization-component The underlying formalizations in MMT surface syntax game-engine-UX UX in the game engine needs-discussion labels Oct 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
formalization-component The underlying formalizations in MMT surface syntax game-engine-UX UX in the game engine needs-discussion
Projects
None yet
Development

No branches or pull requests

1 participant