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] Reset Configuration - Surfaces does not clear (all) surfaces from the list #3034

Closed
2 tasks done
LikeThisReview opened this issue Sep 14, 2024 · 4 comments
Closed
2 tasks done
Labels
BUG Something isn't working
Milestone

Comments

@LikeThisReview
Copy link

Is this a bug in companion itself or a module?

  • I believe this to be a bug in companion

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

After Reset Configuration with all Reset Options checked there were still a number of Surfaces listed on the surface page, including a connected Stream Deck (OK), Emulators and Stream Decks not attached to the computer

Steps To Reproduce

Reset Configuration with all Reset Options checked

Expected Behavior

No surfaces in the list, or only the surfaces actually connected to the computer

Environment (please complete the following information)

- OS: Windows 11
- Browser: Edge
- Companion Version: v3.4.0

Additional context

No response

@LikeThisReview LikeThisReview added the BUG Something isn't working label Sep 14, 2024
@jwetzell
Copy link

As it works right now I see that the following parts of surfaces are "reset".

  • all settings (grid offset, row/column count for emulators, rotation, etc.)
  • "Offline" surfaces are removed (this doesn't match what you are seeing so may need more looking at)
  • emulators are added back with settings reset (like you said this isn't what I would expect either)
  • actively connected surfaces are added back with settings reset

Removing the emulators should be fairly easy (I've got it working locally) if that is what should be happening I can propose the small change I made to get that working.

@LikeThisReview
Copy link
Author

LikeThisReview commented Sep 14, 2024 via email

@Julusian
Copy link
Member

good spot, this is fixed now.
It is intentional that any connected streamdecks will remain, and that matches how companion would behave if they were connected before launching it for the first time.

This also made me realise that it wouldn't clear any tcp connected streamdeck studios, which should be reset too.

@LikeThisReview
Copy link
Author

LikeThisReview commented Sep 16, 2024 via email

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
Status: Done
Development

No branches or pull requests

3 participants