On 10/6/12 10:30 AM, Dr. Hawkins wrote:
On Friday, October 5, 2012, Dr. Hawkins wrote:
This is my output stack. It contains a script, and I regularly delete
all the cards.
Could I be accumulating some kind of cruft?
It occurred to me this morning: on every output run, I pace my naviga
On Friday, October 5, 2012, Dr. Hawkins wrote:
>
>
> This is my output stack. It contains a script, and I regularly delete
> all the cards.
>
> Could I be accumulating some kind of cruft?
>
It occurred to me this morning: on every output run, I pace my navigation
panel group onto the first car
On Fri, Oct 5, 2012 at 5:15 PM, Dr. Hawkins wrote:
> AFAIK, there isn't any code that it *should* be hitting.
ANd this happens even with an empty stack!
Or is it empty.
This is my output stack. It contains a script, and I regularly delete
all the cards.
Could I be accumulating some kind of cr
On Fri, Oct 5, 2012 at 2:08 PM, Bob Sneidar wrote:
> Not sure what the effect of locking messages would be in the middle of a
> closeStack. Stack might not close. I seriously doubt
>however, that your own scripting is taking 4 seconds to run during closeStack!
>If they are, then perhaps it's tim
On 10/5/12 3:55 PM, Dr. Hawkins wrote:
I just need this substack to close without executing any handlers.
Two ways:
1. In each handler in the mainstack, include a check to see if the
target stack is the mainstack and if not, exit the handler.
2. Easier: put empty handlers into the substack
By the way, error 13 is in fact insufficient permissions, as I suspected, but
it was more difficult to determine that that I thought it would be. The usual
lists of OS X errors usually skips the first 25 or so on the positive side. My
opinion here is that system calls that return an error, shoul
Not sure what the effect of locking messages would be in the middle of a
closeStack. Stack might not close. I seriously doubt however, that your own
scripting is taking 4 seconds to run during closeStack! If they are, then
perhaps it's time to review the code to see if there is a more efficient
On Fri, Oct 5, 2012 at 1:51 PM, Bob Sneidar wrote:
> There is the shutDownRequest if you are quitting a compiled app. It gets sent
> to the current card of the main stack!
>Make sure you are trapping for it in the mainStack and not another. Be sure to
>pass it in order to complete the shutdown!
Reading more closely, I am not sure you want to do this anyway. You will not
prevent the usual house keeping things from happening in the app or IDE anyway,
if you use lock messages. Certain things have to fire off for the IDE to even
work properly when messages are locked, or so it is my unders
There is the shutDownRequest if you are quitting a compiled app. It gets sent
to the current card of the main stack! Make sure you are trapping for it in the
mainStack and not another. Be sure to pass it in order to complete the
shutdown! My understanding is that if you don't the SIGTERM sent to
10 matches
Mail list logo
