On 2020-01-28 09:44, jp charras wrote:
Le 28/01/2020 à 17:15, jp charras a écrit :
Le 28/01/2020 à 15:32, Seth Hillbrand a écrit :
No need. It has already been reported with reproduction steps here
https://gitlab.com/kicad/code/kicad/issues/3811
If you find a bug, use the standard bug reporti
Le 28/01/2020 à 17:15, jp charras a écrit :
> Le 28/01/2020 à 15:32, Seth Hillbrand a écrit :
>> No need. It has already been reported with reproduction steps here
>> https://gitlab.com/kicad/code/kicad/issues/3811
>>
>> If you find a bug, use the standard bug reporting procedure but only
>> repor
Le 28/01/2020 à 15:32, Seth Hillbrand a écrit :
> No need. It has already been reported with reproduction steps here
> https://gitlab.com/kicad/code/kicad/issues/3811
>
> If you find a bug, use the standard bug reporting procedure but only
> report bugs there that reproduce in master.
>
> If you
Thanks!
I would have never found it because I didn't search for "floated".
On 2020-01-28 9:32 a.m., Seth Hillbrand wrote:
No need. It has already been reported with reproduction steps here
https://gitlab.com/kicad/code/kicad/issues/3811
If you find a bug, use the standard bug reporting pro
No need. It has already been reported with reproduction steps here
https://gitlab.com/kicad/code/kicad/issues/3811
If you find a bug, use the standard bug reporting procedure but only
report bugs there that reproduce in master.
If you find a bug that doesn't exist in master but does exist in
Jp
Actually, that is the bug: every time I hit F8 one or more of RN3, RN4,
RN5, and RN6 are shown as new components on the PCB. It deletes the old
RNs and put new ones with the same name.
I got RN3, RN4 then RN3, RN4, RN5 and RN6, then RN3, etc.
Every time I hit F8 the thing rips up those R
Le 28/01/2020 à 01:10, Brian Piccioni a écrit :
> Hello
>
> I have been using Kicad while working on re-annotation (hopefully
> Alexander's merge request will soon be accepted and I can dust off mine).
>
> I have been using branches of the current master. I have noticed a few
> issues which I thi
You can also report the bug including the version info from your branch
(especially if your branch is public) -- if the bug is clearly not with
your code, it should be easy for others to reproduce it.
What I do to make things simpler is to keep several working copies of KiCad
around, so I don't ha
I am pretty sure, yes.
So I should recompile the master branch and try reproduce the bugs and
report as normal?
Another example is one of the bugs is related to buses - if one of a
list { SCL SCK ~CS RD} all items after and including CS have an over bar.
Brian
On 2020-01-27 7:14 p.m., Jon
Can you reproduce these same issues on the master branch? Either the latest
master, or the point on master at which your custom branch splits (i.e. the
most recent rebase point)
Doing so will absolutely rule out that there is anything about your branch
related, and also make it easier to figure out
Hello
I have been using Kicad while working on re-annotation (hopefully
Alexander's merge request will soon be accepted and I can dust off mine).
I have been using branches of the current master. I have noticed a few
issues which I think are significant and not related to Alexander's work
(o
11 matches
Mail list logo
