You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like using InvisibleTyping, however I sometimes prefer having my typing status enabled rather than disabled. Because of this, having to re-enable my typing indicator every time I restart discord (in global mode) or every time I change channels (in whitelist mode) gets very tedious.
I saw there was a setting in the config file called autoEnable, however this setting changes the plugin from whitelist mode to global mode.
It would be very nice if the default typing-enabled state of the plugin was exposed to the user as a setting.
The text was updated successfully, but these errors were encountered:
If you right-click the Icon, you can toggle between globally enabled and globally disabled
I did not know that was possible, it would be nice if it was documented somewhere.
I have found some additional problems though:
(Important) The Enable/Disable Globally in the button's context-menu is opposite of the toggle in the BD settings, which is very confusing. My proposed solution is to rename the BD setting from Globally Toggle to Whitelist Mode.
(QoL) "Global mode" actually being a blacklist mode feels a bit unintuitive in my opinion. Having the choice between a whitelist mode, blacklist mode, and global on/off would be better, though would probably also mean a partial rewrite.
I like using InvisibleTyping, however I sometimes prefer having my typing status enabled rather than disabled. Because of this, having to re-enable my typing indicator every time I restart discord (in global mode) or every time I change channels (in whitelist mode) gets very tedious.
I saw there was a setting in the config file called
autoEnable
, however this setting changes the plugin from whitelist mode to global mode.It would be very nice if the default typing-enabled state of the plugin was exposed to the user as a setting.
The text was updated successfully, but these errors were encountered: