mirror of
https://github.com/UpsilonNumworks/Upsilon.git
synced 2026-05-09 08:25:44 +02:00
[GH-ISSUE #45] RPN bug that resets the calculator (+ hypothesis on cause) #13
Labels
No labels
bug
duplicate
easy
enhancement
enhancement
fixed
fixed
good first issue
hard
invalid
pull-request
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Upsilon#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Overengined on GitHub (Oct 9, 2021).
Original GitHub issue: https://github.com/UpsilonNumworks/Upsilon/issues/45
The bug in itself and how to reproduce it:
1.Enter numbers until you fill the memory.
2. Using the arrow keys, select the last entered number.
3. Using the erase key, delete all the numbers in the list, but do not go back to the input box at any time during this phase.
4. Once you've erased all the numbers in the list, check that no cursor can be found in the input box, if there is one, you must start again.
5. Press once the down arrow key so that the cursor appears on the input box.
6. Enter a number and press + , if you've done everything correctly, the calculator crashes and resets.
My hypothesis on why this happens and how it might be fixed:
I've observed that during the steps 4,5, and 6, a realy thin grey box appears on the top of the screen, as if the calculator would be trying to select a "ghost" item (the gray used is the same to highlight selected elements). I think that what happens, is that the calculator tries to do an operation on a selected element that doesn't exist, or at least doesn't have a value, and that causes the crash.
Another element that tends to show that my theory might be right is that, if you do step 6 but without doing an operation and instead simply pressing ok to add the number to the list, nothing abnormal happens.
small note : a similar issue was made by someone else on Omega (apoleon33) , he kindly allowed me t use the gif he made , it can be found here (be aware, it's a big file).
@Syycorax commented on GitHub (Oct 9, 2021):
Fmmpeg-ed the gif to mp4, the video is now way smaller
@RedGl0w commented on GitHub (Oct 31, 2021):
@Lauryy06 commented on GitHub (Oct 31, 2021):
Can I close this issue ?
@Overengined commented on GitHub (Oct 31, 2021):
I don't think, since I don't have seen any hanges been done to the Upsilon repo yet, I think we shall wait.
@Lauryy06 commented on GitHub (Nov 1, 2021):
It's done
@shaunsingh commented on GitHub (Nov 2, 2021):
@Lauryy06 can you pull the changes into your fork (https://github.com/Lauryy06/Upsilon-RPN), its what's used for the submodule
@Lauryy06 commented on GitHub (Nov 2, 2021):
Oh sorry, I modified the submodule but I forgot to push the changes. I'll do it as soon as possible, thanks for reminding me!
@Lauryy06 commented on GitHub (Nov 2, 2021):
This time it's really done.
@apoleon33 commented on GitHub (Nov 3, 2021):
wait that was my issue lol
https://github.com/Omega-Numworks/Omega/issues/432
cool its finally solved ^^