Auto-Away feature not very accessible
See original GitHub issueSo I thought it would be great if TL could automatically set myself away when I detach all clients. Turns out someone already had the idea and it was already implemented in #775. It didn’t work for me though.
I found out that this block is never being executed because client.awayMessage is an empty string. Apparently it has to be set in the user config. Setting myself away on a network just changes the network’s awayMessage item, not the one of the user itself.
So, if I understand correctly: in order to get the auto away feature working, the user (or their admin) has to edit the user.json file and set an away message - that is not very intuitive.
I suggest adding an input field for the user.awayMessage
to the settings, so users could set their away message (without needing access to their config file) and by doing so, enable or disable the auto away feature.
It could have a placeholder text like “Set a message to enable auto away” or “leave empty to disable auto away” or something.
This way,
- it becomes clear that TL has an auto-away feature
- every user, even those without access to their user config file, is able to enable/disable that feature
- the feature works out of the box
Issue Analytics
- State:
- Created 6 years ago
- Reactions:16
- Comments:7 (4 by maintainers)
Top GitHub Comments
This will be trivial to add to client settings, since we have client settings syncing now.
I’ll do this after the client has been ported to Vue.
As promised: #3549