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

🐞 [Bug]: node filters reset moving off node screen #891

Open
1 task
Suhta opened this issue Aug 21, 2024 · 3 comments
Open
1 task

🐞 [Bug]: node filters reset moving off node screen #891

Suhta opened this issue Aug 21, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@Suhta
Copy link

Suhta commented Aug 21, 2024

Firmware Version

2.4.0

What did you do?

On node screen, by default it shows all nodes detected by Lora and MQTT. However, the filters by default are on for Lora and online, which isn’t being shown. Changing the filters to only show Lora and online only works, but if you go off node screen and say to the Bluetooth screen and back to node screen, the filters are not remembered and again reset.

Expected Behavior

The filters set should be remembered next time you go to node screen.

Current Behavior

See above

Participation

  • I am willing to submit a pull request for this issue.

Additional comments

No response

@Suhta Suhta added the bug Something isn't working label Aug 21, 2024
@garthvh
Copy link
Member

garthvh commented Aug 22, 2024

the node filters are not stored anywhere so they don't stick if you close the app but they stay selected during a single app session.

@Suhta
Copy link
Author

Suhta commented Aug 23, 2024

They definitely do not stay the same within my single session. I can go from nodes to Bluetooth and back and the filters are changed or at least what is displayed.

@bswinnerton
Copy link

Ideally they would be stored somewhere across sessions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants