RE: In standalone, closing a modal closes everything

2007-02-02 Thread Mark Powell
Hi Chipp/Trevor

By chance, have you implemented something to work around this bug?  Wait
for fix?  Subject users as is?  If testing for engine version, then
what?  I am at an impasse.  Nothing seems quite workable to me.

Mark

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chipp
Walters
Sent: Thursday, February 01, 2007 9:17 AM
To: How to use Revolution
Subject: Re: In standalone, closing a modal closes everything

Yeah Mark, that's the bug. I believe Trevor's well documented it and I
believe I've heard it's fixed in a newer version, when it gets released.

On 1/31/07, Mark Powell [EMAIL PROTECTED] wrote:

 This, I believe, is the bug in 2.7.2 that Chipp raised a few weeks 
 back.  Am I right?  Anyone know if that little bug has been fixed?

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: In standalone, closing a modal closes everything

2007-02-01 Thread Chipp Walters

Yeah Mark, that's the bug. I believe Trevor's well documented it and I
believe I've heard it's fixed in a newer version, when it gets released.

On 1/31/07, Mark Powell [EMAIL PROTECTED] wrote:


This, I believe, is the bug in 2.7.2 that Chipp
raised a few weeks back.  Am I right?  Anyone know if that little bug
has been fixed?


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


RE: In standalone, closing a modal closes everything

2007-01-31 Thread Mark Powell
Well, I guess it is fixed.  I had had no closeStack handler in the
substack, but when I place

  on closeStack
  
  end closeStack
 
into the stack script of the substack, the resulting executable works.
Apparently, a call within the substack button to 'close this stack' or
'close stack License' sends a closeStack message up the hierarchy?  I
did not realize this...I thought the button script had to specifically
say 'closeStack' to yield that result.  

So 'close this stack' in the button apparently reaches the following in
the stack script of the main stack

  on closeStack
if the environment is not development then quit
  end closeStack

which I guess explains why I was not having a problem in the development
environment.

Thanks everybody for bearing with me.

Mark
 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chipp
Walters
Sent: Tuesday, January 30, 2007 12:11 PM
To: How to use Revolution
Subject: Re: In standalone, closing a modal closes everything

I imagine the closeStack message is being sent to your mainStack (not
the altSplash stack). If you don't change the originating call, then
handle it in the card or stack script of the mainStack.
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: In standalone, closing a modal closes everything

2007-01-31 Thread Mark Smith
Mark, the closeStack message is sent by the engine when a stack is  
closed (a sort of notification that the user has closed a stack), and  
like other messages, will pass up the message path unless trapped.


so if you wanted to use it to make sure the standalone actually quits  
when the mainstack is closed, rather than any stack, you could do this:


in the mainstack script:
on closeStack
  if the environment is not development AND the target is me then  
quit

end close stack

See also : shutdown, shutdownRequest, closeStackRequest

best,

Mark

On 31 Jan 2007, at 12:16, Mark Powell wrote:


 on closeStack
if the environment is not development then quit
  end closeStack


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


RE: In standalone, closing a modal closes everything

2007-01-31 Thread Mark Powell
Aaargh.  I solved the one problem (trapping the closeStack handler) so
that the rev application does not quit improperly.

However, now a new one has come up.  The closing of the modal *SUSPENDS*
the application (throws the focus onto Outlook, Photoshop, or some other
application)!  The rev application is still in the taskbar, it just is
not active anymore.   This, I believe, is the bug in 2.7.2 that Chipp
raised a few weeks back.  Am I right?  Anyone know if that little bug
has been fixed?  Or am I again showing my ignorance as to how message
passing is supposed to work?

Thanks very much.

Mark
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: In standalone, closing a modal closes everything

2007-01-30 Thread Richard Gaskin

Mark Powell wrote:


Here is a distillation of my problem.  From my main stack, I call a
stack with 


   modal stack MyAnswerDialog

On that modal stack, there is an OK button with the script ending with

   close this stack


It ends with that -- what comes before it?


--
 Richard Gaskin
 Fourth World Media Corporation
 ___
 [EMAIL PROTECTED]   http://www.FourthWorld.com
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: In standalone, closing a modal closes everything

2007-01-30 Thread Devin Asay

Mark,
On Jan 30, 2007, at 4:46 AM, Mark Powell wrote:


Here is a distillation of my problem.  From my main stack, I call a
stack with

   modal stack MyAnswerDialog

On that modal stack, there is an OK button with the script ending with

   close this stack

In the development environment, the modal is closed as expected and  
you

return to the main stack.  As an executable, clicking the OK button
quits the application (i.e. OK closes both main and modal stacks).   
I am
using Rev 2.7.2.   Am I doing something wrong?  I could have sworn  
this

has worked in the past.


If you use the following, does it still happen in the standalone:

  close stack MyAnswerDialog

?

I'm wondering if, for some reason, the closeStack message is being  
sent up the hierarchy when running in standalone mode. In other  
words, maybe close this stack is being executed by the mainstack  
(the engine in the standalone.)


Devin

Devin Asay
Humanities Technology and Research Support Center
Brigham Young University

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


RE: In standalone, closing a modal closes everything

2007-01-30 Thread Mark Powell


 It ends with that -- what comes before it?

--in main stack, button script is...

on mouseUp
  openLicenseDialog
end mouseUp

--in main stack, stack script is...

on openLicenseDialog
  modal stack License
end openLicenseDialog

--in stack License, button script is...

on mouseUp
  RequestDone
end mouseUp

--in stack License, stack script is...
on RequestDone
  simple variable checks here
  close this stack
end RequestDone

BTW, Devin, I have tried saying specifically 

close stack License

but the result is the same.

I should clarify one thing.  In development it works as expected.  In
the standalone model, I am using the altSplash methodology, so the
splash screen is technically the executable, while the main stack
referenced above is an un-compiled stack.

Also, I know there has been a bug in one version of Rev or another of
focus switching out of Rev into another application.  I experience that
with 2.7.2.  I can hack together a small sample of what I am talking
about later today, but any idea beforehand are greatly appreciated.



___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: In standalone, closing a modal closes everything

2007-01-30 Thread Chipp Walters

I imagine the closeStack message is being sent to your mainStack (not the
altSplash stack). If you don't change the originating call, then handle it
in the card or stack script of the mainStack.
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution