RG>> self.postAction( editEnterMemoView ) Works great!
RG> Yep! It does. As you might have surmised, my
RG> failure to get it to work arose from using the
RG> editEnterMemoView constant against an Action()
RG> request as opposed to the postAction() request.
RG> Okay ... I've read my books and I'm still a little
RG> cornfused. Could you please explain why this works
RG> with postAction() and not with action().
It does work with action(), but in your arrive method, use doDefault
first, like:
doDefault
action( editEnterMemoView )
Don't ask me why this works, but if I had to guess, it would be this.
From my understanding, any code you add to a UIObject is executed BEFORE
the object's default code. In this case, it would seem that if you
don't add the doDefault first, the memo field hasn't executed the code
it executes when it is arrived at. So perhaps the memo field won't be
ready to accept an editEnterMemoView command until it executes it's
arrive code. Putting in the doDefault first is telling the memo field,
"I want to go right into Memo View when you get control from the form,
but I'll wait until you're done everything you need to do to acquire
control. Then, when, and only when you're finished, I'm telling you to
go into Memo View."
I hope I'm not too off base here. I don't want to give you false
information. But I know putting the doDefault first lets you use the
action() command. I'm also pretty sure that all doDefault does is to
execute the object's built-in code before it executes any user entered
code. So the rest, I hope, is just a logical explanation for what is
occurring.
RG> What do we use this postAction() for? Where does it
RG> come into play? Help! My mind is failing.
I think postAction() is similar to using doDefault before an action(),
but again, I'm not positive. I'm waiting for Lance's answer just like
you.
Robert
--- WILDMAIL!/WC v4.12
---------------
* Origin: The Solution II BBS*Quakertown,Pa*(215)529-9501 (1:2614/205.0)
|