Skip to content
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

Update Yami.qss and Rachni.qss to remove dotted border in OBS UI #7614

Closed
wants to merge 3 commits into from
Closed

Conversation

RoadToDream
Copy link

@RoadToDream RoadToDream commented Oct 18, 2022

Description

Before:
image

After:
image

Motivation and Context

Dotted box on ListWidget doesn't feels consistent with the overall UI design.

How Has This Been Tested?

Tested after build.

Types of changes

Minor UI modification.

Checklist:

  • My code has been run through clang-format.
  • I have read the contributing document.
  • My code is not on the master branch.
  • The code has been tested.
  • All commit messages are properly formatted and commits squashed where appropriate.
  • I have included updates to all appropriate documentation.

@derrod derrod requested a review from Warchamp7 October 18, 2022 19:10
@RoadToDream RoadToDream changed the title Update Yami.qss to remove dotted border in OBS UI Update Yami.qss and Rachni.qss to remove dotted border in OBS UI Oct 18, 2022
@Fenrirthviti
Copy link
Member

This is actually an accessibility feature, that shows the current keyboard focus. We probably shouldn't remove it.

@RoadToDream
Copy link
Author

Sorry I was not aware of this consideration. I will close it.

@RoadToDream RoadToDream reopened this Oct 28, 2022
@RoadToDream
Copy link
Author

Upon re-checking OBS code, this UI choice should not be related to accessibility feature as buttons already highlighted while selected by arrow keys. No need to say, dotted line around buttons is not unified across the app, dotted line around buttons in Scene dock is not behaving the same as the Sources dock. I would say removal of the dotted line will give OBS a cleaner look and not sacrificing functionality from accessibility point of view.
Correct me if I am wrong.
image
image

@Fenrirthviti
Copy link
Member

While the visual inconsistency should definitely be corrected (I agree that the sources dock line looks better here, and not all elements are showing focus), you are misunderstanding the point. It is not showing a selected item, it is showing a focused item. If you click (or use tab to cycle) away from a scene or source, the focus is no longer on that, and now on something else. The dotted line shows current focus. Without it, there is no other way to determine what focus is.

https://pub.rachni.com/vid/obs64_2022-10-28_12-28-56.webm

@RoadToDream
Copy link
Author

Thank you for the detailed explanation! I now understand the dotted line is useful when there are multiple docks. I didn't get it before as the tab behavior doesn't cover many ui components so I was thinking using tab to navigate is not a designed behavior.
Like in settings panel. Tab or arrow key will not only indicate selection by a bounding dotted box but also make the selection. Also some object is highlightable via tab at UI element level(Buttons, dropdown), others can only be selected at dock level(Audio Mixer for example.) I guess these inconsistencies make me overlook the intention of this design.

@Fenrirthviti
Copy link
Member

I think it would probably be better to update parts of the UI where the selection box is inconsistent, and the way that the sources list displays it is far less intrusive/off-looking than the settings window or the scenes list, but if I recall there were issues with getting it to display properly like that in some cases.

I defer to @Warchamp7 on this, but probably better suited for an issue post. I'll create that myself next week, unless you'd like to, as I think it's something that does need to be tracked for accessibility.

@RoadToDream
Copy link
Author

RoadToDream commented Oct 29, 2022

Thank you for putting efforts on it. Would be great to have a discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants