| 2016-07-14 13:51:29 |
Andreas Pokorny |
bug |
|
|
added bug |
| 2016-07-14 13:52:11 |
Andreas Pokorny |
bug task added |
|
miral |
|
| 2016-07-14 13:52:59 |
Andreas Pokorny |
description |
Due to the order in which certain window types are created in gtk, the gdk backend for mir gets two positioning requests when constructing a tooltip. The second one contains the right relative position, but it happens after the surface was constructed by the backend. The default window manager policies in mir and miral seem to ignore the new position. |
Due to the order in which certain window types are created in gtk, the gdk backend for mir gets two positioning requests when constructing a tooltip. The second one contains the right relative position, but it happens after the surface was constructed by the backend. The default window manager policies in mir and miral seem to ignore the new position.
I think clients should be allowed to change menu and tooltip positions as necessary. |
|
| 2016-07-14 13:56:20 |
Alan Griffiths |
miral: status |
New |
Confirmed |
|
| 2016-07-14 13:56:24 |
Alan Griffiths |
miral: importance |
Undecided |
High |
|
| 2016-07-14 13:56:28 |
Alan Griffiths |
miral: assignee |
|
Alan Griffiths (alan-griffiths) |
|
| 2016-07-14 13:56:32 |
Alan Griffiths |
mir: importance |
Undecided |
Low |
|
| 2016-07-14 13:56:37 |
Alan Griffiths |
mir: status |
New |
Confirmed |
|
| 2016-07-14 16:45:48 |
Alan Griffiths |
branch linked |
|
lp:~alan-griffiths/miral/fix-1603086 |
|
| 2016-07-15 01:47:15 |
Daniel van Vugt |
tags |
|
gtk-mir |
|
| 2016-07-15 01:47:27 |
Daniel van Vugt |
mir: importance |
Low |
Medium |
|
| 2016-07-15 10:10:52 |
Andreas Pokorny |
description |
Due to the order in which certain window types are created in gtk, the gdk backend for mir gets two positioning requests when constructing a tooltip. The second one contains the right relative position, but it happens after the surface was constructed by the backend. The default window manager policies in mir and miral seem to ignore the new position.
I think clients should be allowed to change menu and tooltip positions as necessary. |
gdk/mir basically does:
MirRectangle rect = { x, y, 1 ,1};
mir_connection_create_spec_for_tooltip(connection,
width,
height,
format,
parent_surface,
&rect);
where x, y are the top left corners of the tooltip.
But that part of the spec is not used by our mirservers. |
|
| 2016-07-15 14:58:35 |
Andreas Pokorny |
description |
gdk/mir basically does:
MirRectangle rect = { x, y, 1 ,1};
mir_connection_create_spec_for_tooltip(connection,
width,
height,
format,
parent_surface,
&rect);
where x, y are the top left corners of the tooltip.
But that part of the spec is not used by our mirservers. |
Due to the order in which certain window types are created in gtk, the gdk backend for mir gets two positioning requests when constructing a tooltip.
Tooltips are represented as menus in the mir backend of gdk.
The second surface spec contains the right relative position, but it happens after the surface was constructed by the backend. The default window manager policies in mir and miral seem to ignore the new position. |
|
| 2016-07-18 02:07:06 |
Daniel van Vugt |
miral: status |
Confirmed |
In Progress |
|
| 2016-08-29 10:17:00 |
Alan Griffiths |
miral: status |
In Progress |
Fix Committed |
|
| 2016-09-22 11:09:17 |
Alan Griffiths |
miral: status |
Fix Committed |
Fix Released |
|
| 2017-11-03 16:28:08 |
Michał Sawicz |
mir (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-11-03 16:28:08 |
Michał Sawicz |
mir (Ubuntu): status |
New |
Confirmed |
|
