Skip to content
This repository has been archived by the owner on Jan 31, 2023. It is now read-only.

Rapid Change in Screen Orientation May Result in Irreversible Code Loss #81

Open
rolandog opened this issue Jul 3, 2015 · 5 comments
Open

Comments

@rolandog
Copy link

rolandog commented Jul 3, 2015

I am still learning Python and Safe, but I ran into this weird bug right now. I was experiencing several 'server disconnected' notifications (this resulted in a frozen slider), which I attributed to idling while reading up on the code for the examples, ... To reconnect again I would click on the run or evaluate button. However, on one such occasion, after clicking, it cleared the example input and the output was also left blank.

@rolandog
Copy link
Author

rolandog commented Jul 3, 2015

I don't know if this has anything to do with this bug, but a bit earlier, the app had crashed while attempting to plot a simple graph example.

@rolandog
Copy link
Author

rolandog commented Jul 3, 2015

As I was discovering two other bugs (can't select, copy or paste code, and the permalink sharing feature is broken because the browser only shows JSON output from the query; I will file them separately), I may have stumbled on the cause. It seems that rotating the screen causes the editor to blank out.

@rolandog
Copy link
Author

rolandog commented Jul 3, 2015

I don't know if this is linked to #64 or #66. I will try to dig deeper when I'm on a desktop.

@rolandog rolandog changed the title Running an example results in irreversible code loss Rapid Change in Screen Orientation May Result in Irreversible Code Loss Jul 3, 2015
@rolandog
Copy link
Author

rolandog commented Jul 3, 2015

I was able to replicate the bug by rapidly changing screen orientation... but it doesn't always happen (I'd say it's around a 40% chance of being replicated, so you have to try several times), I've yet to try with other examples, but for this case, I'll be working on the Taylor Series example.

The steps are as follows:

  • Open the Taylor series example
  • You may optionally run the code so as to get the plotted graph.
  • Place the text cursor preferably on a position that highlights some code (after a closing parenthesis sign). This causes your Android's keyboard to popup.
  • Flip your phone from vertical to horizontal position and then to vertical again in a quick manner (the time needed for this is around 1 second, tops).
  • If you're presented with a blank text area, you have successfully replicated the bug.
    • I just discovered that your code may not be lost, unless you're that kind of particular person that hits the run button in hopes that everything gets back to normal.
  • If you didn't hit the run button, you may recover by changing screen orientation again, or exiting and entering again.

@rolandog
Copy link
Author

rolandog commented Jul 3, 2015

As is reported in Bug #82, the only way to recover is, so far, to uninstall and reinstall again.

So please be careful!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant