Hello Jeff,
I've tried my big board and the clearances seem to work OK for planes.
I still have to compare the gerbers and check if they are exactly as
expected.
However I get a lot of clearance error on holes in the board, and am
unable to solve this. I've attached an example project. There is
The short answer is a lot. I know the OS will clean up allocated memory
on application close but this lackadaisical attitude is not good
programming practice. Chances are if you are not concerned about
cleaning up memory on application close, then you are probably not very
concerned about memory
I recently merged some changes into the symbol library editor to support
field inheritance. I created a formal announcement[1] on the user forum
for information and comment. Please comment on the user forum rather
than the mailing list. It's easier to keep track of the discussion on
the forum.
Mark,
Yes, last selector. Order of rules (at present) doesn’t matter.
No, we were not planning on keeping the separation, although we did discuss
supporting named conditions.
Cheers,
Jeff.
> On 2 Jun 2020, at 13:00, mdoes...@xs4all.nl wrote:
>
> Hello Jeff,
>
> I assume in that case the
Hello Jeff,
I assume in that case the last selector is applied and not the last
rule, correct?
To be honest I prefer the selector/rule seperation, is that going to stay?
regards,
Mark.
Jeff Young wrote:
Hi Mark,
The condition syntax was just a preview. It???s not
Hi Mark,
The condition syntax was just a preview. It’s not implemented yet.
You’ll need to use the selector syntax for now.
So, for instance:
(selector (match_netclass "Net-(C1-Pad1)") (match_netclass "Net-(C1-Pad1)”)
(rule “Min_Net-(C1-Pad1)")
Cheers,
Jeff.
> On 2 Jun 2020, at 11:05,
Well, the jenkins job that prepares the copr package fails to clone the 3d
models for some reason, maybe the repo grew massively in size recently.
tir. 2. jun. 2020 04.01 skrev Oleg Endo :
> Hi all,
>
> The Fedora nightly builds are already 4 days behind.
> Did something get stuck there?
>
>
I just tested the old simple testcase, the new rule file is:
(rule "Max_Net-(C1-Pad1)"
(constraint clearance (min 1.3mm))
(condition "A.netclass == Net-(C1-Pad1)"))
(rule "Min_Net-(C1-Pad1)"
Hi Mark,
Rules are now evaluated in order: last one which matches wins.
Most of the time you won’t need priority, but if you do have two rules that
match the same things, put the higher priority one later in the rules file.
Cheers,
Jeff.
> On 2 Jun 2020, at 09:41, mdoes...@xs4all.nl wrote:
>
Hello Jeff,
I tried to give the big board a new attempt, previously a lot of strange
things happened which I quite couldn't figure out. I noticed the priority
was no longer accepted. Can you give a quick update on the intended way
the rules are supposed to be used?
regards,
Mark.
10 matches
Mail list logo
