Re: [StrongED] Italic Font required at 4.70 Choices selection

[Ron <gettingchoppy@xxxxxxxxx>]

In message <73f7a2d155.fjgraute@xxxxxxxxx>
          Fred Graute <fjgraute@xxxxxxxxx> wrote:

> In message <13732bd055.Iyonix@-.->
>           Ron <gettingchoppy@xxxxxxxxx> wrote:
> 
> > In message <ceb36ecf55.fjgraute@xxxxxxxxx>
> >           Fred Graute <fjgraute@xxxxxxxxx> wrote:
> > 
> > > In message <b948eac755.Iyonix@-.->
> > >           Ron <gettingchoppy@xxxxxxxxx> wrote:
> > > 
> > > > Sorry if this has already been discussed.
> > > > Selecting a bitmap font is not successful unless the Italic font sprite
> > > > is present. Copying the Regular to Italic and things appear to work OK.
> > > 
> > > The cause is that one of the syntax colouring groups has its style set
> > > to 'Italic' and the selected bitmap font not having that style.
> > > 
> > > The 'official' solution is to find the group that has 'Italic' defined
> > > and change it 'Regular', but copying the 'Regular' style to 'Italic'
> > > also works. :-)
> > > 
> > > I'm considering though to keep the bitmap font but substitute 'Regular'
> > > for 'Italic', instead of reverting to the system font as is done now.
> > >
> > Looking again at this today I had some unusual things happen and the
> > proper fix (editting UsePrefs.Modes.TaskWindow.ColoursSTD) is the
> > cleanest.
> > Perhaps a 'real' bug is that using the  Mode Choices > Colours window
> > does not allow the changing from italic to regular.
> > It seems to be only able to reflect the manual change I mentioned.
> 
> Changing the font style using Mode Choices > Colours should work. If it
> doesn't then it's indeed a bug. Just tried it on 4.70a11 and it worked
> for me.
>

I must have got things out of step while deleting the italic font and
then trying to select the regular.
Putting an Italic font back and it /does/ allow to and froing the types
using Mode Choices > Colours.
I guess what would be best i if we could find an actual italic font.
(Dont know if this is viable at 10x20, but the chances must be better
than 8x16)
I just noticed that the " character has a couple of pixels that
shouldn't be there, haven't checked further yet.

> 
> > I'm still thinking that the way forward would be to have a version of
> > Olly Betts LineEditor module that could take input from BASIC or C
> > to do, for example a ^K.
> > I haven't experimented with writing to the keyboard buffer, Can
> > you/anyone see any problems with that approach?
> 
> A quick test shows that it works but you're limited to c-X style
> keycodes, combinations with Shift can't be used.
> 

I have got as far as this
*echo ABCD|H|H|H|Hx|I|I|I|I { < kbd: }
The [09]'s step forward again otherwise a space is left at the cursor
position.
The control codes for Olly Betts LineEditor dont respond though.
It may be echo that doesn't recognise |U or |K
It is the same with rawkbd:

I probably have to get inbetween the physical keyboard and the
lineeditor module somewhere. More PRM reading to do I guess.

Ron M.



--=20
To unsubscribe send a mail to StrongED+unsubscribe@xxxxxxxxxxxxxx
List archives at http://www.Torrens.org.uk/RO/StrongED/index.html