gene wrote:
> wow, a (supposed) really simple question has really spawned a lot of
> discussion!
>
the ideas you all have posted have merit.
Only... we're not trying to acquire merit, as Kipling wrote, but
merely to get some halfway consensus...
In the near term, it's going to go the way whoe
wow, a (supposed) really simple question has really spawned a lot of
discussion!
Hey, I also don't think the tools should enforce a naming convention on
the user. From these responses, it's pretty clear that we each have our
own idea on what is best for ourselves. By and large, they are all
On Sunday 06 April 2008 19:10, Kai-Martin Knaak wrote:
> > My opinion: No, but the netlister should convert non-compliant
> > names to compliant names, and conversion back should restore the
> > original name.
>
> My opinion: Please don't resort to such syntax tricks behind the
> scenes. Those sch
Hi Vinny,
Once you have edited and saved a part, go back to the schematic, select
the part, then select "Edit" and then "Update Component" or use the
shortcut "ep." This should reload that component and update the schematic.
If you have multiple instances of the component, highlight them all
On Sun, 06 Apr 2008 18:10:00 -0400, al davis wrote:
> The real question: Should gschem attempt to enforce naming conventions
> of the various targets?
gnetlist is the component which is responsible for breakage in the
gschemm-gnetlist-pcb workflow. So gnetlist should is the application at
faul
On Sunday 06 April 2008 13:33, Kai-Martin Knaak wrote:
> Would it be very hard to make net names more robust against use of
> all the characters printed on modern keyboard? Footprint names could
> benefit from such robustness too. Hyphens in the footprint brought
> quite a bit of frustration during
Attaching a source=fileX.sch works great for getting to sub-sheet(s). I
can attach them to the instantiated symbol, or can embed it into the
symbol (both methods navigate nicely). But when it's embedded, they are
not visible at the instantiated schematic level (i.e. selecting the
symbol and "
Kai-Martin Knaak wrote:
> Would it be very hard to make net names more robust against use of all
> the characters printed on modern keyboard? Footprint names could benefit
> from such robustness too. Hyphens in the footprint brought quite a bit of
> frustration during my early days of geda adop
Stuart Brorson wrote:
> LVPECL_LINE_IN_P
> LVPECL_LINE_IN_N
> MRESET_L
> CML_OPTO_OUT_P
> CML_OPTO_OUT_N
> LATCH_L
> TTL3P3_DATA[7:0]
> LVDS_DATA[15:0]_P
> LVDS_DATA[15:0]_N
>
> I did this because we used a spreadsheet program to attach routing
> attributes (e.g. diff pair length tolerances) to t
> [EMAIL PROTECTED]
>
>
> 2. Parts modified are not available until reloaded gschem
> (Vincent Onelli)
>
> --
>
> Message: 5
> Date: Sun, 6 Apr 2008 12:01:31 +0200
> From: Levente <[EMAIL PROTECTED]>
> Subject: Re: gEDA-user: Parts modified are not available until
On Sun, 06 Apr 2008 10:01:41 -0500, John Griessen wrote:
> al davis wrote:
>
>> The leading "+" is one of those problems. Underscores are usually ok.
>> Embedded "+" is also sometimes a problem. "foo+bar" .. is that the
>> sum of foo and bar?
>
> Does everyone understand a trailing underscore
>>> Does everyone understand a trailing underscore as negative logic?
>>
>> No.
>>
>> In my experience, a negatively asserted signal can be flagged in
>> several different ways,
>
> A suffix of SIG_N seems good -- it can either signify Not() or
> Negative logic or Negative half of a pair...
That's
CADENCE Framework II uses e.g. _CLK to write CLK with a bare above the string
for pin lables of symbols, to indicated an inverted CLK signal (input) port.
But these labels are not used as net names or something else.
Peter
Am Sonntag, 6. April 2008 17:16:33 schrieb Stuart Brorson:
> > Does eve
Stuart Brorson wrote:
>> Does everyone understand a trailing underscore as negative logic?
>
> No.
>
> In my experience, a negatively asserted signal can be flagged in
> several different ways,
A suffix of SIG_N seems good -- it can either signify Not() or
Negative logic or Negative half of a p
> Does everyone understand a trailing underscore as negative logic?
No.
In my experience, a negatively asserted signal can be flagged in
several different ways, depending upon who is talking about the
signal.
In PCI bus land, signals asserted low are suffixed with a pound sign,
#. For example:
al davis wrote:
> The leading "+" is one of those problems. Underscores are usually ok.
> Embedded "+" is also sometimes a problem. "foo+bar" .. is that the
> sum of foo and bar?
Does everyone understand a trailing underscore as negative logic?
A trailing * is not so hot script-wise...
J
OK, that's sort of what I thought- thanks. ?It's just that I hate the
look of "+3_3V", but maybe "+3r3V" isn't so ugly.
The leading "+" is one of those problems. Underscores are usually ok.
Embedded "+" is also sometimes a problem. "foo+bar" .. is that the
sum of foo and bar?
I agree with t
al davis wrote:
> On Sunday 06 April 2008 09:36, gene wrote:
>> Is it ok to name a net "3.3VD", for example, using the "."? I
>> haven't tried it yet, so was just looking for a quick answer to save
>> some time.
>
> It's better not to. Even if gschem accepts it, sometimes the netlister
> doesn'
On Sunday 06 April 2008 10:19, gene wrote:
> OK, that's sort of what I thought- thanks. It's just that I hate the
> look of "+3_3V", but maybe "+3r3V" isn't so ugly.
The leading "+" is one of those problems. Underscores are usually ok.
Embedded "+" is also sometimes a problem. "foo+bar" .. i
OK, that's sort of what I thought- thanks. It's just that I hate the
look of "+3_3V", but maybe "+3r3V" isn't so ugly.
al davis wrote:
> On Sunday 06 April 2008 09:36, gene wrote:
>> Is it ok to name a net "3.3VD", for example, using the "."? I
>> haven't tried it yet, so was just looking for a
On Sunday 06 April 2008 09:36, gene wrote:
> Is it ok to name a net "3.3VD", for example, using the "."? I
> haven't tried it yet, so was just looking for a quick answer to save
> some time.
It's better not to. Even if gschem accepts it, sometimes the netlister
doesn't map things like that prop
Is it ok to name a net "3.3VD", for example, using the "."? I haven't
tried it yet, so was just looking for a quick answer to save some time.
thanks
gene
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinf
On Sat, 05 Apr 2008 17:58:25 -0500
Vincent Onelli <[EMAIL PROTECTED]> wrote:
> Hi,
> I am fairly new at gschem, I found that if I modify a part then save in the
> same name the modification do not show when the part is reloaded until
> gschem is reloaded. Same if the modified part is saved under d
On Sat, 05 Apr 2008 09:28:43 -0500
John Griessen <[EMAIL PROTECTED]> wrote:
> Levente wrote:
>
> > http://web.interware.hu/lekovacs/reflow_oven/index.html
> >
> > Actually, it is an electric heater. The problem is that the heat exchange
> > is slow, and it can't maintain the slopes coming from t
24 matches
Mail list logo
