[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
Re: NB: What I've learned so far
- Subject: Re: NB: What I've learned so far
- From: Leslie Bialler lb136@xxxxxxxx
- Date: Mon, 06 Dec 1999 13:52:36 -0500
Boyz and Grrrls,
Several people have e-mailed me privately with questions about NB Win. Here
is what I have learned so far. This is my "transition" from XyWrite 4.0 for
DOS to NB Win.
Your macros should work, whether you have them "hardwired" to a key in your
KBD
file or whether you store them as save gets. The trick is this: They put in a
_blank_ startup file called NBSTART.INT. What I did was to copy _my_
startup.int file, _my_ kbd file, and my altkeys.sav file over to NB to see
what would happen. (I also copied over my settings.dfl file, but that was
less
of a success. I decided it was better to compare the default settings line
for
line and see what NB would accept.)
For this purpose I set my preferences so that the error messages appeared in
a
dialogue box (you have the choice, as in XyWin of having them appear there or
on the prompt line). At each beep (and there were remarkably few) I removed
the
offender or changed the parameters.
Next I tested the save/gets. Unlike with XyWin, what is on _your_ altkeys.sav
file _does_ override Windows conventions, with two exceptions: alt-f and
alt-w.
However the macros finally do execute once you blow away a dropdown menu that
insists on appearing.
Next I tested the macros. For this purpose, I reset the preferences so that
the
error messages appear on the prompt line, since many of my routines, of
course,
have < http://www.columbia.edu/cu/cup