Crybaby Grows up

[DunbarX at aol.com]

Hi.

Exactly. In my utility stack handlers (as in HC), I do not have to even 
consider the test stack, so, if I say:

on opencard
   put the name of btn 1 into fld "utilityField" of stack "wizard"
end opencard

I get the name of the button in the test stack, as expected. I do have to 
specify the stack in which to put the data, though. As expected.

I assumed "this stack" worked the same. Since my HC utility is a floating 
palette, I had to deal with this sort of thing explicitly. in Rev, I can 
understand that a suite of stacks may require more care.

I filtered the "rev" stacks out a while back. Smart to name them so. Thanks, 
though.

This is what I meant by driving. Hands clutching the wheel still a bit too 
tightly, but still.

Craig


In a message dated 2/27/09 4:35:57 PM, jacque at hyperactivesw.com writes:


> The "this stack" issue trips up everyone. In a multi-window environment,
> "this" stack isn't always what you think it is. If your script is in a
> topstack, it's often "this stack", only you can set the defaultstack
> property and then it isn't.


**************
A Good Credit Score is 700 or Above. 
See yours in just 2 easy steps! 
(http://pr.atwola.com/promoclk/100126575x1218822736x1201267884/aol?redir=http:%2F%2Fwww.freecreditreport.com%2Fpm%2Fdefault.
aspx%3Fsc%3D668072%26hmpgID%3D62%26bcd%3DfebemailfooterNO62)