Re: moving stack

2004-12-13 Thread Robert Brenstein
Upward shifted by approximately a titlebar's height.
At what place in the opening sequence is the window reduced to hide 
the menubar?  Or would it be better to get the loc and adjust it to 
account for the menubar before storing it?

Shari
I think it may be simpler to correct the loc before saving it since 
the situation is very clear at that point. Half of the height of the 
menugroup is probably about the same as height of titlebar.

Robert
___
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard


Re: moving stack

2004-12-12 Thread Shari
open stack xyz
set the loc of stack xyz to cd fld someField of stack savePreferences
-- switch the order is what i find helpful. i ran into this before.
andrew
Trouble I'm running into is that it remembers the wrong coordinates. 
When I save the coordinates for future reference, somehow Metacard is 
calculating the titlebar into it.  When I save the loc of the stack, 
it saves the loc, but when I close/open the stack and reset it to the 
saved loc, it is opening at a location slightly higher than the 
location that was supposed to be saved.  Just enough to assume the 
titlebar is the culprit.

I can't find anything anywhere about the height of the titlebar to 
take it into account and open to the new location accordingly.

set the loc of stack xyz to the savedLoc - the titlebar height
That's what would fix it, but that doesn't exist.
I did however discover that one of the cards seems to have gotten 
larger than the stack size.  Don't know how and the card sizes never 
change.  It opens at the proper stack size but when I get the rect of 
the card versus the rect of the stack, there is a HUGE difference. 
(More than the differential of the savedLocation issue.)

Shari
--
Mac and Windows shareware games
http://www.gypsyware.com
___
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard


Re: moving stack

2004-12-12 Thread Robert Brenstein
Trouble I'm running into is that it remembers the wrong coordinates. 
When I save the coordinates for future reference, somehow Metacard 
is calculating the titlebar into it.  When I save the loc of the 
stack, it saves the loc, but when I close/open the stack and reset 
it to the saved loc, it is opening at a location slightly higher 
than the location that was supposed to be saved.  Just enough to 
assume the titlebar is the culprit.

I can't find anything anywhere about the height of the titlebar to 
take it into account and open to the new location accordingly.

set the loc of stack xyz to the savedLoc - the titlebar height
That's what would fix it, but that doesn't exist.
I did however discover that one of the cards seems to have gotten 
larger than the stack size.  Don't know how and the card sizes never 
change.  It opens at the proper stack size but when I get the rect 
of the card versus the rect of the stack, there is a HUGE 
difference. (More than the differential of the savedLocation issue.)

Shari
Would you happen to have a menubar in that stack? May be that is the 
cause of the shift. I can imagine that the loc returns the loc of the 
visible portion of the stack whereas you set it upon reopening before 
the window was reduced to hide the menubar group.

Robert Brenstein
___
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard


Re: moving stack

2004-12-12 Thread Ken Ray
On 12/12/04 9:45 AM, Shari [EMAIL PROTECTED] wrote:

 open stack xyz
 set the loc of stack xyz to cd fld someField of stack savePreferences
 
 -- switch the order is what i find helpful. i ran into this before.
 
 andrew
 
 Trouble I'm running into is that it remembers the wrong coordinates.
 When I save the coordinates for future reference, somehow Metacard is
 calculating the titlebar into it.  When I save the loc of the stack,
 it saves the loc, but when I close/open the stack and reset it to the
 saved loc, it is opening at a location slightly higher than the
 location that was supposed to be saved.  Just enough to assume the
 titlebar is the culprit.

Do you have a menubar? If so, *that* most likely is the culprit, since on
Mac, the amount of space for the titlebar is removed from the stack.


Ken Ray
Sons of Thunder Software
Web site: http://www.sonsothunder.com/
Email: [EMAIL PROTECTED]


___
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard


Re: moving stack

2004-12-12 Thread Shari
Would you happen to have a menubar in that stack? May be that is the 
cause of the shift. I can imagine that the loc returns the loc of 
the visible portion of the stack whereas you set it upon reopening 
before the window was reduced to hide the menubar group.

Robert Brenstein
There is a menubar, yes.
I turn the stack into a standalone on OSX, with the menubar hidden, 
and the standalone has the same upward shift problem.  There is an 
option to save the location of the standalone.  User puts window 
where he wants it, clicks the SAVE button, and it gets the loc of the 
standalone and stores it.

In the preopen stack handler, it gets the stored loc and sets the loc 
of the stack to it.

Upward shifted by approximately a titlebar's height.
At what place in the opening sequence is the window reduced to hide 
the menubar?  Or would it be better to get the loc and adjust it to 
account for the menubar before storing it?

Shari
--
Mac and Windows shareware games
http://www.gypsyware.com
___
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard


Re: moving stack

2004-12-11 Thread Meitnik

In a message dated 12/11/04 12:05:31 PM, [EMAIL PROTECTED] writes:


open stack xyz
set the loc of stack xyz to cd fld someField of stack savePreferences

-- switch the order is what i find helpful. i ran into this before.

andrew
___
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard