[Prev][Next][Index][Thread]
Anyone with ADB keyboard based NeXT(s) out there?
I just tried it on a TurboColor under 3.2. The only things that did NOT work were <shift
Tab> (Backtab) and nothing worked on the keypad (0 to 9, =,/,*'-'+'.'<Enter>.
I hope this helps,
Peter
Begin forwarded message:
Errors-To: executor-request@ictv.com
Sender: executor-request@ictv.com
Precedence: bulk
Date: Thu, 21 Oct 93 23:48:35 -0600
From: Clifford T. Matthews <iclone!ctm@cs.unm.edu>
To: executor@ictv.com
Subject: Anyone with ADB keyboard based NeXT(s) out there?
Content-Type: text
Content-Length: 1272
Dear Folks,
1.3 is on temporary hold again. It turns out that somewhere along the way, we broke
support for ADB keyboards again. It's not clear to me whether we did something, or
whether NS 3.1 behaves slightly differently than NS 3.0 did. If you have an ADB keyboard
based NeXT and can pick up Executor "1.3" as it currently exists on ftp.cs.unm.edu, can
you do so and test it with Microsoft word and let me know what you find?
Even if you can't do the above, if you have an ADB keyboard based NeXT, can you drop
me a line? I'm tempted to send what we have to the duplicators and just add to the
README saying that ADB keyboards don't currently work, but we'll release a 1.3.1 soon
that does support them, but I won't do that if there are a bunch of ADB keyboard users out
there.
In case you missed the great ADB keyboard flamewar, let me just mention that although
there is a portable way to get the key-character under NEXTSTEP, there is *not* a portable
way to get the key-CODE under NEXTSTEP, which is why emulation software is very
sensitive to whatever NeXT does. In this case I suspect that the problem is indeed ours,
but without an ADB-based NeXT, it's very hard for us to test this.
Thanks for your patience
--Cliff