9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@gmx.de
To: 9front@googlegroups.com
Subject: Re: /dev/wsys/*/screen not present for nested rio?
Date: Tue, 8 May 2012 20:57:52 +0200	[thread overview]
Message-ID: <fea8152307f3d428f6495d816e3ae2d6@rei2.9hal> (raw)
In-Reply-To: <1c581e53ec2520d4989053955c2ef15b@sp.inri.net>

the patch that stops serving /dev/screen is here:

1165.1ccc5dd3a9f54176837bc485b128d4ce79493450

the reason we dont serve /dev/screen anymore if its here already there by the
topmost rio is this:

previously, /dev/screen used the image from the display, wich gets initialized
in initdraw(). this is always the whole display image like defined in the
manpage. problem is, that image doesnt work when the screen is resized or
changes its colordepth. like when you run aux/vga to change to a different
mode.

the solution was to use the Image *screen; instead wich gets updated on resize.
problem is, this is always the image of the "window" or whatever your program
(or rio) runs in. so to make it work, only the topmost rio serves the screen
file so the manpage definition of /dev/screen holds and represents the whole
display. similat that only the topmost rio serves /dev/snarf so all programs
and subrios share the same snarf buffer.

--
cinap

  reply	other threads:[~2012-05-08 18:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07  5:28 vrtra
2012-05-07 20:09 ` sl
2012-05-08  4:13   ` vrtra
2012-05-08 12:10     ` sl
2012-05-08 17:56       ` vrtra
2012-05-08 18:23         ` sl
2012-05-08 18:57           ` cinap_lenrek [this message]
2012-05-08 20:49           ` vrtra
2012-05-08 21:10             ` cinap_lenrek

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=fea8152307f3d428f6495d816e3ae2d6@rei2.9hal \
    --to=cinap_lenrek@gmx.de \
    --cc=9front@googlegroups.com \
    /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).