Ticket #2243 (new enhancement)

Opened 2 years ago

Last modified 5 months ago

Treat system errors as other messages

Reported by: dottedmag@… Owned by: asterix
Priority: normal Milestone: 0.13
Component: usability Version:
Severity: normal Keywords: discuss
Cc: OS: All

Description

I have choosen 'Show new events only in roster' option in preferences. This, in nutshell, means 'I want to control when to respond to messages, please do not bug me with popups'.

This works fine with ordinary messages, but not with authorization requests or transport-level errors: they interrupt my current work, stealing focus from the window I working with and popping up window I did not request, which is very disturbing.

I propose to pop up all messages in the manner which is used for ordinary messages: just add 'new message' mark to the roster and popup all the 'connection lost' or 'foobar requires authorization' dialogs when user explicitly asks to do it, either clicking roster or using gajim-remote.

Attachments

Change History

Changed 2 years ago by dkirov

Slightly related to #859.

Modal dialogs should be gone!

Changed 2 years ago by dottedmag@…

My rant about transport-level errors is the complete duplicate of #859.

However, there are more popups (even non-modal dialogs), which are also disturbing.

Probably it worth to rename this bug to something like "All messages in interface MUST follow selected 'When new event is received' interaction mode".

Changed 2 years ago by asterix

these messages could change account row icon to message icon for

autorization, connection lost, etc events

Changed 22 months ago by jim++

  • milestone set to 0.12

Auth can be related to contact I think. For things like connection lost, good idea I think.

Changed 16 months ago by anonymous

  • component changed from None to usability

Changed 14 months ago by roidelapluie

  • keywords discuss added
  • os set to All

Changed 5 months ago by steve-e

  • milestone changed from 0.12 to 0.13

I really like the idea of making messages, warnings and popups less intrusive and sticky to roster or chat window.

We will care about that when adding the infrastructure for the plugin system.

There is some cool widget code in HotWire? that we can use: http://picasaweb.google.com/cgwalters/HotwireScreenshots/photo#5181027568000792850

Add/Change #2243 (Treat system errors as other messages)

Author



Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change. Next status will be 'new'
The owner will change to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.