gwibber-bugs team mailing list archive

[David Klasinc <bigwhale@xxxxxxxxxx>]

Tiny patch that applies described changes.


** Patch added: "move_bug.patch"
   https://bugs.launchpad.net/gwibber/+bug/719526/+attachment/1852182/+files/move_bug.patch

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/719526

Title:
  Raising a client on dual monitor setup

Status in Gwibber:
  New

Bug description:
  On rare occasions Gwibber client will be raised on the wrong monitor.

  This one is rather difficult to reproduce. Here are the steps:

  - Make sure you have two monitors configured as one big desktop (xinerama or AMD's Big Desktop will both be fine)
  - Start Gwibber 
  - Make sure that client is on the first monitor
  - Quit Gwibber (completely so that gwibber-service dies)
  - Start Gwibber again
  - Move the Client window to the second monitor
  - Click on the Messages indicator and and select Messages (or whatever) under the Broadcast.
  - Gwibber will be raised and moved to the first monitor

  Why this happens? (see client.py)
  Because self.save_window_settings() is called only in on_quit() and on_window_close(). When Gwibber is started on the first monitor and then moved to the second one nobody tells it that it was moved.

  Quick fix:

  Add to GwibberClient's setup_ui()
    self.connect("configure-event", self.on_window_end_move)

  And then add another method that will handle this:
    def on_window_end_move(self, *args):
      self.save_window_settings()