Open Bug 473866 Opened 11 years ago Updated 11 years ago
Make toggling Aggressiv Notify easier
Currently the following steps are needed to switch aggressive notify state. 1. Click Chatzilla menu 2. Click Preferences 3. Click Global Settings 4. Click Global tab 5. Click checkbox 6. Click OK This is my most often used function in Chatzilla because the warnings under Windows are really aggressive. I would like to have a much more prominent button on the programs surface. Best is a new button. A solution with a submenu under the Back/Away button would also be fine.
Type these two commands... /alias agro pref notify.aggressive /alias toggle-agro toggle-pref notify.aggressive Now you can turn agressive notify on with "/agro true", and off with "/agro false". If you just want to see the current state, "/agro". Finally, to toggle the current state "/toggle-agro".
I don't really know anyone else who regularly toggles this on/off. At least for me, it only gets triggered if I want to know, and then I really want to know, so I'm happy it gets triggered? Proposing WONTFIX, also based on the workaround in comment #1.
Severity: normal → enhancement
OS: Windows XP → All
Hardware: x86 → All
Summary: FR: Instantly clickable button for toggling Aggressiv Notify → Make toggling Aggressiv Notify easier
Version: unspecified → Trunk
Hb, can you explain exactly when and why you turn the agressive notify off?
When I want to work undisturbed I turn agressive notify off. Alternatively setting the Away state is not good because the other side on the query gets an away message or a similar response. Not to be forced to answer is the most polite reaction in these cases.
(In reply to comment #4) > When I want to work undisturbed I turn agressive notify off. Alternatively > setting the Away state is not good because the other side on the query gets an > away message or a similar response. Not to be forced to answer is the most > polite reaction in these cases. ChatZilla doesn't do automatic away replies. People could whois you and you'd be set to away, but that's it. I'm not sure how it would be more polite to claim to be "there" when in fact you're not.
You need to log in before you can comment on or make changes to this bug.