9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] graphics
Date: Mon,  7 Aug 2000 15:11:02 -0400	[thread overview]
Message-ID: <200008071911.PAA07739@smtp1.fas.harvard.edu> (raw)

	the 'eresized()' routine seems not to be called if the program is not
	waiting on any event. e.g. in one of my earlier implementations i lacked
	a call to ecanread/emouse/emenuhit in the main loop and as a side effect
	eresized was not called when the window was moved... it only started
	working after i added (any) of the abovementioned function calls.

Resize messages are sent over /dev/mouse.
Emouse and friends call eresized when they 
get one.  So if they aren't being called, you'll
ignore resize events.

	it is possible to force the machine to reboot if one mistakingly forgets
	to free the allocimagemix pointer after the recangle is drawn... this seems
	to be a big problem, because i've always assumed a runaway process that
	takes up the entire memory would just be terminated instead of causing
	the machine to reboot... or maybe plan9 does things in a different way?

It shouldn't have rebooted.  That's a bug.
The reason it rebooted is that you ran the
kernel out of image memory, and probably
some allocation somewhere failed and isn't
checked properly.

One of my projects for the coming year is
a reimplementation of most of the draw
stuff, to clean up this sort of thing.  A cursory
look through /sys/src/9/port/devdraw.c
doesn't produce anything promising.

Russ



             reply	other threads:[~2000-08-07 19:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-07 19:11 Russ Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-08-06 17:42 ron minnich
2012-08-06 17:54 ` Charles Forsyth
2012-08-08  1:05   ` ron minnich
2000-08-07 18:30 andrey mirtchovski

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=200008071911.PAA07739@smtp1.fas.harvard.edu \
    --to=rsc@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).