-
Notifications
You must be signed in to change notification settings - Fork 57
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
[MM-57464] Host controls: Lower hand; host controls notifications #705
Conversation
b9c538d
to
f2c14b5
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.
This is awesome @cpoile. Nice work. The only thing I noticed is that in the popout window, the 'user raised hand' notice jumps around strangely when it gets cleared and the 'host lowered your hand' notice animates in (see video below). This seems to happen in both the desktop app and browser. Can we make that cleaner?
Screen.Recording.2024-04-24.at.10.24.04.AM.mov
Thanks @matthewbirtch , I've fixed it, let me know if this works for you. I can delay the "host lowered your hand" chip even more if you want there to be a moment before it shows. |
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.
Looks great to me @cpoile!
server/api_router.go
Outdated
@@ -98,6 +98,7 @@ func (p *Plugin) newAPIRouter() *mux.Router { | |||
hostCtrlRouter.HandleFunc("/make", p.handleMakeHost).Methods("POST") | |||
hostCtrlRouter.HandleFunc("/mute", p.handleMuteSession).Methods("POST") | |||
hostCtrlRouter.HandleFunc("/screen-off", p.handleScreenOff).Methods("POST") | |||
hostCtrlRouter.HandleFunc("/unraise-hand", p.handleUnraiseHand).Methods("POST") |
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.
I'd also expect this to become lower-hand
, and in the new methods as well.
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.
🤦
@@ -1350,6 +1350,7 @@ const ReactionOverlay = styled.div` | |||
display: flex; | |||
flex-direction: column; | |||
gap: 12px; | |||
pointer-events: none; |
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.
I guess this is what you mentioned before. Will events pass through without altering the stack order?
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.
Yep, which is what we want -- we don't want to mess with the z-index of the reactions or notifications or error message boxes, those have to be on top, but we don't want the div they're on to intercept the pointer events.
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.
Cool, will need to merge this into my work as well, thanks.
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.
Nice work!
webapp/src/actions.ts
Outdated
@@ -596,3 +596,13 @@ export const stopScreenshare = async (callID: string, sessionID: string) => { | |||
}, | |||
); | |||
}; | |||
|
|||
export const unraiseHand = async (callID: string, sessionID: string) => { |
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.
-> lowerHand
, you asked for it :)
Summary
Ticket Link