| Saviq | JohnLea, hey, a question about MM changes, we're missing the case when there are two screens on top of each other | 08:44 |
|---|---|---|
| Saviq | JohnLea, are you aware that you can actually drag the black bar between the screens in the Displays settings? | 08:45 |
| Saviq | that changes the primary display | 08:45 |
| Saviq | I wonder if we should maybe leverage that (gnome-shell does that) | 08:46 |
| Saviq | so instead of saying "on leftmost monitor only", say "on primary monitor only" | 08:46 |
| Saviq | swilson, I'll repeat for you as you're probably interested, too | 08:46 |
| Saviq | <Saviq> JohnLea, hey, a question about MM changes, we're missing the case when there are two screens on top of each other | 08:47 |
| Saviq | <Saviq> JohnLea, are you aware that you can actually drag the black bar between the screens in the Displays settings? | 08:47 |
| Saviq | that changes the primary display | 08:47 |
| Saviq | I wonder if we should maybe leverage that (gnome-shell does that) | 08:47 |
| Saviq | <Saviq> so instead of saying "on leftmost monitor only", say "on primary monitor only" | 08:47 |
| swilson | Saviq: Hi there. Yep, I know about the draggable black bar, but not sure users would easily make the association that the Primary display is the one with the black bar in the Displays panel | 08:53 |
| Saviq | swilson, sure, that would have to be more discoverable | 08:53 |
| swilson | But agree with the problem that we are otherwise allowing the system to make an arbitrary choice for the user if both displays are left-most | 08:53 |
| Saviq | swilson, we could have a drop-down of screens to say which is primary | 08:53 |
| Saviq | (probably) | 08:53 |
| swilson | We want to avoid the user having to know about the concept of a Primary display as much as possible... | 08:54 |
| swilson | ...so instead we could offer a list of displays in the Launcher position drop-down, along with the option All Displays | 08:54 |
| Saviq | yup | 08:54 |
| Saviq | wanted to write just that | 08:54 |
| Saviq | as it is now we're completely ignoring the "a above b" scenario | 08:55 |
| Saviq | when there's no single "left-most" screen | 08:55 |
| Saviq | another question that's not answered in the doc, what do we do with the dash showing on non-launcher screen? display it along the left edge of current screen? | 08:56 |
| swilson | good question. also need to think about how to dismiss a fullscreen dash on a display without a launcher | 08:58 |
| swilson | will have a think through that one, chat with John this morning and then update the modifications document | 08:58 |
| Saviq | swilson, thanks, cheers | 08:59 |
| swilson | Saviq: thanks for the catches BTW! If you find any others let me know | 09:00 |
| Saviq | swilson, will do | 09:00 |
| === nuthinking_ is now known as nuthinking | ||
| Saviq | swilson, hey there's another question that needs answering then, if we limit the launcher / dash / hud to just one screen by default | 10:30 |
| Saviq | swilson, what about the top panel? | 10:30 |
| Saviq | and JohnLea a question to you, what about the spread (I'm assuming it's still supposed to be on all screens) | 10:32 |
| swilson | Saviq: we will keep the top panel on each display | 10:32 |
| Saviq | but should it fill the space that's normally taken by the launcher when the launcher isn't there? | 10:32 |
| swilson | the HUD will continue to appear on the display in focus | 10:32 |
| swilson | same with keyboard shortcuts overlay | 10:32 |
| JohnLea | Saviq; and windows will continue to spread on the monitor on which they reside | 10:32 |
| Saviq | swilson, ok, will that end up in the gdoc? | 10:32 |
| swilson | yep, i will make that explicitly clear | 10:33 |
| swilson | spreads still appear on all displays | 10:33 |
| Saviq | and the spread will cover the space that'd otherwise be taken by the launcher? | 10:33 |
| JohnLea | Saviq: yes. Wait until we have the bugs reported before doing anything, we will send you a email when the change is ready go | 10:38 |
| swilson | yes, spread takes up the full display for the launcher-on-one-display case | 10:39 |
| Saviq | JohnLea, swilson, ok, just trying not to miss anything, thanks :) | 10:39 |
| JohnLea | thx for your questioning, we now have some extra clarifications to add to the doc ;-) | 10:40 |
| swilson | Saviq: no worries, very useful to tease out all the cases we need to cover | 10:40 |
| === MacSlow is now known as MacSlow|lunch | ||
| === greyback is now known as greyback|lunch | ||
| === greyback|lunch is now known as greyback | ||
| === MacSlow|lunch is now known as MacSlow | ||
| JohnLea | testtest; ping | 15:22 |
| testtest | JohnLea; ping | 15:22 |
| greyback | swilson: ping | 15:31 |
| greyback | JohnLea: ping | 15:57 |
| === ckpringle_ is now known as ckpringle | ||
| === ckpringle_ is now known as ckpringle | ||
| === nuthinking_ is now known as nuthinking | ||
| === nuthinking_ is now known as nuthinking | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!