From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Attempt at making 3D graphics library
Date: Sun, 30 Dec 2007 11:33:03 -0500 [thread overview]
Message-ID: <9D8B8E4B-AE4B-4B59-8BC7-B047E391665D@mac.com> (raw)
In-Reply-To: <d2708561e4eb32e3b56b4a11d572ed55@yourdomain.dom>
Then how do you check for the window resized event? I heard from IRC
#plan9 that resize events are sent through /dev/mouse, so the
following code is the event(2) way of ensuring resize events get done:
for (;;)
if (ecanmouse())
emouse();
On Nov 24, 2007, at 5:48 PM, Federico G. Benavento wrote:
> You're not supposed to combine event(2) with thread(2).
>
> See mouse(2).
>
>
> Federico G. Benavento
>
> ---
> /bin/fortune:
> Steal money you're a thief: steal a country you're a king.
>
> From: Pietro Gagliardi <pietro10@mac.com>
> Date: November 24, 2007 11:21:57 AM EST
> To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
> Subject: Re: [9fans] Attempt at making 3D graphics library
> Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
>
>
>
> On Nov 24, 2007, at 11:00 AM, andrey mirtchovski wrote:
>
>>> Use q to quit (and
>>> crash, for some threadexitsall-related reason).
>>
>> that usually means you need a bigger stack for your threads.
> Setting both threads to 4096 stacksize fixed it. I'll note that in
> my tutorial. I used one thread to interpret mouse events, since for
> some odd reason eresized() is sent through the mouse. :-(
>
>
next prev parent reply other threads:[~2007-12-30 16:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 3:43 Pietro Gagliardi
2007-11-24 6:57 ` Paul Lalonde
2007-11-24 14:19 ` Pietro Gagliardi
2007-11-24 7:11 ` anyrhine
2007-11-24 16:42 ` Pietro Gagliardi
2007-11-24 15:57 ` Pietro Gagliardi
2007-11-24 16:00 ` andrey mirtchovski
2007-11-24 16:21 ` Pietro Gagliardi
2007-11-24 22:48 ` Federico G. Benavento
2007-12-30 16:33 ` Pietro Gagliardi [this message]
2007-12-03 2:54 ` Pietro Gagliardi
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=9D8B8E4B-AE4B-4B59-8BC7-B047E391665D@mac.com \
--to=pietro10@mac.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).