Is there any reason script-only stacks had to be implemented in the engine?
Is there any reason *not* to implement their equivalent in about five lines
of code in the mainstack of a project? i.e.,
on loadTextStack tFilePath
put url ("file:/" & tFilePath) into tStackData
put line 1 of tStackData into tStackName
create invisible stack tStackName
set the script of stack tStackName to line 2 to -1 of tStackData
send "openStack" to stack tStackName
end loadTextStack
This would immediately fix the issue of chained behaviors, and allow for
the incremental implementation of a far richer format for text-based stack
storage, leading to gains in project-definition source control.
Given that Bug 10275 <http://quality.livecode.com/show_bug.cgi?id=10275> is
over five years and several versions old, am I barking up a tree with this,
or making sense?
with no clue,
Geoff
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
