On Mon, 01 Feb 2010 18:52:40 -0500, DJ Delorie wrote:
Fixed. Amusingly enough, the lesstif hid had the same conflict, but
avoided it as that file didn't pull in the header.
Now it builds, thanks!
___
geda-user mailing list
On Sun, 31 Jan 2010 16:26:59 -0500, DJ Delorie wrote:
and pushed my changes to the master. Enjoy!
fetching it from git but gives me an error while compiling for gtk hid.
in hid/gtk/gui-netlist-window.c:978 is already a function NetlistChanged() as
you introduced with your commits:
I changed the actions to be like this:
ElementList(start)
ElementList(need,...)
ElementList(done)
Netlist(freeze)
Netlist(add,...)
Netlist(thaw)
and pushed my changes to the master. Enjoy! Obviously, we'll keep
fiddling with it as we get more people using it, but
On Fri, 2010-01-29 at 19:33 -0500, DJ Delorie wrote:
Since the import method is gnetlist, I assume we don't have to make
this a gEDA specific field. I did think (briefly) that we ought to
name-space the sources for Import schematics.
What's geda-specific about import::src4 ?
Nothing.. I
On Fri, 2010-01-29 at 13:03 -0500, DJ Delorie wrote:
Well, here it is. Yes, I know it's not in git's pretty format, but
it's a bunch of local commits that make no sense separately. Discuss,
then I'll commit it all.
I'm interested in the diffstat (re-ordered to show the biggest changes):
Minor nit - pcblf is not a great name for the backend. Outside our
circle, lf is probably not something many will understand, and might
end up being one of those FAQ's like Ben mode.
Yup. Suggestions? pcbfa? pcbfwd? pcbimport? pcbmigrate? sch2pcb?
Netlist(Add,name,pin,defer)
On Fri, 2010-01-29 at 14:04 -0500, DJ Delorie wrote:
Good idea. Should freeze/thaw nest, or be a simple flag?
Many implementations nest, emitting the notify when the count gets to
zero. I don't imagine it would be too hard to make the implementation
nest though. I can't (at the moment), think
On Fri, 29 Jan 2010 14:04:29 -0500
DJ Delorie d...@delorie.com wrote:
Minor nit - pcblf is not a great name for the backend. Outside our
circle, lf is probably not something many will understand, and might
end up being one of those FAQ's like Ben mode.
Yup. Suggestions? pcbfa?
On Fri, 2010-01-29 at 14:02 -0600, Vanessa Ezekowitz wrote:
On Fri, 29 Jan 2010 14:04:29 -0500
DJ Delorie d...@delorie.com wrote:
Minor nit - pcblf is not a great name for the backend. Outside our
circle, lf is probably not something many will understand, and might
end up being one
On Fri, 2010-01-29 at 13:03 -0500, DJ Delorie wrote:
import::src0 ... import::src99 (etc)
schematic files. Note that the list stops at the first
missing number in sequence, even if there are higher numbered
sources present.
Since the import method is gnetlist, I assume we
A couple of options I thought of pcb-action or pcb-actions. (Since
it effectively creates a PCB action script - is that right?)
Right, but there are more types of action scripts than just the one
this produces.
(Although since it is gEDA specific, it might be good to mention that)
It isn't.
Since the import method is gnetlist, I assume we don't have to make
this a gEDA specific field. I did think (briefly) that we ought to
name-space the sources for Import schematics.
What's geda-specific about import::src4 ?
For sake of argument, if we had a xcircuit import method, I could
12 matches
Mail list logo
