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

Colors for participants are not different enough #1547

Closed
boarder2 opened this issue Jan 21, 2019 · 5 comments
Closed

Colors for participants are not different enough #1547

boarder2 opened this issue Jan 21, 2019 · 5 comments

Comments

@boarder2
Copy link

When multiple participants are in a live share, the colors that are auto assigned can be very difficult to distinguish even when there is a small number of participants. See screenshot.

Product and Version [VS/VSCode]: VSCode
OS Version [macOS/Windows]: Windows
Live Share Extension Version: 0.3.1120

Steps to Reproduce / Scenario:

  1. Have multiple people join the share

Screenshots
untitled

@lostintangent
Copy link
Member

Yeah this is really good feedback. We should make sure the colors are more visually distinct, at least up to 5 user count (which is the default guest limit).

@valerionew
Copy link

New user here and i really second this, any update on the progress?

@jtgrenz
Copy link

jtgrenz commented Apr 26, 2022

It would be really great if you can manually set the colour of the participants as well. Right now with the theme I'm using, I can't read anything the other participant has highlighted. Liveshare has defaulted the highlight colour to bright yellow and I lose the contrast.

I know it would be difficult to automatically adjust the livehsare highlight colour to work with a given colour scheme, so being able to manually set it would fix my issue here and the similarity issue from the OP for multiple participants

image

@setaskin
Copy link

@fubaduba

@setaskin setaskin assigned fubaduba and unassigned legomushroom Apr 27, 2022
@derekbekoe derekbekoe added this to the Jan-Mar 2023 (uncommitted) milestone Nov 12, 2022
@derekbekoe derekbekoe removed this from the Jan-Mar 2023 (uncommitted) milestone Mar 28, 2023
@derekbekoe
Copy link
Collaborator

We’re not able to prioritize this issue over the other higher-impact issues we receive every week, based on the votes and comments from others in the community and our understanding of the issue. We understand this may be disappointing; we've all been there, whether in this project or others we've contributed to. However, rest assured that we love your input. If you feel it deserves to stay open, then clarify your use case and contact us to let us know how severe it’s for you.

@derekbekoe derekbekoe closed this as not planned Won't fix, can't repro, duplicate, stale Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants