-
-
Notifications
You must be signed in to change notification settings - Fork 511
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
Comments
As it works right now I see that the following parts of surfaces are "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. |
Thanks! I do not know the way it should work but my expectations as a user
is that when I do a full configuration reset that I get an initial setup as
if I installed Companion the first time. Keeping active surfaces makes
sense to me.
…On Sat, 14 Sep 2024 at 15:39, Joel Wetzell ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub
<#3034 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A25NECF7F3MODFNI5O2INU3ZWQ4C3AVCNFSM6AAAAABOGW26F2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJQHE4TKMZTGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
good spot, this is fixed now. This also made me realise that it wouldn't clear any tcp connected streamdeck studios, which should be reset too. |
👍😀
…On Mon, 16 Sep 2024 at 13:16, Julian Waller ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub
<#3034 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A25NECBPJL5VZBCDL6UTAU3ZW24XPAVCNFSM6AAAAABOGW26F2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJSGYZTEMZVGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Is this a bug in companion itself or a module?
Is there an existing issue for this?
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)
Additional context
No response
The text was updated successfully, but these errors were encountered: