Stack no long resizable?

[Mark MacKenzie]

Thank you.  In fact the resizable check box was checked for resizable.  
I acutally toggled this several times in my efforts to track down the 
problem.  No luck at all.

Then I decided to take the "fix everything including the dead simple you 
should have thought of this first stuff".  None of the GUI controls 
fixed this BUT, using your script actually I did it before reading your 
reply but it was the step that reset things to "normal".  So what we do 
know is that in my stack situation, deleting the window resize widget 
object, set something which was not reachable by the GUI reizable stack 
check box but was reachable through the message box and a script.  That 
is perhaps the most important knowledge gained.

Thank you Sarah.

Mark MacKenzie

Sarah Reichelt wrote:

> This is probably a silly question, but are you sure you haven't 
> un-checked the "Resizable" box in the "Size & Position" section of the 
> Stack inspector?
>
> There is a script method of checking/un-checking this and I wonder if 
> your installation of the palette resizer object messed with this. The 
> script would be: set the resizable of this stack to true/false
>
> Cheers,
> Sarah
>
> On 14 Feb 2004, at 11:22 am, Mark MacKenzie wrote:
>
>> I have a stack that is no longer resizeable in the development 
>> platform or when in the browse cursor form.
>>
>> I can change its dimensions within the property inspector (stack) and 
>> the stack resizes and stays that way but I cannot grab the window 
>> frame and resize it..  The min  settings are each at 32 while the 
>> max   is at 575 and 600 pixels.  The stack mode is toplevel. It is a 
>> substack of another stack which is in palette mode.
>> The can't delete function is enabled but the stack is left in 
>> modifiable form within the property inspector.
>>
>> I did once use that object palette rezier object in a test.  Ran into 
>> problems with it and deleted it from the stack.  I cannot find any 
>> scripting which would disable the direct resizable character of this 
>> stack.
>>
>> Can anyone suggest how I can effectively get this back without having 
>> to input numbers into the respective property inspector?
>
>