| From: | |
| Date: | 06 Feb 2001 at 23:52:15 |
| Subject: | Re: Custom screens (was: Re: Can someone look at this code?) |
Hello Xavier,
>> As long as you don't call SetDefaultPubScreen() then no windows will
>> mess up your display. [...]
> Untrue. [...]
Please elaborate! Are you talking about if the user runs a public screen
manager? Cause if he do so then surely it's because he wants to control
where windows should appear. I'm simply saying that by default you
shouldn't worry about visitor windows simply because you make your
screen public (which was the argument toward custom screens), further
actions will have to be taken by the user for this to happen.
>> [...] Reminds me a little of the demo-days, where
>> people went through a lot of trouble to make sure that graphics and
>> modules couldn't be ripped from the demos.
> I believe you mean they tried to make the demo do a whole lot very
> quickly with a small size. Well, efficiency has nothing to do with
> scattering .iff .8svx and .mod files all over the place. And when you
> freeze/kill the OS the odds of any filesystems still being alive are
> dubious.
No this is not what I ment. Some had special code to detect Action
Replay etc. Besides, it was just a side node.
>> No-one considered that users wanted to hear the modules in trackers
>> running in the backgroumd, use the graphics for backgrounds pictures,
>> or print them in magazines when reviewing demos etc.
> A reviewer for a publication of a decent size would not find getting
> screenshots difficult.
I happen to know that it *was* a real problem for some! As I understood
it they photographed the monitor for the best result, thus needed a way
to freeze the demo or simply make a screen dump for static display.
> And I've seen quite a few demo mods out and about.
So? I didn't say all made an effort to obfuscate their music, nor that
patient "hackers" didn't manage to rip the music, or that the musician
simply gave it away...
>> Why is there some strange idea that the programmer knows what the
>> user want,
> Why is there some strange idea that all users know what the programmer
> wants? :-)
That idea has certainly escaped my attention. But based on your reply
I'm assuming that you're just a smart ass...
>> and should try to limit the user in a way that's not just avoiding
>> mistakes, but gives the super user a lot of trouble doing the things
>> he'd like to do?
> Because making the computer do its thing is more important. A 68000 at
> 7.15 MHz doesn't offer the headroom a dual Athlon 1.2GHz with a
> GeForce chip does.
What has this to do with anything? You may argue that a custom screens
allows you to bypass some system functions and thus do more lowlevel
rendering, but I've already touched this subject in another letter.
Besides, I doubt this is really the case. If it is then you're probably
just a lame programmer!
------------------------ Yahoo! Groups Sponsor ---------------------~-~>
eGroups is now Yahoo! Groups
Click here for more details
http://click.egroups.com/1/11231/0/_/451227/_/981500012/
---------------------------------------------------------------------_->