Re: gEDA-user: Is there any way to disable mouse over commands in pcb?
On Thu, 11 Mar 2010 12:56:19 -0500, DJ Delorie wrote: All key bindings are user-controllable via the ~/.pcb/pcb-menu.res (lesstif) or ~/.pcb/gpcb-menu.res files. cite pcb/src/gpcb-menu.res : / # NOTE: I have not figured out what to do with this # section yet. The Mouse section is currently ignored until # I figure out how to handle it. \ So, no joy for the default configuration of pcb, that is, GTK HID. By the way, who is the I referred to in the comment? ---(kaimartin)--- -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key:http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmkop=get ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Is there any way to disable mouse over commands in pcb?
So, no joy for the default configuration of pcb, that is, GTK HID. The mouse section is not the menu/key section. That comment only applies to the mouse buttons (assuming it still applies at all). ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: pcb: functions in hidnogui.c
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. Peter Clifton reminded me, that one obstacle to the application is the necessity to remove a CRASH statement in hidnogui.c. It should be checked, that the removal does not have any undesired side effect. However, I can't judge what this function is supposed to do because there is no clarifying comment and it's name is mentioned nowhere else in the source. Can some developer enlighten me, where the procedure nogui_invalidate_lr gets called? ---(kaimartin)--- -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key:http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmkop=get ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb: functions in hidnogui.c
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 needed for non-GUI runs. However, we also have the batch HID for running batch commands, perhaps we should use that instead of the nogui hid? ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: pcb option --layer-stack
The output of pcb -h says: / --layer-stack string Initial layer stackup, for setting up an export. \ This seems to be a means to choose the output layers when printing from the command line. If I deliberately set the string to some arbitrary value, I get a warning telling me that this is no good layer name, followed by a list of allowed layer names. I get no such warning, if I use these layer names separated by commas. So I assume, my string gets accepted as a layer-stack. However, the eps export HID does not seem to care what layers I mention in the layer stack. I always get all layers with the silk screen printed on top. Is this a bug, or do I misinterpret the description of the layer- stack option? ---(kaimartin)--- PS: There is no description whatsoever on layer stacks in the pcb manual. Most options in the section command line options are obsolete http://pcb.gpleda.org/pcb-cvs/pcb.html#Command_002dLine-Options Is there a reason, why this section of the manual did receive an update when the actual command line options were changed? I have mentioned this deficiency in the manual more than once on the mailing list, since I started looking into command line printing -- about two years ago. Would it help, if I file a bug report on this rather misleading documentation? If this is again a case of lack of developer cycles, how about letting trusted non-developers improve the manual? -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key:http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmkop=get ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb option --layer-stack
Did you include the --as-shown option too? PS: There is no description whatsoever on layer stacks in the pcb manual. The woefully obsolete manual? If this is again a case of lack of developer cycles, how about letting trusted non-developers improve the manual? Go ahead. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Open Source mechanical CAD on the horizon
Hi, maybe somehow late but please give openscad [1] a trial. 1. It converts dxf-drawings in 3D Models 2. It uses a language (C style) instead of a GUI to describe 3D models Thus, it might be much closer to the way of gEDA. I'm just on the way to try out how good this works out for 3D printers. Furthermore there is the Mini-T project from Makerbeam [2]. An aluminium profile construction kit. Similar to item or isel but much smaller. It will be somehow the a mixture between fisher-technic toy and T-profiles. Hope this is useful Bye Torsten [1] http://openscad.org/ [2] http://www.makerbeam.com/ 2010/2/25 Kai-Martin Knaak k...@familieknaak.de: I just got aware of the open source mechanical CAD project freecad. It hit the debian repository a month ago. Although it is still lacking important features, much of the basic infrastructure is already up and running. http://en.wikipedia.org/wiki/FreeCAD_(Juergen_Riegel) ---(kaimartin) -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key: http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmkop=get ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb option --layer-stack
On Fri, 12 Mar 2010 20:30:16 -0500, DJ Delorie wrote: Did you include the --as-shown option too? That did the trick. Now I can print specific layers :-) But what I really want, is a print of the components on the bottom side of the board. So I added --action-string 'SwapSides()' to the command line. Unfortunately, this gets me a segfault: $ pcb -x eps --layer-stack bottom,silk \ --as-shown \ --action-string 'SwapSides()' \ --eps-file /tmp/out.eps phasen.pcb Looking for default_font in . Can't open ./default_font for reading Looking for default_font in /usr/local/bin/../share/pcb Found default_font in /usr/local/bin/../share/pcb Loading file phasen.pcb took 3.81 seconds of CPU time Executing startup action SwapSides() Segmentation fault Note, whatever causes this, is exposed by my command line print patch. Without the patch the action string would not be executed in the first place. It is not a general problem, though. Other actions like Display() are executed fine. Any idea where to look for a reason for the segfault? PS: There is no description whatsoever on layer stacks in the pcb manual. The woefully obsolete manual? Sure. Is there any other? ;-) If this is again a case of lack of developer cycles, how about letting trusted non-developers improve the manual? Go ahead. Ok, I'll bite. Looks like the manual is derived from pcb/doc/pcb.texi . So I'll edit this file and and post a diff to this mailing list, right? ---(kaimartin)--- -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key:http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmkop=get ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb option --layer-stack
But what I really want, is a print of the components on the bottom side of
the board. So I added --action-string 'SwapSides()' to the command line.
Add the solderside layer to your layer stack string (see attached
code snippet)
Any idea where to look for a reason for the segfault?
gdb?
Looks like the manual is derived from pcb/doc/pcb.texi . So I'll edit
this file and and post a diff to this mailing list, right?
Yup. Git patch format, please.
for (i=argn-1; i=0; i--)
{
if (strcasecmp (args[i], rats) == 0)
PCB-RatOn = True;
else if (strcasecmp (args[i], invisible) == 0)
PCB-InvisibleObjectsOn = True;
else if (strcasecmp (args[i], pins) == 0)
PCB-PinOn = True;
else if (strcasecmp (args[i], vias) == 0)
PCB-ViaOn = True;
else if (strcasecmp (args[i], elements) == 0
|| strcasecmp (args[i], silk) == 0)
PCB-ElementOn = True;
else if (strcasecmp (args[i], mask) == 0)
SET_FLAG (SHOWMASKFLAG, PCB);
else if (strcasecmp (args[i], solderside) == 0)
Settings.ShowSolderSide = 1;
else if (isdigit ((int) args[i][0]))
{
lno = atoi (args[i]);
ChangeGroupVisibility (lno, True, True);
}
else
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Is there any way to disable mouse over commands in pcb?
Kai-Martin Knaak wrote: On Thu, 11 Mar 2010 12:56:19 -0500, DJ Delorie wrote: All key bindings are user-controllable via the ~/.pcb/pcb-menu.res (lesstif) or ~/.pcb/gpcb-menu.res files. cite pcb/src/gpcb-menu.res : / # NOTE: I have not figured out what to do with this # section yet. The Mouse section is currently ignored until # I figure out how to handle it. \ So, no joy for the default configuration of pcb, that is, GTK HID. By the way, who is the I referred to in the comment? git annotate src/gpcb-menu.res would seem to indicate that I am I. And... that comment is out of date and should be removed. -Dan ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb option --layer-stack
Kai-Martin Knaak wrote: PS: There is no description whatsoever on layer stacks in the pcb manual. The woefully obsolete manual? Sure. Is there any other? ;-) If this is again a case of lack of developer cycles, how about letting trusted non-developers improve the manual? Go ahead. Ok, I'll bite. Looks like the manual is derived from pcb/doc/pcb.texi . So I'll edit this file and and post a diff to this mailing list, right? if you feel like working on the command line options part of the manual, there are two ideas that have been floated around. Both involve ways to keep the documentation source embedded in the code. This has worked very well for the file format (see structured comments in parse_y.y) and actions (%doc-start comments all over). The two options discussed so far are 1) use more special comments in the source to document command line stuff. Leverage the gather-actions script. Advantages are you can get all the various options without having to build a native pcb (i.e. works for cross compiling, works for getting lesstif and gtk options from the same build). Disadvantage is I couldn't see a reasonable way to not have to type in the help text twice. 2) add an undocumented (since it will be for our internal use, grep for ben-mode in src/hid/png/png.c for an example) --help-texi option. Then you get out basically the same as --help output but in .texi format for inclusion in the manual. Advantages are if you are doing a native build (no cross compile) you can get a manual that only has your options and no others. Disadvantage is I think we'd prefer the manual to always be complete and each section would start with a note about ...this exporter/gui may not always be compiled in The current approach of there being no link between code (or comments within a few lines of the code) I think will always lead us to the current state of the manual being out of date for that part. -Dan ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb option --layer-stack
On Fri, 12 Mar 2010 22:45:28 -0500, DJ Delorie wrote: But what I really want, is a print of the components on the bottom side of the board. Add the solderside layer to your layer stack string (see attached code snippet) Thanks. This finally worked :-) I added this tip to the wiki. For the archive: pcb -x eps --layer-stack outline,silk,solderside \ --as-shown \ --action-string 'Display(Value)' \ --eps-file /tmp/out.eps phasen.pcb Any idea where to look for a reason for the segfault? gdb? I feared so ;-) Looks like the manual is derived from pcb/doc/pcb.texi . So I'll edit this file and and post a diff to this mailing list, right? Yup. Git patch format, please. That is, use the command git format-patch ? Any options to add? ---(kaimartin)--- -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key:http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmkop=get ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb option --layer-stack
That is, use the command git format-patch ? Any options to add? Don't know, I'm new at this too. I've been told that git patches are what we want, I suppose either format-patch to the mailing list, or a public repository we can fetch from, would suffice. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb option --layer-stack
On Fri, 12 Mar 2010 23:58:12 -0500, Dan McMahill wrote: if you feel like working on the command line options part of the manual, there are two ideas that have been floated around. Both involve ways to keep the documentation source embedded in the code. sounds good. 1) use more special comments in the source to document command line stuff. Leverage the gather-actions script. I fail see how the gather-actions script works. The comment suggests to put comments like /* ACTION(name,func) */ in the source. The perl source does indeed look for this string. However, grep finds no such comments in the source. Instead, there are comments like /* %start-doc actions all over the place. 2) add an undocumented (since it will be for our internal use, grep for ben-mode in src/hid/png/png.c for an example) --help-texi option. Then you get out basically the same as --help output but in .texi format for inclusion in the manual. Hmm, if there is already a way to extract formated comments to texinfo, I'd rather not invent a separate one from scratch. ---(kaimartin)--- -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key:http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmkop=get ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb option --layer-stack
You want the doc/extract-docs script, not gather-actions. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
