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

Open weakaura at the page it was closed #5608

Closed
capangel opened this issue Jan 6, 2025 · 6 comments
Closed

Open weakaura at the page it was closed #5608

capangel opened this issue Jan 6, 2025 · 6 comments
Labels
🎨 Feature Request This is a request for a new feature, or an expansion of an existing feature.

Comments

@capangel
Copy link

capangel commented Jan 6, 2025

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Not a problem, a quality of life improvement..
When coding in WA in game, we always have to reopen the group(s)-> aura-> page etc.. to go back to the location we where coding at every reload.

Describe the solution you'd like
A clear and concise description of what you want to happen.
Have a checkbox option allowing to reopen exactly where you close WA

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

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

@capangel capangel added the 🎨 Feature Request This is a request for a new feature, or an expansion of an existing feature. label Jan 6, 2025
@mrbuds
Copy link
Contributor

mrbuds commented Jan 6, 2025

When coding in WA in game, we always have to reopen <...> to the location we where coding at every reload

But custom auras doesn't need a reload to use the updated code

@capangel
Copy link
Author

capangel commented Jan 6, 2025

I had different behaviour in the past after a reload.

As an example, I had a behaviour where a trigger active was not followed by going through the conditions. If I only close an reopen WA, the problem was solved.
That is, I was loading in WOW and the aura did not work. open + close WA and it works perfectly.

Now I don't take a chance, I do it often.
I think that just for a checkbox and an additional saved variable, this was somewhat easy to do.

edit: btw I have another issue where I have to do /reload WOW for an aura to work. So I'll like to get immediate to the code I was working on.

@mrbuds
Copy link
Contributor

mrbuds commented Jan 6, 2025

Original post was about reloading ui make /wa not show the same screen you had open, and now you are talking about closing and reopening wa options to fix an aura, that's a different issue.

Can you give a proper step by step example showing what this is about? Because closing and reopening options shows the exact same thing that was shown before closing them. And having to reopen /wa options or reload ui to fix an aura won't be solve with the proposed fix.

@capangel
Copy link
Author

capangel commented Jan 6, 2025

You"re getting confused. Keep to the original post. " Have a checkbox option allowing to reopen exactly where you close WA". it says it all.
Thanks.

@mrbuds
Copy link
Contributor

mrbuds commented Jan 6, 2025

There is no need for such checkbox as it's already the normal behavior.

@mrbuds mrbuds closed this as completed Jan 6, 2025
@capangel
Copy link
Author

capangel commented Jan 6, 2025

"it's already the normal behavior". -> sry then .Can you show me the proper step so WA reopen on the same page it was left? thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎨 Feature Request This is a request for a new feature, or an expansion of an existing feature.
Projects
None yet
Development

No branches or pull requests

2 participants