[GH-ISSUE #263] Systray "connected" icon #213

New issue

Open

opened 2026-05-05 05:41:41 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 05:41:41 -06:00

Owner

Originally created by @wjtk4444 on GitHub (Mar 8, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/263

As far as I'm concerned, currently there are two different tray icons.

the "default" barrier icon meaning that the program is running
icon with a green "checkbox" meaning that server is running

Having an additional icon which informs user that barrier is connected to client(s) would be very useful. Currently there's no way (other than actually opening the user interface, selecting "show log" option and reading trough it) of telling whether there are any connected clients or not.

I would propose to do something like that: (sorry for the poor quality, it's just a concept)

Left to right:
server stopped | server running | connected to client(s)

I'm not familiar with barrier's code base, but it seems like something that doesn't require too much of an effort to implement. If you approve the general idea of this feature but do not have spare time to take care of it - please let me know. I might do it myself and open a pull request.

Originally created by @wjtk4444 on GitHub (Mar 8, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/263 As far as I'm concerned, currently there are two different tray icons. - the "default" barrier icon meaning that the program is running - icon with a green "checkbox" meaning that server is running Having an additional icon which informs user that barrier is connected to client(s) would be very useful. Currently there's no way (other than actually opening the user interface, selecting "show log" option and reading trough it) of telling whether there are any connected clients or not. I would propose to do something like that: (sorry for the poor quality, it's just a concept) ![image](https://user-images.githubusercontent.com/20820296/54039855-ddf4ab80-41bb-11e9-8382-ec30d91988f9.png) Left to right: server stopped | server running | connected to client(s) I'm not familiar with barrier's code base, but it seems like something that doesn't require too much of an effort to implement. If you approve the general idea of this feature but do not have spare time to take care of it - please let me know. I might do it myself and open a pull request.

gitea-mirror added the

enhancement

good first issue

labels 2026-05-05 05:41:41 -06:00

gitea-mirror commented

2026-05-05 05:41:44 -06:00

Author

Owner

@ghost commented on GitHub (Jul 1, 2019):

I would like this feature very much, for the client as well. The states we've got for the client are:
1 Client not running (X)
2 Client running but not connected (blank)
3 Client running and connected (checkmark)

Currently the checkmark icon covers states 2 and 3. This could be improved.

@ghost commented on GitHub (Jul 1, 2019): I would like this feature very much, for the client as well. The states we've got for the client are: 1 Client not running (X) 2 Client running but not connected (blank) 3 Client running and connected (checkmark) Currently the checkmark icon covers states 2 and 3. This could be improved.

gitea-mirror commented

2026-05-05 05:41:47 -06:00

Author

Owner

@voidplayer commented on GitHub (Dec 16, 2021):

latest 2.4 just landed on debian from 2.3.x

First very noticeable thing is that systray icon dont have green tick when theres a connection

in 2.3.x and before it was already working as you are describing. A checkmark when a connection is established and none when is just running

I was wondering if this is a debian bug and was checking the bug reports and find this enhancement proposal

@voidplayer commented on GitHub (Dec 16, 2021): latest 2.4 just landed on debian from 2.3.x First very noticeable thing is that systray icon dont have green tick when theres a connection in 2.3.x and before it was already working as you are describing. A checkmark when a connection is established and none when is just running I was wondering if this is a debian bug and was checking the bug reports and find this enhancement proposal

gitea-mirror referenced this issue

2026-05-05 07:56:49 -06:00

[PR #214] [MERGED] Macos build issues #1579