You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Im writing because I want to report a bug of the new Pock version (or maybe it is related to the new BigSur idk)..... but in the system preferences when you go to "Keyboard" there is the section "Touchbar Shows" and there you can activate the Control Strip by checking the box next to "Show Control Strip".... now when I switch to the Pock-TouchBar (by double pressing the control-key) and then come back this feature automatically gets deactivated (somehow the box left to "Show Control Strip" is still checked but the Control Strip doesnt show up on the touchbar like if it was unchecked).... so everytime i switch back from Pock to the normal Touchbar I have to go to preferences and reactivate this, id say necesarry, feature to bring back my controls for brightness ect..... so this is very annoying, and it would be great if you could fix this soon... thx :)
The text was updated successfully, but these errors were encountered:
Im writing because I want to report a bug of the new Pock version (or maybe it is related to the new BigSur idk)..... but in the system preferences when you go to "Keyboard" there is the section "Touchbar Shows" and there you can activate the Control Strip by checking the box next to "Show Control Strip".... now when I switch to the Pock-TouchBar (by double pressing the control-key) and then come back this feature automatically gets deactivated (somehow the box left to "Show Control Strip" is still checked but the Control Strip doesnt show up on the touchbar like if it was unchecked).... so everytime i switch back from Pock to the normal Touchbar I have to go to preferences and reactivate this, id say necesarry, feature to bring back my controls for brightness ect..... so this is very annoying, and it would be great if you could fix this soon... thx :)
The text was updated successfully, but these errors were encountered: