Hi Torge and all,
it works for me in a 3.2 alpha image 4913. Havent tested it in 3.3.alpha.
It's nice - maybe we use it to solve a common problem:
When one uses Squeak on a machine with 1024x768 and have some morph's at the bottom right corner of the screen he's/she's not able to access them on a machine with a smaller screen (800x600). It's the same problem if you work full screen with Squeak and change to the smaller window mode later.
Maybe the standard world background is modified to have the AutoScroll functionality, so if we move the mouse to the squeak windows border region it is checked if the world is larger.
What do you all think? Bye Torsten
On Friday 27 September 2002 04:08 am, Torsten.Bergmann@phaidros.com wrote:
When one uses Squeak on a machine with 1024x768 and have some morph's at the bottom right corner of the screen he's/she's not able to access them on a machine with a smaller screen (800x600). It's the same problem if you work full screen with Squeak and change to the smaller window mode later.
Maybe the standard world background is modified to have the AutoScroll functionality, so if we move the mouse to the squeak windows border region it is checked if the world is larger.
What do you all think?
I'd like to use this with Connectors; I'll take a look at it. I think ideally there'd be some kind of automatically-appearing widget (scroll bar(s), etc.) that would give the user some kind of indication that there were morphs outside the visible area. Maybe a little icon could be drawn in the corners (in a subclass, of course) indicating the off-screen presence of things. I'll look at it when I have some free cycles (I actually have a consulting gig now and am trying to beat a very close deadline).
Hi Thorsten and all,
I looked into it a bit and dind't quite succeed. The problem i had is that my ScrollRegion won't forward mouse events in the way that TransformMorph does. This i should fix anyway because without it the uses are somewhat limited. My way of proceeding: - Insert a hook in DisplayScreen class>>checkForNewScreenSize(hopefully the same method is called on startUp as on resize) - In the hook *check for shrinking size *check for Morphs outside new bounds(other than Flaps * reproduce the code from: Morph>>inATwoWayScrollPane.
Now all non-flap morphs are inside a TwoWayScrollPane with the ScrollBars partly hidden by the flap tabs. The user can choose to enable auto scroll but will no longer be able to click on anything(to be fixed).
changeset attached, Torge
P.S.: Thanks for trying my cs and apologies for the rather rude tone of my last message. Just a little frustrated.
Torsten.Bergmann@phaidros.com wrote:
Hi Torge and all,
it works for me in a 3.2 alpha image 4913. Havent tested it in 3.3.alpha.
It's nice - maybe we use it to solve a common problem:
When one uses Squeak on a machine with 1024x768 and have some morph's at the bottom right corner of the screen he's/she's not able to access them on a machine with a smaller screen (800x600). It's the same problem if you work full screen with Squeak and change to the smaller window mode later.
Maybe the standard world background is modified to have the AutoScroll functionality, so if we move the mouse to the squeak windows border region it is checked if the world is larger.
What do you all think? Bye Torsten
squeak-dev@lists.squeakfoundation.org