Closed ddgarcia closed 10 years ago
I disagree. That's what small stage mode is for. If you're missing the button on the right that indicates that the actual Snap window is bigger than your browser's current workspace, so simply click in small stage mode to show the run / stop / pause buttons (and be sure not to use an oversized stage).
There is a point where even the small stage is too small, but I'm not sure that's a very common use case...
However, this is another one of those 'nice to haves' we could work on. If your screen is resized to be less than X wide, the stage automatically switches to small mode.
Heh! I've actually implemented this already, it's in the code, but commented out, because I ended up not liking the auto-small stage after all. But you're welcome to experiment with this feature yourself :-)
Small mode is different from a small screen size, isn't it? In small mode all the sprites and lines drawn get smaller, whereas small screen size has normal size sprites etc. I think it would be really confusing to mix those up automagically.
Yup, you're right. That's exactly what bothered me about this feature. I did implement it at one time, because Scratch 1.4 and BYOB did it (which is, I think, why Michael also suggests it). What I don't like about this feature is that when you make the window bigger again, the stage doesn't automagically get bigger again. Now, I think we could also do that, but then you'd loose control over small-stage mode altogether. So, I think, pressing the small-stage/normal-stage toggle in the tool bar isn't too much of a hassle for users...
Closing this, seems to have petered out.
...NOT where the right edge of the stage is (which gets cut off when the screen is small), making it impossible to run projects on small windows...![screen shot 2014-02-12 at 5 50 03 am](https://f.cloud.github.com/assets/2229297/2148942/5cb56fd6-93ed-11e3-99b2-4d87eaf9051d.png)