On 11/19/09, Peter Clifton wrote:
> I tried it, and couldn't reproduce a crash, neither under gdb or
> valgrind. What are the steps to reproduce?
I had reproduced it faultlessly on two different machines
with different GUIs before I reported; after your post
I went to a third and reproduced it so
On Nov 19, 2009, at 11:10 AM, Peter Clifton wrote:
> The code which refreshes the pin-numbers when you change these
> unusually
> attached attributes is broken (missing) in git HEAD. Various special
> case checks for "slot=" exist, but none of the others. Nice things
> start
> to happen when
The bottom line question for the core developers is:
What prevents us from writing a file of Guile functions and adding a
line to gafrc to load it and get this functionality?
On Nov 19, 2009, at 1:53 PM, Henry Von Bank wrote:
>
> After a symbol is placed in the schematic an attribute should be
On Thu, 2009-11-19 at 18:39 +, Ineiev wrote:
> Hello;
>
> I just fed tut1.pcb from PCB distribution to DRC and got another
> segmentation fault.
I tried it, and couldn't reproduce a crash, neither under gdb or
valgrind. What are the steps to reproduce?
Are you on Lesstif or GTK?
Admittedly
While I am wasting time with this mailing list when I should be
working, here is how I propose to change the symbol organization.
Feel free to do with this as you wish, including criticizing any of
the (I'm sure many) issues with this proposal.
Symbol file
The symbol itself should
Henry Von Bank wrote:
>What I would propose would be to leave the slotting behavior alone for
>the time being (option a), but hopefully mark it for deprecation in
>some future version, as it can be confusing and is not well defined.
>
We could actually leave it alone almost indefini
On Thu, 2009-11-19 at 12:38 -0600, Bill Gatliff wrote:
> Kai-Martin Knaak wrote:
> >
> >
> > The two other EDA suites I worked (eagle and protel) with maintain the
> > notion of a "component" that contains all the info. In a way, this is a
> > very heavy symbol that knows about slots, possible fo
Bill Gatliff wrote:
> Kai-Martin Knaak wrote:
>
>> The two other EDA suites I worked (eagle and protel) with maintain the
>> notion of a "component" that contains all the info. In a way, this is a
>> very heavy symbol that knows about slots, possible footprints and which
>> schematic symbols
Hello;
I just fed tut1.pcb from PCB distribution to DRC and got another
segmentation fault.
diff --git a/src/find.c b/src/find.c
index 1962234..d5f1332 100644
--- a/src/find.c
+++ b/src/find.c
@@ -4417,6 +4417,7 @@ BuildObjectList (int *object_count, long int
**object_id_list, int **object_type
Kai-Martin Knaak wrote:
>
>
> The two other EDA suites I worked (eagle and protel) with maintain the
> notion of a "component" that contains all the info. In a way, this is a
> very heavy symbol that knows about slots, possible footprints and which
> schematic symbols are necessary to represent
Bill Gatliff wrote:
> Now I'm beginning to see the problems with slotting and symbols the way
> we're doing them now: they unnecessarily tie the concept of a symbol to
> the concept of a component, because the pin numbers that we currently
> record in our symbols are also the pin numbers that the
I've been using gEDA for a while, and have been following this thread
closely. There have been a lot of good arguments from all sides for
how things should work. I'm wondering if we should take a more
pragmatic way of looking at things. There are a few options:
a) keep the slotti
> > If they fitted a dooms-day device controller on the spare die-space of
>
> May I remind you your under a NDA!
No Doomsday Agreement?
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
On Thu, 2009-11-19 at 10:38 -0600, Bill Gatliff wrote:
> Now I'm beginning to see the problems with slotting and symbols the way
> we're doing them now: they unnecessarily tie the concept of a symbol to
> the concept of a component, because the pin numbers that we currently
> record in our symbols
Bill Gatliff wrote:
> Now I'm beginning to see the problems with slotting and symbols the way
> we're doing them now: they unnecessarily tie the concept of a symbol to
> the concept of a component, because the pin numbers that we currently
> record in our symbols are also the pin numbers that the
On Nov 19, 2009, at 9:38 AM, Bill Gatliff wrote:
> Peter Clifton wrote:
>> Lets say I have a symbol:
>>
>> ---|\
>> ---|/
>>
>>
>> That might have 4 slots - IE.. I expect 4 of those nand gates in the
>> chip.
>>
>
> ... and I think that might be where the problem suddenly cre
On Nov 19, 2009, at 6:03 AM, Vincent Onelli wrote:
> Hello,
>
> I downloaded teardrop.c file, I would like to use, but I do not know
> how
> to compile and install can anybody give me direction?
> Thank you. Vinny
>
>
http://github.com/bert/pcb-plugins/
go clone that repo, and it has a makefil
On Nov 19, 2009, at 7:18 AM, Peter Clifton wrote:
> If they fitted a dooms-day device controller on the spare die-space of
> the chip.. that again, could be a separate symbol.
May I remind you your under a NDA!
___
geda-user mailing list
geda-user@m
On Thu, 19 Nov 2009 15:18:39 +, Peter Clifton wrote:
> We could "probably" do with some additional annotations "somewhere"
> about exactly what pieces constitute a physical device - or sub-circuit,
> but that that would be an addition - rather than the abuse of an
> existing interface.
The tw
Peter Clifton wrote:
> Lets say I have a symbol:
>
> ---|\
> ---|/
>
>
> That might have 4 slots - IE.. I expect 4 of those nand gates in the
> chip.
>
... and I think that might be where the problem suddenly creeps in.
The _component_ defines how many and what kinds of ci
On Nov 19, 2009, at 6:53 AM, Bill Gatliff wrote:
> Peter TB Brett wrote:
>> And, furthermore, if I/we fixed it to work as designed, some users
>> would be
>> up in arms -- because they have been using the mechanism in a way
>> contrary
>> to its design, and fixing it to work as designed has b
On Thu, 2009-11-19 at 09:03 -0500, Vincent Onelli wrote:
> Hello,
>
> I downloaded teardrop.c file, I would like to use, but I do not know how
> to compile and install can anybody give me direction?
> Thank you. Vinny
>
http://www.delorie.com/pcb/teardrops/
__
> I downloaded teardrop.c file, I would like to use, but I do not know how
> to compile and install can anybody give me direction?
http://www.delorie.com/pcb/teardrops/
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/ma
On Thu, 2009-11-19 at 09:03 -0500, Vincent Onelli wrote:
> Hello,
>
> I downloaded teardrop.c file, I would like to use, but I do not know how
> to compile and install can anybody give me direction?
> Thank you. Vinny
http://www.delorie.com/pcb/teardrops/
Quoting:
"""
Install
Compile like this:
On Nov 19, 2009, at 1:33 AM, Peter TB Brett wrote:
> On Wed, 18 Nov 2009 16:21:10 -0700, John Doty wrote:
>
>>> I hold that a "slot" is related to a multiplicity of identical units
>>> within the chip, and the slotting mechanism was _not_ intended as an
>>> arbitrary way of fudging different com
On Thu, 2009-11-19 at 01:23 +, Kai-Martin Knaak wrote:
> On Wed, 18 Nov 2009 16:17:02 +, Peter Clifton wrote:
>
> > It is a perfect example of why gEDA can never grow more "friendly"
> > interfaces to these problems. _Because_ the existing interface can be
> > abused - and people think it
On Nov 19, 2009, at 3:00 AM, Michael Sokolov wrote:
> John Doty wrote:
>
>> A powerful component of an electronic design *automation* process.
>> Not the usual fritterware tool that forces you to tell it what to do,
>> repeatedly, by manual operation. Do graphics with GUI, do flow with
>> script
On Nov 18, 2009, at 3:06 PM, Peter Clifton wrote:
> On Wed, 2009-11-18 at 20:53 +, Peter Clifton wrote:
>> On Wed, 2009-11-18 at 18:57 +0100, Stephan Boettcher wrote:
>
>>> I think I'd prefer flexible mechanism instead of multiple mechanism
>>> doing almost the same.
>>
>> Fine, condemn us to
Hello,
I downloaded teardrop.c file, I would like to use, but I do not know how
to compile and install can anybody give me direction?
Thank you. Vinny
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/ged
Peter TB Brett wrote:
> And, furthermore, if I/we fixed it to work as designed, some users would be
> up in arms -- because they have been using the mechanism in a way contrary
> to its design, and fixing it to work as designed has broken their
> schematics.
>
During the transition between the
On Wed, 18 Nov 2009 16:21:10 -0700, John Doty wrote:
>> I hold that a "slot" is related to a multiplicity of identical units
>> within the chip, and the slotting mechanism was _not_ intended as an
>> arbitrary way of fudging different combinations of pin-numbers into
>> the
>> netlist in variou
Hey Peter I just tried your color scheme and it looks great, I'll
definately be using it. Thanks.
On Wed, Nov 18, 2009 at 2:43 PM, Peter Clifton wrote:
> On Wed, 2009-11-18 at 14:02 -0800, Anthony Shanks wrote:
>> I've tried looking at some pcb docs and have played around with the
>> preferences
32 matches
Mail list logo
