Re: xkbd version 0.7

on Wed, Mar 13, 2002 at 06:42:53PM -0500, digger vermont wrote:
> Hello mallum,
> 	Just when I was starting to understand how things worked it all
> changed!
> 	I just upgraded xkbd and the text placement is nicely centered.  I went
> and looked at cvs and there's a lot rewritten.  It looks good.  I had
> been playing around with the text placement and didn't have much luck. I
> was trying to use extents.x and y from XftTextExtents8.  I've been
> learning alot looking at xkbd and now I'll have to go back and start
> over. :)
> 

Yes, some things have been jigged around. The core of xkbd now exists
a fairly basic shared lib, so other apps can include it. 

I also improved ( hopefully ) the keyboard layout to improve the
problem if Xft telling me single chars of a monospaced font are
different widths.

> I notice a new definition key_span_width.  With out looking closer or
> playing around I don't know what it does.  Also taking it out for a
> quick spin I noticed that the nice double line I had made by defining a
> blank key is gone.
> 

Xkbd now checks the widths of all single char keys, finds the widest
and sets all the single key widths to be that width. It also does a
similar thing with the keys height.

The key_span_width simply sets a keys width to a multiple of this max
char width. It works well with layouts like the fitaly one where the
keyboards layout is very aligned. 

The keyboard layout code still needs some work, but its definetly
getting there...

I also added a few other config options for things like slide
sensitivity and key repeat rate. Im yet to document this. 

What I really need to do is fix all the #ifdef's USE_XFT so xkbd will compile
_without_ Xft. I really appreciate any help with that *hint* ;)

Also I've had a report that the latest xkbd ( 0.7.1 ) causes some
problems on install , with the Python menu script - has any body else
noticed this ?

  -- mallum