XYWRITE DEVEL

[chet.gottfried@xxxxxxxx]

 ->     --Annie:

XY-> M0-M9 functions are on Alt keys in my .kbds (save/gets are the Ctrl+Shift
 -> set) but I never use them. I can't explain why; they just aren't right for
 -> the way I work. Almost from the start, I've done attributes another way.
 -> Typically, my  (=roman) cancels other styles this way:
 ->     19=SI,{,m,d,n,m,},CI
 -> Since no XP/TP pair is present this should cause a split-second "Invalid
 -> formatting command" error; if it happens it's too fast to see even on an XT
 -> This works for me, and I suspect that it's what xyDos 4 rebelled against. T
 -> .kbd fix is easy and obvious. But my copious xpl files change attributes wi
 -> save/gets, always lc, throughout. What does this new restriction gain? I
 -> threw up my hands. Out with the xy4!

You should learn to play a little more. The function TP is a lot
of fun: The apparent switch is that although it toggles between
two modes in 4, one can't necessarily predict the toggle
(without taking a VA, of course). But it can flip between
page-line and draft OR draft and expanded, depending upon where
one is. Something to be said for XP!

By the way, I notice that upon storing and calling a file, all
lowercase mode calls revert to uppercase afterward.

It was also good to code a 1-meg text file via programming in 4
rather than having to break it up into pieces for 3+. As someone
else has commented, the programming environment seems more stable
(although I've been able to lock 4 too), but in one test case of
a faulty program, whereas 3+ simply locked, 4 actually gave an
error message.

Of course, none of this is an excuse for doing without
documentation, but you might want to give the program more of a
chance. I miss the text features of help frame 5, for example,
but K does look more interesting.

--Chet

---
 ? SLMR 2.1a ? Art + write + dtp = chet.gottfried@xxxxxxxx