-
Notifications
You must be signed in to change notification settings - Fork 541
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
Add keyboard shortcut to temporarily hide all labels in the App #1779
Conversation
1315230
to
c01def1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Looks like HOLD was straightforward to add. Clean solution.
I wouldn't worry about debouncing. Updates are supposed to run in a single animation frame regardless.
this.element.src = ICONS.overlaysHidden; | ||
} else { | ||
this.element.title = `Show all overlays (h)`; | ||
this.element.classList.add(lookerControlActive); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe reverse the icons? It looks like the strike through icon is shown when labels are visible. I would have thought that means they are hidden.
Couple things I saw while testing:
|
Fixed the issues mentioned above. This should be ready to go now. |
See background in #1761.
This feature adds the ability to temporarily hide all overlays/tooltips by pressing the "Shift" key. This is supported while viewing samples in the
Looker
modal image and video modes.Specifically this adds:
Looker
Looker
controlsAtom
for persisting the show/hide overlay value in recoilLooker
and recoil (based on fullscreen)To implement a control with "hold" supprt, you must specify it's
ControlEventKeyTypes
asHOLD
as well as add a new method:control.afterAction()
. ThisafterAction
method will be called onkeyup
allowing for the control to make updates after the user depresses the key.NOTE: in a typical hold event model I would usually debounce the keydown event. I've left that optimization out, if we notice performance issues we can look into adding that or something similar.