What is supposed to be the effect of DisplayScreen
tim at sumeru.stanford.edu
Tue Apr 1 01:43:34 UTC 2003
> Well, the intent is pretty simple ;-) Just give people a way of making
> things at certain resolutions without screwing up their environment
> permantly. Try to get as close as you can to a reasonable interpretation of
> the request if it can't be done "properly". If you think it through from
> that point of view the behavior becomes perfectly well-defined.
That's ok then. So resolution first, fullscreen if it can be done, depth
optional if it can be done. Remember original screen resolution when
entering fullscreen and return to it when exiting fullscreen. Fail if
you can't get 'reasonably' close where 'reasonable' is not well-defined.
> > Not to mention that some prims are expected to return
> > true/false to say if they failed and others are expected to use
> > primitiveFailed()....
> I actually don't care whether you #primitiveFail() or return true/false as
> long as the result is that if the primitive "succeeds" then the resolution
> of Squeak's main display has the requested resolution (not including
Not so much an issue related to this particular prim as a more general
annoyance. We need to be more careful and consistent with these things.
Compare ioSetDisplayMode() which _must_ return true or false with
ioSetFullScreen() whose return value is ignored and we have to
At least we need to document which is meant somewhere reasonable! Like
so much else...
Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
Where the system is concerned, you are not allowed to ask "Why?".
More information about the Squeak-dev