Zficani, are you still working on this? It came up in
https://gitlab.com/kicad/code/kicad/issues/1973#note_277712551.
You could fork in gitlab and make it a merge request.
Eeli Kaikkonen
On Sat, Oct 26, 2019 at 3:58 AM Zficani Zficani wrote:
> Hi,
> I'm sorry for the delay but I finally got ev
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
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
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
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
5 matches
Mail list logo
