Re: Stack name conflicts resolved?

2016-11-05 Thread Monte Goulding
> On 6 Nov. 2016, at 1:31 pm, Mark Wieder wrote: > > When new stacks are created in memory they are assigned the id 1002. > Why? > If there's a stack already in memory why not create the new stack with the > next sequential id? > Then the combination of id and filename

Re: Updating Text-Script Only Stacks in Run-Time, Message Path Memory

2016-11-05 Thread Monte Goulding
> On 6 Nov. 2016, at 1:33 pm, Mark Wieder wrote: > >> So, yes… something is causing the IDE not to pick up the changes in the open >> scripts and (re)placing it in the message path. > > Yep. It's one of the two reasons I don't use script-only stacks. From the sounds of

Mobile tao: mouseStillDown, mouseUp, answer dialog

2016-11-05 Thread Mike Kerner
This is the second time I've been bitten by this, so this is more a note to me for the next time it happens, because I had forgotten what I learned, the first time, and I didn't look in the right place for my notes on the subject, but I did look here. For some context, I was trying to (poorly)

Re: Goofy question about Datagrids

2016-11-05 Thread Sri
Bob Sneidar-2 wrote > Well I discovered that what you CANNOT do is call a user-defined command > or function that has not been loaded yet, as in a front or back script > that has not been inserted yet. If I do, when I open the stack I get an > error. I suppose I could do the inserts in a preopen

Re: Updating Text-Script Only Stacks in Run-Time, Message Path Memory

2016-11-05 Thread J. Landman Gay
On 11/5/16 10:04 AM, Sannyasin Brahmanathaswami wrote: But the engine does not yet "see" my new handler. Just for fun: open stack file on disk.. in BBEdit: yes, confirmed, my changes are there. ERGO conclude: editing a script only stack and saving it does *not* update the "live" version of

Stack name conflicts resolved?

2016-11-05 Thread Richard Gaskin
I've grown weary of stack name conflict over the years, and this morning decided to take some time to assess where we're really at with that and see if perhaps there's a way to handle things more liberally than how the IDE does now. TL/DR version: It seems there's actually no real problem at

Re: Background colour of a new stack

2016-11-05 Thread Richard Gaskin
Graham Samuel wrote: > This may be old news to some, but in the LC7x series and earlier, if > you created a stack, the card displayed as white. In LC 8.1.1, it > displays as grey (reported as 220,220,220). To make cards look the > way they did in earlier versions, I have to created a background

Re: Background colour of a new stack

2016-11-05 Thread Randy Hengst
Graham, I also thought the change of color to be a bit odd. If I understood you correctly, you are adding a graphic to “cover up” the gray background. You don’t need to add a graphic to create the white background. Go to the Stack Inspector and change the backgroundColor to white. Then each

Re: Stack name conflicts resolved?

2016-11-05 Thread Monte Goulding
I didn't say it couldn't be done. Possibly we would need versions of the mainstacks and openstacks that listed long IDs. Sent from my iPhone > On 6 Nov. 2016, at 9:08 am, Richard Gaskin wrote: > > I imagine for good reason, but I'm curious: where does topstack not

Re: Stack name conflicts resolved?

2016-11-05 Thread Richard Gaskin
stephen barncard wrote: > On Sat, Nov 5, 2016 at 11:28 AM, Richard Gaskin wrote: > >> I've grown weary of stack name conflict over the years, and this >> morning decided to take some time to assess where we're really at >> with that and see if perhaps there's a way to handle things more >>

Re: Stack name conflicts resolved?

2016-11-05 Thread Monte Goulding
> On 6 Nov. 2016, at 5:28 am, Richard Gaskin wrote: > > That is, once we modify the IDE to allow it. ^ this is the issue. For the most part it isn’t the engine that has the issue with multiple stacks with the same name open it’s the IDE. There would be bucket

Re: Stack name conflicts resolved?

2016-11-05 Thread Richard Gaskin
Monte Goulding wrote: >> On 6 Nov. 2016, at 5:28 am, Richard Gaskin wrote: >> >> That is, once we modify the IDE to allow it. > > ^ this is the issue. For the most part it isn’t the engine that has > the issue with multiple stacks with the same name open it’s the IDE. > There would be bucket

Re: Stack name conflicts resolved?

2016-11-05 Thread stephen barncard
On Sat, Nov 5, 2016 at 11:28 AM, Richard Gaskin wrote: > I've grown weary of stack name conflict over the years, and this morning > decided to take some time to assess where we're really at with that and see > if perhaps there's a way to handle things more liberally

Background colour of a new stack

2016-11-05 Thread Graham Samuel
This may be old news to some, but in the LC7x series and earlier, if you created a stack, the card displayed as white. In LC 8.1.1, it displays as grey (reported as 220,220,220). To make cards look the way they did in earlier versions, I have to created a background rectangle graphic

Re: Updating Text-Script Only Stacks in Run-Time, Message Path Memory

2016-11-05 Thread Sannyasin Brahmanathaswami
right… not the engine… some IDE gremlin… restarted LC… open some script only stack that had been put into use earlier, edit save and the changes are available runtime. So, yes… something is causing the IDE not to pick up the changes in the open scripts and (re)placing it in the message

Re: Stack name conflicts resolved?

2016-11-05 Thread Mark Wieder
On 11/05/2016 03:02 PM, Monte Goulding wrote: On 6 Nov. 2016, at 5:28 am, Richard Gaskin wrote: That is, once we modify the IDE to allow it. ^ this is the issue. For the most part it isn’t the engine that has the issue with multiple stacks with the same name

Re: Updating Text-Script Only Stacks in Run-Time, Message Path Memory

2016-11-05 Thread Mark Wieder
On 11/05/2016 02:39 PM, Sannyasin Brahmanathaswami wrote: So, yes… something is causing the IDE not to pick up the changes in the open scripts and (re)placing it in the message path. Yep. It's one of the two reasons I don't use script-only stacks. -- Mark Wieder ahsoftw...@gmail.com

Re: Background colour of a new stack

2016-11-05 Thread Graham Samuel
Thanks Randy, I hadn’t realised I could do that. Excellent! Graham > On 5 Nov 2016, at 22:40, Randy Hengst wrote: > > Graham, > > I also thought the change of color to be a bit odd. > > If I understood you correctly, you are adding a graphic to “cover up” the > gray

Updating Text-Script Only Stacks in Run-Time, Message Path Memory

2016-11-05 Thread Sannyasin Brahmanathaswami
I ran into this today: Run a boot stack that has a list of stack files, Initialization script loads N number of stacks as libs with "start using stack x" on a loop So far so good. I can run cmds from the message box to fire handlers in any of the stacks that were loaded with "start using" Run