I guess I'll have to try the testing procedure you suggest. The problem is that I don't own a Windows machine, so the testing cycle time is *greatly* elongated. I'll get back to you all about this part, but it will take a while....

Re the standalone settings, is there some particular setting that would give this (non-resizable) behavior? I can't see it by inspection in the standalone settings panel. And it works in the Mac build, so...???

And, any ideas, anyone, on the non-response of the option-menu in Windows?

-- Peter

Peter M. Brigham
[EMAIL PROTECTED]
http://home.comcast.net/~pmbrig/

-- LOTTERY, n. A tax on people who are bad at math.

PS: it just occurred to me to look at my mainstack (stays invisible, opens the datastack), which is *not* resizable, I have just set this to be resizable in case somehow this property of the mainstack is transferred erroneously in Windows to the visible datastack. I'll test that out too.


On Jan 5, 2008 10:13 AM, Peter Brigham <[EMAIL PROTECTED]> wrote:

Any advice appreciated. I realize that some of this must be obvious
to those more experienced than I, but I'm trying to learn....

For my limited brain power, I'd go back to basics, I'd create a brand new
resizeable stack, with one button and script:

on mouseUp
  beep
end mouseUp

Save, create a standalone and see if it is resizeable in Win.

if (resizeable = false) then
  clearly some setting somewhere is incorrect
  Win users can make resizeable stacks
  track the incorrect setting down
  it may be a stack setting or a standalone builder setting
  get this simple stack to resize in Win
  remove all your workarounds in your recipe stack
  set the settings as above
else
  clearly your workarounds are not required
  remove them ALL
  messages are probably being lost
  in your recipe stack
  insert multiple "answer" dialogs throughout scripts
  ie answer "Step 1", answer "Step 2", answer "Step 3"
  good locations would be at the beginning & end of any
  preOpenStack
  preOpenCard
  OpenStack
  OpenCard scripts
  build as standalone
  for the Win build
  track down where the stack skips or doesn't answer
  this is probably where the Win build is going wrong
  check the docs, you may be using a Mac only feature
  fix as necessary
end if

Aaahhh, sorry, natural language scripting can be addictive ;-)

HTH

_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to