[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IIe Keyboard On A II Plus
"Michael J. Mahon" <mjmahon@aol.com> wrote in message 0aydnRAvsZqQovzVnZ2dnUVZ_hOdnZ2d@comcast.com">news:0aydnRAvsZqQovzVnZ2dnUVZ_hOdnZ2d@comcast.com...
> Bill Garber wrote:
> > "Michael J. Mahon" <mjmahon@aol.com> wrote in message LcednTS2moWPJP3VnZ2dnUVZ_vadnZ2d@comcast.com">news:LcednTS2moWPJP3VnZ2dnUVZ_vadnZ2d@comcast.com...
> >
> >>a2aviator@gmail.com wrote:
> >>
> >>>You need to have the capslock key that the Franklin has, otherwise
> >>>you're emulating softswitch lowercase.
> >>>
> >>>If the lower case works as is on the //e keyboard with a ][+ and the
> >>>lowercase character ROM installed, then it shouldn't be much different
> >>>to have it send the right stuff to a Franklin.
> >>
> >>But GETLN in the ][ and ][+ monitor converts lower case to upper case,
> >>so BASIC won't see anything but upper case.
> >>
> >>To see any lower case, you'll need an application that accepts it from
> >>the keyboard (most will expect the shift key mod).
> >
> >
> >
> > I don't know about that, Mike. If the ROM has the upper 32 codes
> > defined, then why wouldn't it do it? When I type * PRINT CHR$(65+32)
> > on the Franklin, it displays "a", and also on my II+ with the Dan Paymar
> > ROM installed. It would be trivial to program those codes into the encoder.
>
> If you have a lower case character generator ROM, then your machine
> can display lower case, but you can't type it into a BASIC program
> from the keyboard, even if the keyboard does deliver lower case,
> because the monitor routine that BASIC (and a lot of other software)
> uses folds lower case to upper case.
Even if it's between quotes in a PRINT command, say?
And, if so, then we would need to modify the monitor ROM.
Might turn out to be a lot of work, if there isn't a lot of space
in it to provide more firmware.
Bill Garber from GS-Electronics
http://www.garberstreet.com