Ticket #333 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

Chat focus settings are broken

Reported by: valerio Owned by: valerio
Priority: critical Milestone: kmess-2.0
Component: GUI - Chat window Version: 2.0-alpha
Keywords: Cc:

Description (last modified by valerio) (diff)

This ticket is related to this topic.

The methods which decides when to show new chatwindows, when to switch between tabs, etc, is totally broken. For the nth time :P

Change History

Changed 3 years ago by valerio

  • description modified (diff)

Changed 3 years ago by sifcenter

I hope with r3699 it's fixed. Anyway I leave the ticket open.

Changed 3 years ago by valerio

Everything regarding chat focus is currently working okay, except for a small glitch: sometimes a new chat tab being created by a contact starting a chat with you, switches tab to the new one by itself.

Changed 3 years ago by diederik

The tab focus issue is also mentioned here: http://www.kmess.org/board/viewtopic.php?f=4&t=3391

Changed 3 years ago by valerio

There was another issue, new chats being created as minimized weren't being shown at all in the task manager: that was a KDE task manager bug, promptly  fixed by aseigo. Once more the KDE devs amaze me :D

Changed 3 years ago by valerio

 This topic also reports about broken focus settings.

Changed 3 years ago by sifcenter

I think the problem is that the following: if contact B changes his picture for example, kmess ( contact A ) opens a SB ( and the UserStartedChat() is setted to true ) with contact B to retrieve the information about it .. if in the whiletime contact B writes to Contact A, the client of contact B will re-use the already started SB. At this time kmess decides to give the focus through raiseChat( newChat, switchboard->getUserStartedChat() ). So, what do you think about the way to follow?

Changed 3 years ago by sifcenter

I think I fixed it at r4045, anyway I leave this ticket opened...

Changed 3 years ago by valerio

  • status changed from new to closed
  • resolution set to fixed

It's working perfectly now, I'll close this :)

Note: See TracTickets for help on using tickets.