o3de / sig-ui-ux

Documents and communications for the O3DE UI/UX Special Interest Group
6 stars 5 forks source link

10-13-2022 - SIG-UI-UX Office Hours (Add your request in comments) #89

Closed amzn-leenguy closed 1 year ago

amzn-leenguy commented 1 year ago

SIG-UI-UX Office Hours for 10-13-2022

Hi O3DE Community, We want to invite you to our UX design review and office hours.

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up the Office Hours.
Please add a comment to this ticket with following information:

This is a weekly meeting will cover the following items.

How do I sign up get feedback?

How can I use office hours:

yuyihsu commented 1 year ago

@jjjoness can you join our office hour on 10/13 to review the file moving/organizing behavior in Asset Browser?

@amzn-mike can you join this office hour to discuss the asset allocation proposal you have with @jjjoness .

mbalfour-amzn commented 1 year ago

Discord username: Mike B [Amazon] Topic of conversation: Quick question for discussion: Most component modes can be exited either by hitting Esc, pressing the "Done" button, or double-clicking. I'd like to disable the double-click exit for painting because it's too easy to do by accident. A) Is this OK? B) Do we need to remove the double-click exit for all component modes for consistency?

How much time you might need: Hopefully < 5 minutes? Any UX resource you have already been working with and if their attendance is required. Josh Rainbolt. Attendance not required, but appreciated.

amzn-leenguy commented 1 year ago

Thanks for coming to us for office hours for this @mbalfour-amzn . We are happy to help. @rainbj I have conflict for today's office hours with a legal review, but I trust you handle this one on my behalf (Since I worked on developing Component Mode in the viewport). Thank you!

mbalfour-amzn commented 1 year ago

As a follow-up to this, the answer is that removing the double-click-to-exit behavior for all component modes has already been discussed between UX and the Viewport team, so I'll post a PR to remove this default behavior for all component modes.