Re: Whoops: Getting the name of the script only stack an handler is in

2019-01-03 Thread Martin Koob via use-livecode
To view the messages in threaded form I use: http://lists.runrev.com/pipermail/use-livecode/ I can't reply thru that so when I do want to reply I use: http://runtime-revolution.278305.n4.nabble.com/ I can't imagine trying to manage all the email from the lists in my mail. I have enough to sort

Re: Whoops: Getting the name of the script only stack an handler is in

2019-01-03 Thread Bob Sneidar via use-livecode
Apple Mail does indeed support threading, but somehow certain emails or rather replies to emails "unthread" and start a new thread. Part of the problem is that some simply subscribe to the list as individual emails, while others employ the digest, and still others use the forum (I think). The

Re: Whoops: Getting the name of the script only stack an handler is in

2019-01-03 Thread Martin Koob via use-livecode
Hi Another way to approach it is to use the 'get the executionContext'. You can get the filename of the script only stack from this I tried this in a button with a behaviour script on a new stack with three fields to see the different results. on mouseUp pButtonNumber set the itemdelimiter

Re: Whoops: Getting the name of the script only stack an handler is in

2019-01-02 Thread William Prothero via use-livecode
Bob: I tried it. Yes: put the name of me —returns the name of the control that hosts the behavior script put the name of this me —returns the name of the behavior script Best, Bill > On Jan 2, 2019, at 11:34 AM, Bob Sneidar via use-livecode > wrote: > > Ah yes then, me refers to the object

Re: Whoops: Getting the name of the script only stack an handler is in

2019-01-02 Thread Mark Wieder via use-livecode
On 1/2/19 8:01 AM, Bob Sneidar via use-livecode wrote: And I replied before checking all my other emails. Seriously, at some point we need to develop a list system where emails remain threaded. I have over 40 from this list this morning, and reading through every one, then trying to go back

Re: Whoops: Getting the name of the script only stack an handler is in

2019-01-02 Thread Bob Sneidar via use-livecode
Ah yes then, me refers to the object the script belongs to. With behaviors, me refers to the *instance* of the script which is "owned" by the object being interacted with. "this me" refers to the actual behavior script. What you want is "this me". Bob S > On Jan 2, 2019, at 08:35 ,

Re: Whoops: Getting the name of the script only stack an handler is in

2019-01-02 Thread prothero--- via use-livecode
Bob, Thanks for the response. You are probably right, the filename of me should work. I don’t know whether it’s old age or not, but several times I have worked on a problem until I felt I had exhausted my ideas, posted a question to this list, then a solution immediately came to mind. If this

Re: Whoops: Getting the name of the script only stack an handler is in

2019-01-02 Thread Bob Sneidar via use-livecode
Doesn't "the filename of me" work? Bob S > On Dec 31, 2018, at 14:48 , William Prothero via use-livecode > wrote: > > My question: > How do I get the name of the script only stack that holds the “Feature” code? > The above code gives me the name of the main stack, which is not useful for

Re: Whoops: Getting the name of the script only stack an handler is in

2019-01-02 Thread Bob Sneidar via use-livecode
And I replied before checking all my other emails. Seriously, at some point we need to develop a list system where emails remain threaded. I have over 40 from this list this morning, and reading through every one, then trying to go back and respond is a little more brainwork than I am used to

Re: Getting the name of the script only stack an handler is in

2019-01-02 Thread Bob Sneidar via use-livecode
I don't mean to sound flippant, but what is the question? Bob S > On Dec 31, 2018, at 14:38 , William Prothero via use-livecode > wrote: > > Folks: > I’m trying to implement a structure where I can simply add script only stacks > that seamlessly add capability to my app. To do this, I have

Re: Whoops: Getting the name of the script only stack an handler is in

2018-12-31 Thread William Prothero via use-livecode
Folks: Ok, if there is a way to get the name of the stack containing a particular handler, I’ll use it. Otherwise, each “feature” stack will return a precoded name. I had to fiddle to get the polling to work without errors. The impetus for this is to re-factor the code for a project that’s

Whoops: Getting the name of the script only stack an handler is in

2018-12-31 Thread William Prothero via use-livecode
Folks: Sorry, I accidentally sent the email before finishing it. Here’s the complete message. But perhaps I’ve solved it. I only need to put the name of the “feature” stack in the pollActions handler. Anyway, I still have my question. I’m trying to implement a structure where I can simply add

Getting the name of the script only stack an handler is in

2018-12-31 Thread William Prothero via use-livecode
Folks: I’m trying to implement a structure where I can simply add script only stacks that seamlessly add capability to my app. To do this, I have all of the “feature” stacks in a given folder, and when I initialize the app, I start using all of the “feature” stacks. Then I want to initialize