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

Editor user experience improvements #628

Open
pedrovelho opened this issue Dec 5, 2018 · 1 comment
Open

Editor user experience improvements #628

pedrovelho opened this issue Dec 5, 2018 · 1 comment

Comments

@pedrovelho
Copy link
Contributor

While working on PrEstoCloud I had several annoying moments using the studio editor. I created this issue so we can improve this hopefully in a near future.

  • Need to close the editor to save, this is really the most annoying one. I have often to close what I am doing just to save it because if I click outside the editor window it will close the current script without saving my changes. I suggest a save button that does not close the editor. Close button then close without saving, but why having this button if just clicking outside boils down to the same?

  • When you open the editor window you cannot use the pg-up and down or arrows because focus is not set automatically. I suggest set focus inside automatically.

  • Scrolling, so you must use the mouse wheel to scroll. If your file is a bit long you might click and drag the vertical scroll bar, but attention if you release the mouse button outside the window you accidentally loose all your work because the editor window close without saving. I propose we ask for saving before leaving or just ignore mouse release as a mouse click.

  • The state of scrolling is not saved, each time document is open it starts from the beginning so we need to find ourselves again on the code. It would be much better if it opens already focusing on the last line.

fviale added a commit that referenced this issue Dec 18, 2018
Work on #628 Editor user experience improvements
@amouhoub
Copy link
Member

amouhoub commented Apr 7, 2019

@pedrovelho @fviale is this issue fixed including all of the aforementioned items ? if not can you please update this issue with a listing of still items. thank you in advance

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

No branches or pull requests

3 participants