Re: styles, win98 workaround question

["Fred Weiner" fw1948@xxxxxxxx]

Carl.
 
Thank you! Can't wait to try these out.
 
Fred Weiner.

 
On 5/19/06, Carl Distefano mailto:cld@xxxxxxxx wrote:

Reply to note from "Fred Weiner" mailto:fw1948@xxxxxxxx Fri, 19 May 2006

13:21:18 -0700

> Is there a way to keep a collection of styles for use with any
> document, available on the fly? I've thought of collecting them
> into a file and loading it, then copy-and-paste from it as

> needed, but this seems so inelegant.

There are two possibilities, both of which conserve customization
memory, which is scarce.  One is to add the styles to FISHOUT.DAT,
whence you can fish them out on the fly (fly-fishing?) with

FISH stylename.  If you haven't used frame FISH(OUT) before,
setup is easy; read the helpscreen at HELP FISH.

Another is to load the styles into U2 via one or more personal frames.

Here's a template; issue DECODE to decode it:

XPLeNCODE v2.0
b-gin [UNTITLED]
{{;5mystyle}} Insert MYSTYLE "delta" into text[cr|lf]{002}{<}
IF{<}VA$WS{>}==1{>}[GT_]{<}SV01,{<}SSMYSTYLE,NP,OR=0,SZ=12PT,

12PT,UF=STANDARD,SY=23Z,10,0,0,MD=NM,FD=66LI,PW=85DI,OF=2DI,2
DI,LM=5DI,RM=75DI,TP=7LI,7LI,BT=2LI,3LI,2LI,7LI,RT=0,TS=0DI,I
P=0DI,0DI,0DI,FL,NJ,HY=1,WD=2,OP=2,ET=0LI,0LI,EE=0LI,0LI,AL=0
,LS=1LI,LL=0LI,0LI,EL=0,SN=0DI{>}{>}{<}GT01{>}{<}EX{>}{<}EI{>

}{<}PRNo file{>}{002}[cr|lf][cr|lf]
-nd
XPLeNCODE

The upside to this approach is that you can fetch the style with a
single keystroke, by assigning the chosen framename (MYSTYLE, in the
example) to a key in the KeyBoarD file, thus:


nn=NOJM(,2,.,m,y,s,t,y,l,e,)

or, the equivalent:

nn=NOJM2,.,m,y,s,t,y,l,e,Q2

or by issuing MYSTYLE on the CMline.  The downside is that,
to edit the saved style, you have to edit _and reLOAD_ U2 every time,

being careful not simply to SAve it (issue HELP LOADHELP for
more about this); it's a bit of a bother.  By contrast, FISHOUT.DAT,
being an ordinary XyWrite file, is freely editable and _SAvable_.


Of course, you can always save the style to a permanent Save/Get, but
that consumes memory -- needlessly, as the above alternatives show.

--
Carl Distefano
mailto:cld@xxxxxxxx