Re: [Xcircuit-dev] Backspace problem

[ken r. <ke...@24...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks! That did it. 

I was using the RPM that was posted on the xcircuit site, which was 2.5.3 with the XCF_Text_Left, and.... my delete key was physically broken on my keyboard-- no scancodes being sent out for several keys that I never use, delete included. Duh.

I was also still using the older parameterized library. Double-duh. The new analoglib2 works great.

Thanks, I am relieved to find out that both were pilot-error problems.

Cheers!

- -ken
- -------
On Mon, Apr 29, 2002 at 12:50:59PM -0400, R. Timothy Edwards wrote:
> Dear Ken,
>    You might want to play around with the default bindings defined in
> "keybindings.c"---lines 527 and 529 are
> 
>    add_binding(XK_Delete, XCF_Text_Delete);
> and
>    add_binding(XK_BackSpace, XCF_Text_Delete); /* Changed from XCF_Text_Left */
> 
> respectively, in version 2.5.4.  The comment at the end of the second
> one was the way it was in version 2.5.3.  It is possible that this,
> combined with some "xmodmap" settings in your home directory or system
> login defaults, are remapping the "delete" key to match "backspace", and
> in so doing, lose the "text delete" function because the XK_Delete
> keysym no longer maps to any keyboard key.  Remapping the backspace
> key caused so many complaints that I repented after only a few minor
> versions with the change.  "XCF_Text_Left" is mapped to the left-arrow
> key, anyway.
> 
> -------------------
> 
> As for the PCB output:  The first library page symbols were designed for
> use in VLSI layouts, not PCB layouts.  So the "c.1" and "c.2" names of
> the pins is not appropriate for PCB use.  Either use the capacitor symbols
> with values on the "analoglib2" library page, or else edit the "capacitor"
> library part and change "c.1" to "1" and "c.2" to "2", making them valid
> pin numbers for PCB use.  Technically, this is PCB's problem, as it should
> accept non-numerical pin names.  It may be the "." that it dislikes,
> though;  I haven't checked to find out.  Pin numbers don't make much
> sense for discrete components, unless they're in a can or SIP or some
> other package for which pin numbering is meaningful.  Either way, the
> advice above will solve your problem without writing ugly "sed" scripts.
> 
> 						Regards,
> 						Tim
> 
> _______________________________________________
> Xcircuit-dev mailing list
> Xci...@li...
> https://lists.sourceforge.net/lists/listinfo/xcircuit-dev

- -- 
- ---------------
Freedom of the press belongs to those who can afford to pay the hosting bill.
Now, that means you! $1/1GB, no monthly fees. http://www.nearlyfreespeech.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8z1+Fe8HF+6xeOIcRAiSuAJsE6GqfegVL/3ScXo2vaWGBvL+IwQCeNtR8
YbpJjmTLYjHSMENeePJ2J0M=
=RPEB
-----END PGP SIGNATURE-----