Hi,
On 04/12/2018 06:41 PM, Michael Frank wrote:
> I have just been observing this thread for a while and I’m wondering if
> (at least for *nix implementations) installing the files into a version
> specific sub-tree and putting links into the “unix/linux way”
> directories might be a solution
Absolutely, but those things need discussion and I’m trying not to bother the
dev team too much until 5.0 is out.
To add to the list:
compliance with schematic (missing nets, missing footprints, etc.) (whether
this goes in DRC or another facility TBD)
text stroke checking
copper density ? (for
Le 13/04/2018 à 14:20, Jeff Young a écrit :
> Hi JP,
>
> Cool; I just wanted to make sure there’s wasn't something I was missing.
> I’ll go ahead and move it
> for 6.0.
>
> Here’s what I’ve got so far (hole-to-hole distance is the only new feature;
> the rest is just UI
> rearrangement):
We have to leave the spaces for the footprint libraries. Otherwise we
will break the behavior that's always been in place. I know it's not
the best situation but hopefully it will be fairly short lived.
On 04/13/2018 07:32 AM, Maciej Sumiński wrote:
> Ok, thank you both for clarification. In
Ok, thank you both for clarification. In such case, I suppose we keep
spaces enabled for footprint library and entry names and disable for
symbol related names. I have found a few places that use different rules
for name validation and I wanted to unify them.
Cheers,
Orson
On 04/13/2018 01:30
Orson,
You must have missed the original conversation. We cannot have spaces
in symbol library nicknames until the schematic and symbol library file
formats are implemented. I didn't want to make a change to the current
schematic file format. Once they are in place, I will remove the spaces
Another question is whether spaces are considered valid in library item
names (symbols/footprints). Should both logical library names and
library items permit the same character set? Seems reasonable to me, but
I need to be sure.
Cheers,
Orson
On 04/13/2018 11:36 AM, Maciej Sumiński wrote:
> I
I have just noticed that one cannot use spaces in symbol library
nicknames [1], whereas they are valid for footprint library nicknames
[2]. I suppose it should be unified and moved to a function (static
method in LIB_ID?) to avoid valid characters sets diversion. I will fix
it, but I need to know
Hi Wayne,
thanks for the clarification.
Cheers
Fabrizio
On Wed, Apr 11, 2018 at 9:10 PM, Wayne Stambaugh
wrote:
> Fabrizio,
>
> We are aware of the issue but it will not be addressed for v5. Chris'
> fix was a stop gap measure until we can implement something better.
Le 12/04/2018 à 23:40, Jeff Young a écrit :
> Not the courtyard graphics, but rather the require-courtyards and
> no-overlapping-courtyard settings?
It needs a file format change, with a very poor benefit.
(I am thinking Design Rules, Layers Setup and DRC should be enhanced (many
missing
10 matches
Mail list logo