On Sun, Nov 22, 2015 at 3:04 PM, Richard Gaskin
wrote:
> Dr. Hawkins wrote:
>
>> On Sat, Nov 21, 2015 at 7:24 PM, J. Landman Gay wrote:
>>
>>
> The deficiency isn't in the messaging system, but the monolithic file
>> structure. The only reason I got into this is the staggering amount of
>> spac
Dr. Hawkins wrote:
On Sat, Nov 21, 2015 at 7:24 PM, J. Landman Gay wrote:
No deficiency.
The deficiency isn't in the messaging system, but the monolithic file
structure. The only reason I got into this is the staggering amount of
space being taken for each checkpoint.
Moving into the 1990s
On Sat, Nov 21, 2015 at 7:24 PM, J. Landman Gay
wrote:
> No deficiency.
The deficiency isn't in the messaging system, but the monolithic file
structure. The only reason I got into this is the staggering amount of
space being taken for each checkpoint.
Moving into the 1990s with some kind of r
On 11/21/2015 8:55 PM, Dr. Hawkins wrote:
All in all, though, about 12 hours to work around the staggering deficiency
of the IDE.
No deficiency. You put a script into the main message path and the IDE
happened to get some messages before your library did. All messages pass
through all the lib
On Sat, Nov 21, 2015 at 6:27 PM, Scott Rossi wrote:
> FrontScripts and backScripts are part of the normal message path and
> aren't exclusive to any stacks. You might be able get away with private
> handlers and functions triggered in a frontScript but you have to be extra
> careful to always pa
FrontScripts and backScripts are part of the normal message path and aren't
exclusive to any stacks. You might be able get away with private handlers and
functions triggered in a frontScript but you have to be extra careful to always
pass all standard messages or you'll prevent stuff from worki
On Sat, Nov 21, 2015 at 5:46 PM, Scott Rossi wrote:
> Handlers in libraries are available to all open stacks. If you're relying
> on standard messages in your library (ie openStack, closeStack, etc) these
> will get triggered by any stack that opens or closes. You either need to
> use custom ha
Handlers in libraries are available to all open stacks. If you're relying on
standard messages in your library (ie openStack, closeStack, etc) these will
get triggered by any stack that opens or closes. You either need to use custom
handler names that are only triggered by stacks that "know" t
On Sat, Nov 21, 2015 at 4:29 PM, Dr. Hawkins wrote:
>
> I hacked around it with
>
Ugh. It's worse than I thought.
I've added the hack to closeField and exitField.
Now it seems suspendStack, resumeStack and the like are all up for this,
too. And then there would be resizeStack, and pretty muc
I don't think that this is supposed to happen . . .
I've taken the time to break my substacks into their own files, and load
them all. Now a version increment only creates a new 875k file rather than
9mb.
It's taken some thinking, and what used to be the mainstack needs to be a
library (otherwis
10 matches
Mail list logo
