Re: Idle handlers and Text files

2007-11-08 Thread BNig

Hi,

I tested 

on preOpenStack 
   answer moo 
end preOpenStack 

on first card of otherwise empty stack on 
MacBook Pro, System 10.4.10 german, RR 2.8.1, GLX on and off.

it works with doubleclick, drag and drop and starting stack from within
Revolution.

only difference is on doubleclick and drag and drop there is no RR-logo in
the answer dialog box, probably because the icons are not yet available?

hth

bernd



Malte Brill wrote:
 
 Hi Kay,
 
 this is extremly interesting. As you see a different behaviour than  
 me, I suspect it might be a setting somewhere or something that got  
 corrupted on my and other machines. Would love to investigate that.
 
 All the best,
 
 Malte
 ___
 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
 
 

-- 
View this message in context: 
http://www.nabble.com/Re%3A-use-revolution-Digest%2C-Vol-50%2C-Issue-10-tf4756652.html#a13644520
Sent from the Revolution - User mailing list archive at Nabble.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: Idle handlers and Text files

2007-11-08 Thread Malte Brill

Hi Kay,

this is extremly interesting. As you see a different behaviour than  
me, I suspect it might be a setting somewhere or something that got  
corrupted on my and other machines. Would love to investigate that.


All the best,

Malte
___
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: Idle handlers and Text files

2007-11-08 Thread Kay C Lan
On Nov 8, 2007 6:30 PM, BNig [EMAIL PROTECTED] wrote:


 on first card of otherwise empty stack on
 MacBook Pro, System 10.4.10 german, RR 2.8.1, GLX on and off.

 it works with doubleclick, drag and drop and starting stack from within
 Revolution.


Had thought that there may have been something about a German install, but
clearly not.  Do you have any other development environments or frontscripts
(other than GLX) that may be running?

Got an old Rev 2.6 that you can start up and test?
___
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: Idle handlers and Text files

2007-11-07 Thread Mark Schonewille

Yes, and I missed it. Sorry.

Best regards,

Mark Schonewille

--

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Quickly extract data from your HyperCard stacks with DIFfersifier.  
http://differsifier.economy-x-talk.com



Op 7-nov-2007, om 8:49 heeft Malte Brill het volgende geschreven:



I´m suspecting the last line of your script is a typo. Should read

end openStack

However, is button foo on the first card?

All the best,

Malte


___
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: Re: Idle handlers and Text files

2007-11-07 Thread Kay C Lan
On Nov 6, 2007 11:11 PM, Malte Brill [EMAIL PROTECTED] wrote:


 Well, my experience is that it does not get sent if Rev is not yet
 open and you double click on a stack file, or drag the stack to the
 rev icon in the Dock  under Os X.
 If Rev is already open stacks Do get preOpenstack and openStack.


Sorry for coming to this late, but I must differ.

I have preOpenStack handler which determines if the mySQL server is running
and if not, pops up a dialog to tell me that it isn't and that my app is
about to Quit to allow me to start mySQL first. Works like a charm. I quite
often start my app by double clicking when Rev isn't running. I don't Drag 
Drop though, but I just tried it and it worked fine, again without Rev
running in the first place.

App in IDE mode, OSX 10.4.10, Rev 2.8.1, MacTel, with  without GLX2

There must be something in your code.
___
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: Idle handlers and Text files

2007-11-07 Thread Malte Brill

Hi Kay,

following test scenario. Vanilla Stack, first card script reads:

on preOpenStack
  answer moo
end preOpenStack

Save-quit rev, double click - No moo at all

quit rev - open Rev - double click - Moos just fine

same with drag and drop

RR 2.8.1, Intel MacBook, German Os X.4.10, with and without GLX.

ATB,

Malte


___
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: Idle handlers and Text files

2007-11-07 Thread Kay C Lan
On Nov 7, 2007 9:28 PM, Malte Brill [EMAIL PROTECTED] wrote:

 following test scenario. Vanilla Stack, first card script reads:

 on preOpenStack
   answer moo
 end preOpenStack

 Save-quit rev, double click - No moo at all

 quit rev - open Rev - double click - Moos just fine

 same with drag and drop

 RR 2.8.1, Intel MacBook, German Os X.4.10, with and without GLX.


Malte,

Just started Rev, created a brand new Main Stack, copied your handler above
into the card script, Quit Rev and tried both double clicking and Drag 
Drop and 'moo' came up both times.

RR 2.8.1 in IDE mode, Intel MacBook Pro, English OS x.4.10, with and without
GLX

Additionally, I've had this stack working since 2.6, but without the warning
about mySQL server not running. In the preOpenStack handler there is a call
to lookup the last record in a table and present the data. If mySQL wasn't
running I'd just get empty fields, with mySQL running the fields would be
filled so I'm pretty sure preOpenStack has been behaving this way for years
- at least for double clicking as this is how I've normally started this
stack; can't say the same for Drag  Drop as I don't start my stacks that
way.

Need others to test.
___
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: Idle handlers and Text files

2007-11-06 Thread Len Morgan
Along the lines of this discussion, I think someone mentioned that the 
preOpenStack message is NOT sent when you are using the IDE.  Is this 
true?  If so, where can I put start-up code so that I set things up 
before an app gets going in both the IDE and a stand-alone?


Thanks!

len


Mark Schonewille wrote:

Hi Jonathan,

It is recommended to use the send command instead of the idle handler.

on preOpenStack
  send foo to me in 0 millisecs
  pass preOpenStack
end preOpenStack

on foo
  -- do something here
  send foo to me in 200 millisecs
end foo

If the preOpenStack handler doesn't allow you to do this, you made a 
mistake somewhere, which needs to be corrected to avoid problems in 
the future.


If I understand you correctly, you can't send a mouseUp message 
automatically after opening the stack. That also means you made a 
mistake somewhere, which needs to be corrected. I don't think that 
using the idle handler, or send, is a good alternative in this case. 
My advice would be to find out why you can't send that mouseUp command.


The Finder simply updates open windows once in a while, including the 
desktop. It doesn't matter at which level in the hierarchy they are. 
However, if you add or remove a folder, the window gets updated 
instantly.  Not sure that it helps you, but if I do a test writing 
files to a folder or the desktop, I see the file appear instantly on 
my local disks, but not that quickly on network disks.


Best regards,

Mark Schonewille

--

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Quickly extract data from your HyperCard stacks with DIFfersifier. 
http://differsifier.economy-x-talk.com



Op 6-nov-2007, om 9:14 heeft Jonathan Scott het volgende geschreven:


Howdy,
Thank you to everyone who pointed me towards my solutions.
I still don't know exactly what is going on, but here are the 
solutions I figured out after receiving your advice:


openstack not functioning
I just put in a new card with nothing on it (as the first card in 
the stack).  In it's handler I put in an on idle handler that does 
nothing but issue send 'mouseUp' statements and then moves the user 
to another card afterward (to a place where there is no on idle 
handler).


text files not being written
The big problem was that text files were actually being written.  
I just couldn't find them for a few minutes sometimes.  Sometimes I'd 
have to wait a very long time for the files to pop up on the screen.  
My assumption was that the finder's ability to update every viewable 
portion of the hard drive can take a lot of time.  IOW, the file was 
there, it was just that the finder hadn't moved in to update that 
part of the screen yet.  So, my workaround was to have all files be 
saved to a folder on the desktop.  Because the desktop is closer to 
the top of the hierarchical structure, it is probably updated with 
much greater frequency.  I still don't know if this is a good 
decision.  It works though, so I'm happy.


Thanks again everybody.


___
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: Idle handlers and Text files

2007-11-06 Thread Mark Schonewille

Hi Len,

The preOpenStack message should be sent in the IDE when a stack  
opens. I believe there was a bug in a particular version of  
Revolution, which prevented the message from being sent under  
particular circumstances.


The message that is never sent to a stack in the IDE is the startUp  
message.


Best regards,

Mark Schonewille

--

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Quickly extract data from your HyperCard stacks with DIFfersifier.  
http://differsifier.economy-x-talk.com



Op 6-nov-2007, om 14:49 heeft Len Morgan het volgende geschreven:

Along the lines of this discussion, I think someone mentioned that  
the preOpenStack message is NOT sent when you are using the IDE.   
Is this true?  If so, where can I put start-up code so that I set  
things up before an app gets going in both the IDE and a stand-alone?


Thanks!

len



___
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: Idle handlers and Text files

2007-11-06 Thread Richard Gaskin

Len Morgan wrote:
 Along the lines of this discussion, I think someone mentioned that the
 preOpenStack message is NOT sent when you are using the IDE.  Is this
 true?

I don't believe so; AFAIK the IDE does not prevent your stack from 
getting preOpenStack messages.  Perhaps you were thinking of startup?


 If so, where can I put start-up code so that I set things up
 before an app gets going in both the IDE and a stand-alone?

I do initialization from a preOpenStack handler in the card script of 
the first card of the stack file which will be made into a standalone.


--
 Richard Gaskin
 Managing Editor, revJournal
 ___
 Rev tips, tutorials and more: http://www.revJournal.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: Idle handlers and Text files

2007-11-06 Thread BNig

Hi,

in my experience at times the Finder can be slow to update a file but most
of the times this is not a problem for me.

If I really depend on the Finder to be up to date on the file I'm creating I
update the Finder with an applescript. This forces the Finder to update the
file.

You can do this from Revolution:

on mouseUp

answer file choose document
if it is empty then exit mouseUp

-- it contains a path to a file including the filename in revolution
style
put it into theRevPathFile

-- convert the the path from revolution style to mac style for
applescript
put revMacFromUnixPath (theRevPathFile) into theFile

-- build the applescript command
put tell application   quote  Finder  quote  into
UpDateFileWithAppleScript
put return  update filequote  theFile  quote after
UpDateFileWithAppleScript
put return  end tell after UpDateFileWithAppleScript

-- do the applescript
do UpDateFileWithAppleScript as applescript

-- if something went wrong in the applescript the result is not empty
if the result is not empty then put the result

end mouseUp

of course this only shows how it works, to put it into a mouseUp handler
with a choose file will probably not work on a file, which is not yet
updated by the Finder...

So just take the inner part of the handler and provide it with a complete
path (rev style) to the file you want to update after you created it.

fwiw

Bernd



Mark Schonewille-3 wrote:
 
 Hi Jonathan,
 
 
 The Finder simply updates open windows once in a while, including the  
 desktop. It doesn't matter at which level in the hierarchy they are.  
 However, if you add or remove a folder, the window gets updated  
 instantly.  Not sure that it helps you, but if I do a test writing  
 files to a folder or the desktop, I see the file appear instantly on  
 my local disks, but not that quickly on network disks.
 
 Best regards,
 
 Mark Schonewille
 
 
 Op 6-nov-2007, om 9:14 heeft Jonathan Scott het volgende geschreven:
 
 Howdy,
  Thank you to everyone who pointed me towards my solutions.
  I still don't know exactly what is going on, but here are the  
 solutions I figured out after receiving your advice:

 openstack not functioning
  I just put in a new card with nothing on it (as the first card in  
 the stack).  In it's handler I put in an on idle handler that  
 does nothing but issue send 'mouseUp' statements and then moves  
 the user to another card afterward (to a place where there is no  
 on idle handler).

 text files not being written
  The big problem was that text files were actually being written.   
 I just couldn't find them for a few minutes sometimes.  Sometimes  
 I'd have to wait a very long time for the files to pop up on the  
 screen.  My assumption was that the finder's ability to update  
 every viewable portion of the hard drive can take a lot of time.   
 IOW, the file was there, it was just that the finder hadn't moved  
 in to update that part of the screen yet.  So, my workaround was to  
 have all files be saved to a folder on the desktop.  Because the  
 desktop is closer to the top of the hierarchical structure, it is  
 probably updated with much greater frequency.  I still don't know  
 if this is a good decision.  It works though, so I'm happy.

  Thanks again everybody.

 ___
 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
 
 

-- 
View this message in context: 
http://www.nabble.com/Re%3A-use-revolution-Digest%2C-Vol-50%2C-Issue-10-tf4756652.html#a13608036
Sent from the Revolution - User mailing list archive at Nabble.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: Re: Idle handlers and Text files

2007-11-06 Thread Malte Brill

 I don't believe so; AFAIK the IDE does not prevent your stack from
 getting preOpenStack messages.  Perhaps you were thinking of startup?

Well, my experience is that it does not get sent if Rev is not yet  
open and you double click on a stack file, or drag the stack to the  
rev icon in the Dock  under Os X.

If Rev is already open stacks Do get preOpenstack and openStack.

(latest 2.8 version, GLX installed, but I think the reason is the  
normal IDE not GLX)


ATB,

Malte
___
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: Idle handlers and Text files

2007-11-06 Thread Klaus Major

Hi all,


 I don't believe so; AFAIK the IDE does not prevent your stack from
 getting preOpenStack messages.  Perhaps you were thinking of  
startup?


Well, my experience is that it does not get sent if Rev is not yet  
open and you double click on a stack file, or drag the stack to the  
rev icon in the Dock  under Os X.

If Rev is already open stacks Do get preOpenstack and openStack.

(latest 2.8 version, GLX installed, but I think the reason is the  
normal IDE not GLX)


and the IDE definitively catches a custom shutdownrequest handler.

In our current project we make a data backup before the user quits,  
that is triggered by a
shutdownrequest handler in a stack that is also being used!, but  
in the IDE, the app quits

WITHOUT making any backup.


ATB,

Malte


Regards

Klaus Major
[EMAIL PROTECTED]
http://www.major-k.de


___
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: Idle handlers and Text files

2007-11-06 Thread Richard Gaskin

Malte Brill wrote:


  I don't believe so; AFAIK the IDE does not prevent your stack from
  getting preOpenStack messages.  Perhaps you were thinking of startup?

Well, my experience is that it does not get sent if Rev is not yet  
open and you double click on a stack file, or drag the stack to the  
rev icon in the Dock  under Os X.

If Rev is already open stacks Do get preOpenstack and openStack.


Thanks for the clarification, Malte.  The engine's sending it -- do you 
know why it isn't be passed?


--
 Richard Gaskin
 Managing Editor, revJournal
 ___
 Rev tips, tutorials and more: http://www.revJournal.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: Idle handlers and Text files

2007-11-06 Thread Mark Schonewille

Hi Len,

You'd put a preOpenStack handler into the card script of the  
mainstack if you want that script to run only when the mainstack  
opens and not when substacks open. Otherwise, the preOpenStack  
handler would be send up the message hierarchy each time a substack  
is opened.


Best regards,

Mark Schonewille

--

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Quickly extract data from your HyperCard stacks with DIFfersifier.  
http://differsifier.economy-x-talk.com



Op 6-nov-2007, om 16:43 heeft Len Morgan het volgende geschreven:

I probably did confuse the startup message with preOpenStack  
however, I put a simple debug message in my preOpenStack handler  
(which is the STACK script) and it doesn't ever fire (when running  
in the IDE).


The last line of your response brings up a question though: Why  
would you put a preOpenStack message in the first card instead of  
the stack script?  This seems counterintuitive to me.


For what it's worth, I am NOT starting up my stack by double  
clicking on it.  I start up the Rev IDE first (w/ GLX2) and then  
use File-Open Stack to pick my stack.


Len Morgan


___
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: Idle handlers and Text files

2007-11-06 Thread Len Morgan
I probably did confuse the startup message with preOpenStack however, 
I put a simple debug message in my preOpenStack handler (which is the 
STACK script) and it doesn't ever fire (when running in the IDE).


The last line of your response brings up a question though: Why would 
you put a preOpenStack message in the first card instead of the stack 
script?  This seems counterintuitive to me.


For what it's worth, I am NOT starting up my stack by double clicking on 
it.  I start up the Rev IDE first (w/ GLX2) and then use File-Open 
Stack to pick my stack.


Len Morgan


Richard Gaskin wrote:

Len Morgan wrote:
 Along the lines of this discussion, I think someone mentioned that the
 preOpenStack message is NOT sent when you are using the IDE.  Is this
 true?

I don't believe so; AFAIK the IDE does not prevent your stack from 
getting preOpenStack messages.  Perhaps you were thinking of startup?


 If so, where can I put start-up code so that I set things up
 before an app gets going in both the IDE and a stand-alone?

I do initialization from a preOpenStack handler in the card script of 
the first card of the stack file which will be made into a standalone.




___
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: Idle handlers and Text files

2007-11-06 Thread Devin Asay


On Nov 6, 2007, at 8:43 AM, Len Morgan wrote:

I probably did confuse the startup message with preOpenStack  
however, I put a simple debug message in my preOpenStack handler  
(which is the STACK script) and it doesn't ever fire (when running  
in the IDE).


The last line of your response brings up a question though: Why  
would you put a preOpenStack message in the first card instead of  
the stack script?  This seems counterintuitive to me.


One good reason to do this is that when you make the stack into a  
standalone application, the stack in effect becomes the engine.  
Therefore, it is the final stop in the message hierarchy. That means  
that any substack or other stack that your standalone opens, if it  
doesn't have its own preOpenStack handler, will pass the preOpenStack  
message to the engine. You may not want the preOpenStack handler  
there to be activated for other stacks. On the other hand, if you put  
it in the first card's script, it will only run when the application  
is launched (because a stack by default opens to the first card.)


For what it's worth, I am NOT starting up my stack by double  
clicking on it.  I start up the Rev IDE first (w/ GLX2) and then  
use File-Open Stack to pick my stack.


Len Morgan


Richard Gaskin wrote:

Len Morgan wrote:
 Along the lines of this discussion, I think someone mentioned  
that the
 preOpenStack message is NOT sent when you are using the IDE.  Is  
this

 true?

I don't believe so; AFAIK the IDE does not prevent your stack from  
getting preOpenStack messages.  Perhaps you were thinking of startup?


 If so, where can I put start-up code so that I set things up
 before an app gets going in both the IDE and a stand-alone?

I do initialization from a preOpenStack handler in the card script  
of the first card of the stack file which will be made into a  
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: Idle handlers and Text files

2007-11-06 Thread Len Morgan

Hello Mark!

If my first wife had not asked me to get the big snip as an 
anniversary present many years ago, I'd name my next male child after 
you for that little tidbit.  I may still consider re-naming my first 
born male child after you, although at 22, he may have some thoughts on 
the matter.


You have saved me DAYS of frustration in tracking down why my 
preOpenStack is getting executed AGAIN when I quit the app!  Is that 
little item documented anywhere?  Now that I see it in writing and 
knowing (a little) about how the message path works, it makes perfect 
sense.  I guess I always figured that when I opened another stack, the 
message was sent to it.  It never occurred that if there was no 
preOpenStack message, that it would get passed back to the caller!  
Perhaps that is obvious to everyone but me.


Thanks again!!!

len morgan


Mark Schonewille wrote:

Hi Len,

You'd put a preOpenStack handler into the card script of the mainstack 
if you want that script to run only when the mainstack opens and not 
when substacks open. Otherwise, the preOpenStack handler would be send 
up the message hierarchy each time a substack is opened.


Best regards,

Mark Schonewille

--

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Quickly extract data from your HyperCard stacks with DIFfersifier. 
http://differsifier.economy-x-talk.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: Idle handlers and Text files

2007-11-06 Thread Jim Ault
I think you could put a preOpenStack handler in every stack or substack at
the stack script level and choose not to send it along the hierarchy.  This
would allow the use of preOpenStack  in the substacks when desired.

However, this would not be correct if the preOpenStack  message actually got
sent to the main stack in either the IDE or the stand alone.

I have little experience with apps and preOpenStack, so others can give
wiser advice.

Jim Ault
Las Vegas


On 11/6/07 8:13 AM, Len Morgan [EMAIL PROTECTED] wrote:

 Hello Mark!
 
 If my first wife had not asked me to get the big snip as an
 anniversary present many years ago, I'd name my next male child after
 you for that little tidbit.  I may still consider re-naming my first
 born male child after you, although at 22, he may have some thoughts on
 the matter.
 
 You have saved me DAYS of frustration in tracking down why my
 preOpenStack is getting executed AGAIN when I quit the app!  Is that
 little item documented anywhere?  Now that I see it in writing and
 knowing (a little) about how the message path works, it makes perfect
 sense.  I guess I always figured that when I opened another stack, the
 message was sent to it.  It never occurred that if there was no
 preOpenStack message, that it would get passed back to the caller!
 Perhaps that is obvious to everyone but me.
 
 Thanks again!!!
 
 len morgan
 
 
 Mark Schonewille wrote:
 Hi Len,
 
 You'd put a preOpenStack handler into the card script of the mainstack
 if you want that script to run only when the mainstack opens and not
 when substacks open. Otherwise, the preOpenStack handler would be send
 up the message hierarchy each time a substack is opened.
 
 Best regards,
 
 Mark Schonewille
 
 -- 
 
 Economy-x-Talk Consulting and Software Engineering
 http://economy-x-talk.com
 http://www.salery.biz
 
 Quickly extract data from your HyperCard stacks with DIFfersifier.
 http://differsifier.economy-x-talk.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


___
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: Idle handlers and Text files

2007-11-06 Thread Mark Schonewille

Hi Len,

That's really too much honour for me, but I'm always glad to help.

There is a nice stack by Richard, explaining the message hierarchy.  
You can find it here: http://support.runrev.com/scriptingconferences/


The message hierarchy is extensively documented in the HyperCard  
literature. I don't know of any good reference directly connected  
with Revolution, except fo page 103 of the user manual PDF included  
with Revolution 2.7.1 and later.


Best regards,

Mark Schonewille

--

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Quickly extract data from your HyperCard stacks with DIFfersifier.  
http://differsifier.economy-x-talk.com



Op 6-nov-2007, om 17:13 heeft Len Morgan het volgende geschreven:


Hello Mark!

If my first wife had not asked me to get the big snip as an  
anniversary present many years ago, I'd name my next male child  
after you for that little tidbit.  I may still consider re-naming  
my first born male child after you, although at 22, he may have  
some thoughts on the matter.


You have saved me DAYS of frustration in tracking down why my  
preOpenStack is getting executed AGAIN when I quit the app!  Is  
that little item documented anywhere?  Now that I see it in writing  
and knowing (a little) about how the message path works, it makes  
perfect sense.  I guess I always figured that when I opened another  
stack, the message was sent to it.  It never occurred that if there  
was no preOpenStack message, that it would get passed back to the  
caller!  Perhaps that is obvious to everyone but me.


Thanks again!!!

len morgan


___
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: Idle handlers and Text files

2007-11-06 Thread Stephen Barncard
although somewhat off-topic, this might be a good time to add that 
Dar Scott's 'Message Mechanics Primer'  example stack will help one 
wrap one's head around the oft-confusing world of messages:


http://www.swcp.com/dsc/revstacks.html

A Primer on Message Mechanics. This module (stack file) is a primer 
on using send, cancel, pendingMessages and callbacks. Those are the 
basic Revolution components needed to get your stacks to do several 
things at the same time. The primer starts from the basics and builds 
on those, providing examples and details along the way. It is 88 tiny 
pages long and if that is not long enough for you, note that it is 
set up so you can add your own pages. It is fun and... It is Free!



sqb





Hello Mark!

If my first wife had not asked me to get the big snip as an 
anniversary present many years ago, I'd name my next male child 
after you for that little tidbit.  I may still consider re-naming my 
first born male child after you, although at 22, he may have some 
thoughts on the matter.


You have saved me DAYS of frustration in tracking down why my 
preOpenStack is getting executed AGAIN when I quit the app!  Is that 
little item documented anywhere?  Now that I see it in writing and 
knowing (a little) about how the message path works, it makes 
perfect sense.  I guess I always figured that when I opened another 
stack, the message was sent to it.  It never occurred that if there 
was no preOpenStack message, that it would get passed back to the 
caller!  Perhaps that is obvious to everyone but me.


Thanks again!!!

len morgan



--


stephen barncard
s a n  f r a n c i s c o
- - -  - - - - - - - - -


___
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: Idle handlers and Text files

2007-11-06 Thread Mark Smith
Also worth remembering is that the openStack/preOpenStack message is  
sent by the engine to the first card in the mainstack, which is  
another reason one might want to handle it there.


Best,

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: Idle handlers and Text files

2007-11-06 Thread Jonathan Scott

on openstack
  send mouseUp to btn foo
  pass openstack
close openstack

	Is this wrong?  It's such a simple procedure.  How could it be  
wrong?  If it is, please fill me in on it.




On Nov 7, 2007, at 3:00 AM, [EMAIL PROTECTED]  
wrote:



If I understand you correctly, you can't send a mouseUp message
automatically after opening the stack. That also means you made a
mistake somewhere, which needs to be corrected. I don't think that
using the idle handler, or send, is a good alternative in this case.
My advice would be to find out why you can't send that mouseUp  
command.


The Finder simply updates open windows once in a while, including the
desktop. It doesn't matter at which level in the hierarchy they are.
However, if you add or remove a folder, the window gets updated
instantly.  Not sure that it helps you, but if I do a test writing
files to a folder or the desktop, I see the file appear instantly on
my local disks, but not that quickly on network disks.

Best regards,

Mark Schonewille


___
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: Idle handlers and Text files

2007-11-06 Thread Mark Schonewille

Hi Jonathan,

Your brief handler should be correct, but from here I can't see  
whether you lock any mesages that prevent the openStack handler from  
being sent or whether you have any openStack handler at a lower lever  
in the message hierarchy. There must be something in your stack that  
causes the problem. The fact that your script works in an otherwise  
empty stack but not in the mainstack of your project supports my  
suspicion that something is wrong with your mainstack.


Best regards,

Mark Schonewille

--

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Quickly extract data from your HyperCard stacks with DIFfersifier.  
http://differsifier.economy-x-talk.com



Op 7-nov-2007, om 0:50 heeft Jonathan Scott het volgende geschreven:


on openstack
  send mouseUp to btn foo
  pass openstack
close openstack

	Is this wrong?  It's such a simple procedure.  How could it be  
wrong?  If it is, please fill me in on it.





___
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: Idle handlers and Text files

2007-11-06 Thread Malte Brill

 Is this wrong?  It's such a simple procedure.  How could it be
 wrong?  If it is, please fill me in on it.


I´m suspecting the last line of your script is a typo. Should read

end openStack

However, is button foo on the first card?

All the best,

Malte___
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