Bug 750 - decoder menu opens on wrong monitor
Summary: decoder menu opens on wrong monitor
Status: RESOLVED INVALID
Alias: None
Product: PulseView
Classification: Unclassified
Component: Data display (show other bugs)
Version: 0.3.0
Hardware: All Linux
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-08 11:29 CET by Christian Thäter
Modified: 2017-05-07 08:00 CEST (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Thäter 2016-02-08 11:29:06 CET
running pulsview in i3-wm on a dual monitor setup, layout as following:

------------------------------------
|External Monitor   |              |
|  editor           |  terminal    |
|                   |              |
|                   |              |
|-----------------------------------
|                                  |
| pulseview                        |
|                                  |
|                                  |
------------------------------------

      --------------------
      | Laptop Screen    |
      |                  |
      |                  |
      |                  |
      --------------------


when opening the 'Add Decoder' menubox it gets entirely displayed on the Laptop Screen below the External Monitor. This only happens when the Menu won't fit in the space from the top of the Pulseview window to the bottom of the screen. Resizing Pulseview, moving it to the top or running it fullscreen works. Seems there is something wrong when calculating the available space.
Comment 1 Soeren Apel 2016-04-17 22:27:24 CEST
To be honest, this sounds like a WM (or Qt, albeit unlikely) issue to me. I'm tempted to close it as invalid as the offending widget is a standard QToolButton and there's nothing we can do here.

I would like you to check the behavior of the menu (Alt -> Decoders -> Add) which contains the same list. Does it get pushed onto a different monitor as well? If so then it's definitely a WM issue. If not then it's still ambiguous.
Comment 2 Soeren Apel 2017-05-07 08:00:14 CEST
No user feedback for 1 year and most likely a Qt/WM issue, so closing as invalid.