9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] once more: drawterm osx-x11 on x86-64
Date: Sun,  1 Mar 2015 23:55:49 -0800	[thread overview]
Message-ID: <c9b35f9be243863e68126afc3cfafd07@brasstown.quanstro.net> (raw)
In-Reply-To: <20150228082917.835A5B827@mail.bitblocks.com>

On Sat Feb 28 00:30:20 PST 2015, bakul@bitblocks.com wrote:
> On Sat, 28 Feb 2015 09:18:24 +0100 cinap_lenrek@felloff.net wrote:
> > i ment in the context of rio resize.
>
> Presumably he means his carefully laid out rio windows get out
> of kilter (or alignment) when they all get resized. You need a
> layout engine to keep them looking nice and proportionate.

alignment might not be the best term for it.  resizing the screen
causes rio to scale each window to fit the new screen.  the distances
from the edge are also scaled.  this has the advantage that
screen transitions x->(y->x)* are idempotent.

there is no way currently for a program to treat the screen in a more
sophisticated manner.

On Fri Feb 27 18:15:25 PST 2015, sstallion@gmail.com wrote:
> I might be alone in this, but the resize drives me up the wall. I've had to
> go out of the way to patch rio to ignore resize updates. I suspect the
> reason for this is my riostart creates a few windows by default, which end
> up getting resized when I fullscreen drawterm, throwing everything out of
> whack. It would be nice if you could add a command line option for this - I
> started looking at this, but haven't had much time to make a proper patch.

i don't see not dealing with screen resizes at all as fundamentally better.
i also have this issue, and on a small drawterm on my impossibly small-screen'd
mac, resizing causes the default faces configuration goes right across the screen,
but not resizing would cause the stats window to disappear off to the right.

a quick hack would be to probe the screen pix dimensions and change
behavior based on that.

but i don't immediately see what the right approach is.  do we force windows
to declare hints about how they should be resized and when?  how does resizing
interact with dpi?

- erik



  reply	other threads:[~2015-03-02  7:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27  0:00 Mark van Atten
2015-02-27 22:40 ` Mark van Atten
2015-02-27 23:10 ` Jeff Sickel
2015-02-27 23:27   ` Mark van Atten
2015-02-28  1:19     ` Jeff Sickel
2015-02-28  2:14       ` Steven Stallion
2015-02-28  8:07         ` cinap_lenrek
2015-02-28  8:13           ` lucio
2015-02-28  8:18             ` cinap_lenrek
2015-02-28  8:29               ` Bakul Shah
2015-03-02  7:55                 ` erik quanstrom [this message]
2015-03-02  8:47                   ` Steve Simon
2015-02-28  9:17       ` Mark van Atten
2015-02-28  0:39   ` yy
2015-02-28  1:09   ` Sean Hinchee
2015-02-28  1:35     ` Jeff Sickel
2015-02-28 18:05 sl
2015-02-28 18:29 ` Bakul Shah
2015-03-10 17:32 michaelian ennis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c9b35f9be243863e68126afc3cfafd07@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).