Geometry Manager [was: newbie: when to use substacks?]

Sarah sarahr at genesearch.com.au
Tue Jun 3 23:18:01 EDT 2003


If you go the Geometry settings for the actual card (as opposed to any 
object on the card), you can set "Update before opening card" which 
will do this for you automatically.

Sarah

On Tuesday, June 3, 2003, at 03:38  pm, Igor Couto wrote:

> Hi there, Jan!
>
> On Tuesday, June 3, 2003, at 03:20  PM, Jan Schenkel wrote:
>
>> I've been using the Geometry Manager quite a bit the
>> past 3 weeks and never had problems with different
>> cards in the same stack with their own geometry
>> setups.
>
> I think I know what Alex is referring to... Try this:
>
> 1) Create New Stack
>
> 2) Place a field
>
> 3) Use the Geometry Manager to specify that the field should resize 
> (scale) if the stack window is resized.
>
> 4) Create a New Card.
>
> Now, your new card is empty.
>
> 5) While you are in your new card, RESIZE THE STACK WINDOW.
>
> 6) Go to the first card, where our field is. Voila! The field has not 
> resized...
>
> Note that if you resize the stack NOW, while you are on the first 
> card, then the field WILL resize as specified. So it seems that the 
> Geometry Manager specs work ONLY for the current, active card being 
> resized - not all the other cards in the stack... That is kind of 
> efficient - I can see the reason to keep it that way - but on the 
> other hand, when the user opens a new card, shouldn't the Geometry 
> Manager check that the geometry of the objects present satisfy the 
> user specifications?
>
> Is there a command we can put in a scrip on preOpenCard, perhaps, that 
> will get the Geometry Manager to do its thing before the card opens?
>
> Many thanks,
> --
> Igor de Oliveira Couto
> ----------------------------------
> igor at pixelmedia.com.au
> ----------------------------------
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>
>
>





More information about the use-livecode mailing list