[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34516: Multi-monitor frame sets
From: |
Andy Moreton |
Subject: |
bug#34516: Multi-monitor frame sets |
Date: |
Sun, 24 Feb 2019 22:13:26 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1.92 (windows-nt) |
On Sun 24 Feb 2019, martin rudalics wrote:
>>> You should always use the workarea values for displaying emacs frames.
>
> Much easier said than done.
>
>> Ok, this patch uses the workarea instead:
>
> AFAICT, the workarea may "move" from one display to another. So to be
> on the safe side, code should always assume the presence of a workarea
> even when there's none at the very moment. But I have no idea whether
> the workarea size and position may change when moving from one display
> to another.
Please explain what you mean here with an example, as what you have
written makes no sense.
AndyM
- bug#34516: Multi-monitor frame sets, (continued)
- bug#34516: Multi-monitor frame sets, Andy Moreton, 2019/02/19
- bug#34516: Multi-monitor frame sets, Juri Linkov, 2019/02/19
- bug#34516: Multi-monitor frame sets, Andy Moreton, 2019/02/19
- bug#34516: Multi-monitor frame sets, Juri Linkov, 2019/02/20
- bug#34516: Multi-monitor frame sets, Andy Moreton, 2019/02/20
- bug#34516: Multi-monitor frame sets, Juri Linkov, 2019/02/23
- bug#34516: Multi-monitor frame sets, martin rudalics, 2019/02/24
- bug#34516: Multi-monitor frame sets, Juri Linkov, 2019/02/24
- bug#34516: Multi-monitor frame sets,
Andy Moreton <=
- bug#34516: Multi-monitor frame sets, martin rudalics, 2019/02/25
- bug#34516: Multi-monitor frame sets, Andy Moreton, 2019/02/25