Stack shift on 800X 600 Display on OSX

Sannyasin Sivakatirswami katir at hindu.org
Wed Dec 24 23:40:53 EST 2003


Well, I think now we can distinquish two issues. the clipping of the 
bottom of the stack is a one... and is in our other thread... this is 
different... this has to do with  opening a substack into the same 
window ID as the main stack, which by the way was my way of opening a 
splash screen and then moving to a substack... (see your other thread 
on that subject) The advantage being that this seems to be the only way 
you can add a visual effect to the transition.

Unfortunately there is a a "gotcha" at 800 X 600 and it appears both on 
Mac OS X and Windows:

At 800 X 600 the substack does not open in the exact same location as 
the splash screen, but jumps up by the distance of the title bar of the 
splash screen stack.

anyway, I needed to wrap this project up.. I switched to the hide and 
show stack strategy, but then Locking and unlocking the screen also 
caused havoc, the screen would not completely update and pixels from 
the stack that was being hidden were appearing to clip the top stack 
that was begin shown... work around: remove all such shinanigans and
  and two lines of code with a nice effect turns into 5 lines with an 
abrupt screen cut. But this works fine.


    --visual effect dissolve very fast
     --open  stack "dws Intro" in window "dws youth"

     put the loc of this stack into tPresentLoc
     go invisible stack "dws Intro"
     set the loc of stack "dws intro" to tPresentLoc
     hide stack "dws youth"
     show stack "dws intro"

that works... As for the height clipping, we learned our lesson... 
follow the old presentation developer's guideline for video and slide 
production "Stay away from the edges!"

Sannyasin Sivakatirswami
Himalayan Academy Publications
at Kauai's Hindu Monastery
katir at hindu.org

www.HimalayanAcademy.com,
www.HinduismToday.com
www.Gurudeva.org
www.Hindu.org



Tom wrote:

+++++++
FWIW,

800x600 on my G4 15" laptop does that bottom cut off thing and is fine 
in XP and 2000. I adjusted my stack to fix this at startup to handle 
this on 800x600 screens BUT now on XP I have too much space at top and 
bottom. It appears 800x600 is not the same in all worlds to me.

I wonder if OSX has issues with 800x600 screen sizes???

Or it's a bug. :-)

Tom
+++++++++

On Dec 22, 2003, at 12:36 AM, katir at hindu.org wrote:

Again this is happening on stacks you can check out yourself at:

http://www.himalayanacademy.com/books/dws_youth/

Scenario is that I have a "home"  splash screen stack that is 750 X 550 
set to open at the screenloc on start up, which it does. Then, to open 
a substack I am using:

  open stack "dws Youth" in window (the windowID of this stack)

Now, when i open run this on my cinema display, it appears in the 
center of the screen as expected. clicking the "begin" button which 
calls the substack into the same window works perfectly -- it snaps 
exactly into place over the previous mainstack.  so far so good... and 
my navigation buttons which are running at the bottom right of the 
stack close to the edge appear fine also.

but, when I change the display to 800 X 600,  opening the main stack 
does work. it comes in at the screen loc,  just below the mac menu bar 
with the title bar of the stack shown, but now, when I hit "Begin" and 
call the substack into the main stack window space, something strange 
happens. The substack appears, but is offset upward by the distance of 
its' title bar. This appears to the user as a jump upward on the 
screen. what seems to be happening is that the top left coordinate of 
the stack window image area,  just below the title bar of the stack,  
i.e. NOT the topleft of the substack's title bar, is "posted" so  to 
speak to the top left of the window where the main stack previously 
was, but that coordinate was the top left corner of the title bar of 
the main stack... not it's "image" area.... The substack now has it's 
title bar under the mac menubar. this behavior was also report by 
someone with a 800 X 600 display, so I don't think is just a local 
anamoly in the OSX shift



More information about the Use-livecode mailing list