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

Configuration reminder for the editor. #314

Closed
WeylonSantana opened this issue Sep 14, 2020 · 3 comments
Closed

Configuration reminder for the editor. #314

WeylonSantana opened this issue Sep 14, 2020 · 3 comments
Labels
feature request New and valid feature request question Project information is requested

Comments

@WeylonSantana
Copy link
Contributor

Is your feature request related to a problem? Please describe.
The editor could remember some settings as configured. Every time the editor is opened, I have to change this setting to select only the current layer.

Describe the solution you'd like
When a configuration is made, such as selecting only the current layer, client path, or the like, the editor could remember these settings when it is reopened and not return to the default.

Additional context
Add any other context or screenshots about the feature request here.

@Cheshire92
Copy link
Contributor

I don't think the editor saves any settings at all at the moment.

Which settings would you suggest exactly for which parts of the editor?

@Cheshire92 Cheshire92 added question Project information is requested enhancement Minor feature addition or quality of life change labels Sep 16, 2020
@lodicolo lodicolo added feature request New and valid feature request and removed enhancement Minor feature addition or quality of life change labels Sep 16, 2020
@WeylonSantana
Copy link
Contributor Author

WeylonSantana commented Sep 24, 2020

@Azurebeats in the toolbar, in selection, the default is to select all layers, and select the current layer. Remembering this setting would be a good one. I rarely use to select all layers, I always select a specific layer, usually events. So every time I open the editor, I have to define that.

Another good editor setup would be to remember where the user is while editing events. Because while we are configuring events, with each new edition, the script is updated and returned to the top, this is extremely discouraging for those who make great scripts. I always feel obliged to fragment an event into several, as it is faster and easier than locating everything in a script, where any change will return to the top. This is one of the most annoying things while I am creating event systems.

If when we added commands to events, the editor remembered and stayed where we were, it would be a great addition.

This is what I can remember for now, because in the options of adding a path for the client. the editor remembers which path and allows the client to run, even closing the editor several times. the editor remembers.

@WeylonSantana
Copy link
Contributor Author

@Cheshire92 for me you can close this one, your pr that makes the events go back to where they were when adding a new command partially solves this one. For me it's great. (I didn't find that pr)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New and valid feature request question Project information is requested
Projects
None yet
Development

No branches or pull requests

3 participants