> I had X die on me twice because of something like that- once because I
> started Netscape while running twelve xquakes, and once because of a typo
> in freesci/src/core/resource.c ;-)
Hm. I've never had X die on me. I've had situations where I
couldn't do ls in a terminal because there wasn't enough ram to load the
program, too. I suspect that it largely depends on the server, though,
since the server for each card is pretty different.
> > while(!space) {
> > write_to_frame_buffer("Out of memory\n (free some up to
> > continue)");
>
> This requires the graphics target to handle the memory shortage correctly,
> of course.
Yes. :-)
However, you want to make as many links in a chain strong as
possible. And besides, there shouldn't be too much of a memory requirement
for ggi once it is initialized since it just has buffers in shared memory
which are copied back and forth. I couldn't see any other sane arrangement
so it really should just be resetting values in arrays. There will still be
weak spots, but better to have fewer weak spots than more, no?
> sleep() gets interrupted by signals (and GGI uses a signal to synchronize
> the screen). A better way to handle this would be to call the
> graphics target's "wait" function (which also reads mouse events and
> updates the pointer position)
Possible. Would ggi process events so that we'd get them queued up,
or what in its delay function? Are you sure that it has one, btw?
> Doing a few memcpy()s and calling s->gfx_driver->Redraw() should suffice.
Ok. I'll look up what to do in a little bit (probably the next week
or so). For the moment where should I put the empty function sci_malloc()
(which right now would just be a pass-through to malloc())? I mean so that
anyone who does coding can use sci_malloc instead of malloc and when we add
the functionality, it will automatically be there.
> Sounds good. Writing to stderr wouldn't help in fullscreen mode, after
> all.
That's what I was thinking. And it wouldn't help people who launched
freesci from a menu or a gnome button, etc.
Probably wouldn't hurt to print it out. A question or two:
1. Does ggi have rectangle and text drawing functions?
2. Is there an online programming manual/tutorial for ggi like there is for
gtk?
3. What do you think about realloc()? Should that be handled in the code or
should we have an sci_realloc() that does the same sort of thing as
sci_malloc()?
-Chris
--
[EMAIL PROTECTED]
"If I had had more time I would have written a shorter letter." - Pascal
Linux Programs: http://cs.alfred.edu/~lansdoct/linux/
Linux - Get there. Today.
Evil Overlord Quote of the Day (www.eviloverlord.com):
99. Any data file of crucial importance will be padded to 1.45Mb in size.
