On Oct 17, 2011, at 4:11 AM, Scott Rossi wrote:
Maybe this isn't the best method to accomplish what I need, but can anyone
see why this is failing?
Scott, when you execute the do, it's getting the text of the button and
passing that along instead of the long id that's coming into
On Oct 17, 2011, at 12:30 PM, Scott Rossi wrote:
...this command can be triggered by any external object via the above router
command (in the same script) with something like this:
runPrivateCommand getObjectID,long id of long id of btw 1
I think you can even use:
runPrivateCommand
Hi Scott,
I'm sure you have good reasons but I'm curious about why you would want to
classify a handler as private if you know you will need to access it from
outside the script that it's in?
Pete
Molly's Revenge http://www.mollysrevenge.com
On Mon, Oct 17, 2011 at 10:30 AM, Scott Rossi
Pete-
Monday, October 17, 2011, 2:01:13 PM, you wrote:
Hi Scott,
I'm sure you have good reasons but I'm curious about why you would want to
classify a handler as private if you know you will need to access it from
outside the script that it's in?
Thanks. You beat me to it. This has been
Recently, Mark Wieder wrote:
I'm sure you have good reasons but I'm curious about why you would want to
classify a handler as private if you know you will need to access it from
outside the script that it's in?
Thanks. You beat me to it. This has been bothering me all day. Knowing
Scott,
