On Sun, 6 Feb 2000, Andrew Apted wrote:
> Marcus Sundberg writes:
>
> > Well, Andrew is wrong. The functionality does not belong there, and
> > you gain nothing by putting it there.
>
> Imagine this: one process using display-file to output (via mmap) a
> constantly changing image to a file. Another process using
> display-file to read that image (again via mmap) and displaying it.
>
> There are no-doubt other ways of achieve the same thing, but could it
> get any simpler (and more intuitive) than that ?
Now you're seeing what I was planning for that @#%@% movie player.
The silly beast is becoming multitasking now... turns out multithreading
works -beautifully- if you use wait states properly. Actually the beast
is better at playing mp3's on my computer than mpg123 thanks to this :)
But you need a fast enough CPU...
Anyways, another part of such an exchange is some for of coordination
between reader and writer on when the screen is safe for update...
(isn't memory-target better for this? :)
G'day, eh? :)
- Teunis
