From: Steven Stallion <sstallion@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] once more: drawterm osx-x11 on x86-64
Date: Fri, 27 Feb 2015 20:14:00 -0600 [thread overview]
Message-ID: <CAGGHmKGGOnW=YsUNgxU6usBErd3qMQ5GwafeSTpw=RO7SG2W4g@mail.gmail.com> (raw)
In-Reply-To: <86308593-B4A7-41BF-AEDB-924C66BC5FF3@corpus-callosum.com>
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
On Fri, Feb 27, 2015 at 7:19 PM, Jeff Sickel <jas@corpus-callosum.com>
wrote:
> The older versions of drawterm just map a large view to fill
> the whole screen and then clip the view to the window size you’ve
> selected. When you drag the view it doesn’t resize the internal
> rio content. That meant that when taking a 1280x1024 window to
> 2560x1440 everything would stay the same and you’d just see the
> extra space already allocated. If you draw to the new areas and
> then resize the window back to the smaller rect you lose easy
> access to any rio windows created outside of the current clipping
> rect.
>
> The Cocoa version does proper resizing. It’s just a lot of effort
> to get the same features back into the X11 code base.
>
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.
Cheers,
Steve
[-- Attachment #2: Type: text/html, Size: 1628 bytes --]
next prev parent reply other threads:[~2015-02-28 2:14 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 [this message]
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
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='CAGGHmKGGOnW=YsUNgxU6usBErd3qMQ5GwafeSTpw=RO7SG2W4g@mail.gmail.com' \
--to=sstallion@gmail.com \
--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).