[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: PCB lesstif pcb-menu.res ideas



DJ Delorie wrote: 
Choose via tool the usual way.  Now PCB is ready to act on a left
button down event.  In comes a scroll wheel event.  Now PCB suspends
polling the mouse for an instant, and reponding to the new event,
changes the value of ViaDrillingHole up a mil for the up button, or
down a mil for the down button.


I think what you're asking for is tool-sensitive bindings.  Thus, if
the via tool is the current tool, you want up and down to do
via-specific things,


Yes, that's one way to think of it.

Another way is just an add on to what you already did with the multi-keys bindings. If F1, whoops! You already defined multikeys bindings to work on plain ascii only, so F1 key is not one of those keys. So that's not an easy falling-out-of-what-just-happened thing to do -- I was thinking follow F1 with more keys, some of which were mouse buttons...

Is there an easy way to let the function keys also be some of the user bindable keys? We have some pretty good reasons to use some of the letter keys as a one letter mnemonic. They can be same as gschem and/or different one letter mnemonics -- r for route, g for grid, z for zoom, v for view full.

One letter commands increase usability. I'd like to have them in gschem too, and yet, while gschem stays as it is, I want to be able to change some key defs in PCB to match gschem so I keep my head straight as I switch from one to the other in a schematic driven design.

John G


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user