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

Show vault locked/unlocked state in the vault title in the tray menu #2101

Merged

Conversation

kevinstsauveur
Copy link
Contributor

Closes #1583.

Description

This PR adds the unlock status to the name of the vault in the tray. It adds * as a prefix to each unlocked vault. I tried it as a suffix like it was described in the issue but the marker is less obvious since the name of each vault is not consistent.

With this new feature, it's easier than ever to find exactly which vaults are unlocked with a visual marker in the list.

Example

Here's an example with testvault as an unlocked vault and testvault2 as a locked fault.

2022-03-14 02_47_58-

@CLAassistant
Copy link

CLAassistant commented Mar 14, 2022

CLA assistant check
All committers have signed the CLA.

@kevinstsauveur
Copy link
Contributor Author

Please take note that the CI Pull Request / Compile and Test (pull_request) fails because of One or more dependencies were identified with vulnerabilities that have a CVSS score greater than or equal to '0.0'. It is not due to my changes.

@infeo
Copy link
Member

infeo commented Mar 16, 2022

@kevinstsauveur Thanks for the PR!

We are working currently on fixing the CI, the vulnerability message is a false positive (see also jeremylong/DependencyCheck#4177). I checked out the branch locally, everything seems to work.

@tobihagemann What do you say about using * as an unlock indicator? Due to using AWT in the tray, we are unfortunately restricted to use only ASCII-characters as any kind of indication.

@tobihagemann
Copy link
Member

Sorry for the late response. I've been thinking about this every now and then. To be honest, I would prefer a solution that doesn't look like from 1997 but I guess AWT is just that old. Really just ASCII? Even a bullet point won't work? In that case, I'm okay with *.

But I'd prefer a space between * and the display name.

@kevinstsauveur
Copy link
Contributor Author

kevinstsauveur commented Mar 21, 2022

It seems like it's working on my side with unicode characters (this would have to be thoroughly tested with other systems, maybe @infeo could give us more insight on this limitation). Here's an example with U+002A *, U+2713 and U+2022 (the bullet in awt would not be my choice judging by the resulting icon) and succeded with a space as suggested.

image * image ✓ image •


This is the result of an exploration of other possibilities without adding markers but playing with the font. First font is italic and the second is bold. I find those two options way less obvious to see and are difficult to differentiate. I prefer prefix.

image image

@tobihagemann
Copy link
Member

Thank you for exploring all the different options! 🚀 My vote is for the first option with a * prefix.

@infeo
Copy link
Member

infeo commented Mar 21, 2022

According to #1474 (and the blocking java upstream issue), Unicode chars are not supported.

I assume that due some windows specialiality the checkmark works (fun fact: also the victory hand ✌️ ). But what the hidden scheme is I cannot say and I doubt it would be a os-independent approach.

@infeo infeo self-assigned this Mar 22, 2022
@infeo infeo merged commit 303f841 into cryptomator:develop Mar 22, 2022
@infeo infeo added this to the 1.6.7 milestone Mar 22, 2022
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.

Show vault locked/unlocked state in the vault title
5 participants