X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3EA8A3858D39
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=cs.umass.edu
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=cs.umass.edu
Subject: Re: Confusing Cygwin X / xlaunch issue
To: Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>,
        The Cygwin Mailing List <cygwin AT cygwin DOT com>
References: <1e4edecf-166c-e3c1-f961-b31bfa01271f AT cs DOT umass DOT edu>
 <deb23c76-5095-f3a8-d4ce-e3070a9286b1 AT dronecode DOT org DOT uk>
From: Eliot Moss <moss AT cs DOT umass DOT edu>
Message-ID: <f0622ea9-b6ac-8421-47c9-7f4ce341f70e@cs.umass.edu>
Date: Tue, 26 Oct 2021 16:38:13 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101
 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <deb23c76-5095-f3a8-d4ce-e3070a9286b1@dronecode.org.uk>
Content-Language: en-US
X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 NICE_REPLY_A, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To: moss AT cs DOT umass DOT edu
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 19QFcWh9001000

On 10/26/2021 4:02 PM, Jon Turney wrote:
> On 24/10/2021 12:01, Eliot Moss wrote:
>> First, things work fine when I am using just my hi-res laptop display, or that
>> display plus a hi-res external display in "Extend these displays" mode
>> according to Windows 10.  At present I am using a lower resolution external
>> display (becaue I am on an extended trip and it's what I have) in "Extend
>> these displays" mode with my hi-res laptop display.  This seems to confuse X
>> (and also xlaunch?).  Here are the issues:
> 
> Thanks for reporting this problem.

>> When booted with the external lo-res display as the main display:
>>
>> - xterm windows come up with a very large font.
>> - The X menu (controlled by .XWinrc) does not come up.
> 
> This means that you're right-clicking on the notification area icon, but no menu appears?

Correct.

> If so, I guess this means that we're getting confused about where to place the menu, but I'm not 
> sure how that could happen.

> wrt the font scaling issue, looking at the source, it seems that we don't re-consider the display 
> dpi after a WM_DISPLAYCHANGE message, but keep on using the value determined at startup.  This is 
> probably a bug.
> 
>  > winInitializeScreenDefaults - primary monitor w 3240 h 2160
>  > winInitializeScreenDefaults - native DPI x 192 y 192
> [...]
>  > [  1035.750] winWindowProc - WM_DISPLAYCHANGE - new width: 2560 new height: 2048 new bpp: 32
> 
> As a workaround, you might experiment with using the xserver option '-dpi' to set a value 
> corresponding to your hi-res display, so that will be used even if the normal-res display is 
> Windows' primary monitor.

That didn't hurt at least.  I did not go to the trouble of rebooting,
but given that I had booted to the hi-res Window and then started X
with the lo-res as primary, the font scaling was right.  The menu still
did not come up, though.  That seems to require starting X with the
hi-res Window - the one that was primary when Windows was booted.

Regards - Eliot

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple