-
Notifications
You must be signed in to change notification settings - Fork 465
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
[Ion::Keyboard::scan] Added some scancode #1616
base: master
Are you sure you want to change the base?
Conversation
The text was iffset due to the subtitle rows
Not just after adding or deleting text
Because some functions already have the parentheses in their name, so their type would have been Variable but it is clearer to give it the type WithoutParentheses. this is the case for nodes created from toolbox nodes.
Scenario: write i, open the varbox and select "in" -> parentheses are added, but there shouldn't be any
Reverts 39c3d66cd
Not at the end of "words" separated by spaces.
For instance, type "abs", there is "()" autocompletion
That function is supposed to recompute the layout, not perform any drawing. Namely, presenting the render without a potential previous call to SDL_RenderClear could lead to some visual glitches.
We might be relayouting a bit too often, but better safe than sorry! Jokes aside, most SDL_WINDOWEVENT should trigger a relayout, and in general those events aren't triggered on a regular basis anyway.
Otherwise the .ipa cannot be uploaded to the app store.
Scenario: Put the complex mode to exponential, then go back to Calculation and: Toolbox, Down, Down, Down, Down, OK, OK, Two, Plus, Imaginary, Toolbox, Down, Down, Down, Down, OK, Down, OK, Two, Plus, Imaginary, OK, Toolbox, Down, Down, Down, Down, Down, OK, Down, OK, Up, OK, Right, Zero, OK, OK, Toolbox, Down, Down, OK, Toolbox, Back, Up, Zero, Up, OK, Zero, Up, Up, Up
If the last cell is too big to fit entirely, we would scroll to the top of the calculation, instead of the bottom
There was a problem with the way of computing Height, see Calculation::HistoryViewCell. We did not encounter a problemeatic scenario here, but there is no reason it would have been safe before.
When a library was broken, we would see an error due to the failed setWindowStyle call, instead of getting the briken library error.
|
|
KeySDLKeyPair(Ion::Keyboard::Key::Zero, SDL_SCANCODE_0), | ||
KeySDLKeyPair(Ion::Keyboard::Key::Dot, SDL_SCANCODE_KP_PERIOD), | ||
KeySDLKeyPair(Ion::Keyboard::Key::Dot, SDL_SCANCODE_PERIOD), | ||
KeySDLKeyPair(Ion::Keyboard::Key::EXE, SDL_SCANCODE_RETURN), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this could be changed to Ok,
So KP_ENTER is EXE and RETURN is OK ?
|
e385767
to
974bf08
Compare
bb3baa7
to
e4c3a98
Compare
This is very usefull with Ion module of mpy port. Some keys aren't mapped, because they don't exist at simulator's host's keyboard (ex : sin, pi, sqrt, ...)
It fixes #1555 and #1678