From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mimir.eigenstate.org ([206.124.132.107]) by ewsd; Tue Nov 24 18:35:38 -0500 2020
Received: from abbatoir.fios-router.home (pool-74-101-2-6.nycmny.fios.verizon.net [74.101.2.6])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 5330ddd5 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO);
	Tue, 24 Nov 2020 15:35:28 -0800 (PST)
Message-ID: <288D9AF57CE80B394F1E5B40EA69B2D4@eigenstate.org>
To: amavect@gmail.com
To: 9front@9front.org
Subject: Re: [9front] rio: resize flash patch
Date: Tue, 24 Nov 2020 15:35:26 -0800
From: ori@eigenstate.org
In-Reply-To: <94c8a395-0467-9296-92da-ebe20b127955@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: scale-out lifecycle shader-based full-stack cloud 

Quoth Amavect <amavect@gmail.com>:
> On 11/22/2020 10:57 AM, cinap_lenrek@felloff.net wrote:
> > also imagine what happens when a graphical program outputs
> > debug prints. or just sysfatal.
> > 
> > i guess you could catch this by disabling that optimization
> > once the program also writes to the windows cons file after
> > the mouse file has been opend.
> > 
> > --
> > cinap
> > 
> 
> Debug prints work just fine (unless you see something I don't).
> This patch only affects resizing or moving the window.
> 
> Thanks,
> Amavect
> 

Thinking about this a bit more -- I *think* I'm ok with
documenting that the holder of /dev/mouse is responsible
for refreshing on resize.

If that's not something we want to do, it should also be
possible to write a message to wctl to claim responsibility
for refreshing a window, and making that explicit.