Bug #1286
closed
Urgent hints and counters in window title are wrong with multiple windows (Azoth)
Added by krigstask about 11 years ago.
Updated almost 11 years ago.
Description
1. Open window with two chat tabs (the first window).
2. Detach one of tabs (that would make the second window).
3. Wait until new message arrives to the second window.
4. Marvel at the first window with urgent hint.
Also, when I have one message for Contact1 and one for Contact2, window titles are expected to be '(1) Contact1' and '(1) Contact2'. Instead they are '(2) Contact1' and 'Contact1'. Probably the same problem.
- Category set to Plugins: AN
- Status changed from New to Assigned
- Assignee set to 0xd34df00d
- Target version set to 0.6.60
What window should get the urgent hint if the corresponding tab is closed?
The roster one if auto-opening's off, and the one where message is auto-opened when it's on, I should think.
Handling auto-opening case would either require the tab to be opened just for the notification, or we lose the ability to make the auto-opening more flexible (by inspecting, say, tab name) later.
krigstask wrote:
Instead they are '(2) Contact1' and 'Contact1'.
Are you sure both are Contact1?
I'm sure that was a typo, sorry.
'(2) Contact1' and 'Contact2', of course.
0xd34df00d wrote:
Handling auto-opening case would either require the tab to be opened just for the notification
How do you mean? Of course tab should be opened for notification.
krigstask wrote:
0xd34df00d wrote:
Handling auto-opening case would either require the tab to be opened just for the notification
How do you mean? Of course tab should be opened for notification.
It should only be opened if the user has chosen to open the message. That is, after user has interacted with notification, but I meant that it should be opened (or at least created, which is also a kludge, invisible, though) to test what window it will go to.
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Applied in changeset main|commit:fa89152cd3e9fba343c71443d964df5fabe40a6a.
- Estimated time set to 4:00 h
A month has passed, assuming it's working.
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by