[Date Prev][Date Next][Subject Prev][Subject Next][ Date Index][ Subject Index]

Re: Stack commands



** Reply to message from Carl Distefano  on Tue, 27 Dec 2005
00:53:00 -0500


> JM 2.RegData/RQ2 BX run Q2 ;*;

You can also issue, at any time, a manual STACK command, to save the
Stack to (reserved) filename MY.STK located in Editor's directory. Frame
FINITO saves whatever file is named in REG variable "Stored_Stack" -- so
ideally, for these two capabilities to be compatible, Stored_Stack should also
point at MY.STK in Editor's dir.

There are a bunch of ways to load old, saved sets of Stack commands -- what is
idiotic is to NOT save it and reload it, because that just robs you of
continuity between sessions. You can do this in STARTUP.INT (the first S/G 50
assignment ignores REG's StoredStack variable, whereas the second one uses it
-- pick just ONE method!):

JM 2.stack.int Q2 ;*; INiTialize Stack (prepare XyWrite to use Stack)
;*; 1st example; MY.STK is the name you gave to your
saved Stack from your last session
JM 2.RegData Q2 >;*; 2nd example
JM 2.stackaux Q2 ;*; Load your Stored Stack

Next, you can ensure that commands you really always need available are part of
the Stack. If you had a particularly long session last time, and were fixed on
one task, it is possible that these important commands dropped out of the Stack
because you didn't happen to use them, and you issued 150 or 200 different
commands (or however many commands you set as your max Stack size). So
reintroduce them into the Stack -- if they are still present in the Stack, they
won't be replaced but they will be kicked up to the beginning of the Stack,
thereby allowing less-used commands to sink toward the bottom (and, eventually,
out of sight unless you use them again). Here, for example, is a command that
I always need -- the ability to CAll and edit U2, and this is how you
"pre-load" it into the Stack -- Save/Get 627 is the Stack "preloader":

$S ;*; that's func $S

There is just one subtle element of all this that you MUST enable, which is a
tiny frame in DLG that redirects funcs $S and $E to U2, where Stack's code is
now located (normally $S and $E are handled by DLG). Probably, Alan, the
reason that things started to work again in v119 is that you refreshed your old
copy of DLG with the new one offered at XyWWWeb. That's IMPORTANT to do! ALL
the old functionality of DLG from the factory is retained, but errors are fixed
and a few new frames are installed, such as this one. It's a simple matter of
replacing the old DLG with the new one, and then relaunching XyWrite.

Here's that tiny frame in DLG, in case anybody wants to install it manually --
put it at the beginning of DLG:

XPLeNCODE v2.0
b-gin [UNTITLED]
{{;5$S,$E}}[cr|lf]{002}{<}SX99,{<}VA$FR{>}{>}[JM_]2.{<}PV99{>
}[Q2_]{002}[cr|lf][cr|lf]
-nd
XPLeNCODE

-----------------------------
Robert Holmgren
holmgren@xxxxxxxx
-----------------------------