Re: gEDA-user: pcb: functions in hidnogui.c

2010-03-16 Thread Peter Clifton
On Tue, 2010-03-16 at 04:50 +0100, kai-martin knaak wrote: > Peter Clifton wrote: > > > Having looked at it, I think it is pretty safe just to remove the CRASH > > statements in the hidnogui HID. (Both invalidate_lr and invalidate_all). > > > > Alternatively, we would have to provide a NOP implem

Re: gEDA-user: pcb: functions in hidnogui.c

2010-03-15 Thread kai-martin knaak
Peter Clifton wrote: > Having looked at it, I think it is pretty safe just to remove the CRASH > statements in the hidnogui HID. (Both invalidate_lr and invalidate_all). > > Alternatively, we would have to provide a NOP implementation of the two > invalidate calls in each HID. I'd suggest (if thi

Re: gEDA-user: pcb: functions in hidnogui.c

2010-03-15 Thread kai-martin knaak
Peter Clifton wrote: > The reason you can't grep for the hidnogui variant directly is that > these function pointers are installed as a default by macros in > hid/common/hidnogui.c in a call to "apply_default_hid()". This is called > from the various HIDs _init() function. Thanks for the clarific

Re: gEDA-user: pcb: functions in hidnogui.c

2010-03-15 Thread Peter Clifton
On Sat, 2010-03-13 at 00:46 +, Kai-Martin Knaak wrote: > As you might guess from the rant thread, I am still interested in getting > this particular patch applied. It significantly improves the usability > because it provides more versatile command line printing. With the > DISPLAY() action

Re: gEDA-user: pcb: functions in hidnogui.c

2010-03-15 Thread Peter Clifton
On Fri, 2010-03-12 at 20:03 -0500, DJ Delorie wrote: > > Can some developer enlighten me, where the procedure > > nogui_invalidate_lr gets called? > > Run pcb in gdb, set a breakpoint there. > > There are two purposes here... we need a HID that is a prototype for > new HIDs, hence the CRASH comma

Re: gEDA-user: pcb: functions in hidnogui.c

2010-03-12 Thread DJ Delorie
> Can some developer enlighten me, where the procedure > nogui_invalidate_lr gets called? Run pcb in gdb, set a breakpoint there. There are two purposes here... we need a HID that is a prototype for new HIDs, hence the CRASH commands all throughout that. In addition, a "do-nothing" hid is neede

gEDA-user: pcb: functions in hidnogui.c

2010-03-12 Thread Kai-Martin Knaak
As you might guess from the rant thread, I am still interested in getting this particular patch applied. It significantly improves the usability because it provides more versatile command line printing. With the DISPLAY() action I can select whether to print refdes, or value with the components