> On Sep 7, 2015, at 9:13 AM, Bernhard Stegmaier
> wrote:
>
> Hi,
>
> a small note on homebrew (or, MacPorts) for OS X:
> The problem is, that you need a special patched wxWidgets for KiCad.
> So, you can’t (no, you can’t) use the stock one such a package system
> provides - and you probably
The DMGs are not going away and are the primary method for KiCad on OS X.
I'm not going to spend my limited time supporting folks who want to compile
KiCad on their own on OS X, but I'm also not going to hide or obsfucate any
of the helper scripts I use to build it.
On the other hand, it looks li
I think that there should be an easy to grab DMG that can be installed, but
it appears to be trivial to use homebrew casks to "automate" the process.
Keep in mind, casks are *not* compiling anything, they're just grabbing
pre-existing binaries because it makes it "easier" (for CLI folk) to
install
Ian, I think you are right. I think everything is already done, except me
putting the "issue a PR" into Jenkins so it happens periodically.
Adam Wolf
On Tue, Sep 8, 2015 at 12:31 PM, Ian Woloschin wrote:
> I think that there should be an easy to grab DMG that can be installed,
> but it appear
Hooray for already solved problems! :D Too bad the baby is still
sleeping. Time for new things to solve!
For the Gentoo ebuild, will the project consider releasing a source
tarball, or is it just going to be a bzr (...git?) tag in the appropriate
repository? I don't think it matters, I believe
Why don't you target a git or bzr tag--probably easier to reuse the work
for a "nightlies/fresh" ebuild as well.
Adam Wolf
On Tue, Sep 8, 2015 at 12:37 PM, Ian Woloschin wrote:
> Hooray for already solved problems! :D Too bad the baby is still
> sleeping. Time for new things to solve!
>
> Fo
For the stable release I will create a source archive of some sort. If
time permits, I'll try to create them for the rc branches as well.
On 9/8/2015 1:37 PM, Ian Woloschin wrote:
> Hooray for already solved problems! :D Too bad the baby is still
> sleeping. Time for new things to solve!
>
>
In the be careful what you wish for category, I've committed the changes
to enable launching CvPcb from Eeschema in stand alone mode. I also
enabled launching the footprint editor as well. Please note that any
schematic opened that does not have a project file in the same path may
be missing comp
From the hotkey export for eeschema and pcbnew I created a libreoffice/pdf
sheet that's intended to provide a comprehensive view on the hotkeys.
For this purpose, the hotkeys for both subsystems are put together, and
rearranged according to two criteria:
1. Those with comparable functionality i
Wayne, was it your intention to include the incomplete bugs in the
blockers for rc1? I mean, incomplete bugs are bugs that have a
potential to be revived, but where the developers are not really
supposed to spend more time on them until some feedback are given.
I personally don't think they should
What is your intention or goal with this?
2015-09-08 21:00 GMT+02:00 Rob Maris :
> From the hotkey export for eeschema and pcbnew I created a libreoffice/pdf
> sheet that's intended to provide a comprehensive view on the hotkeys.
>
> For this purpose, the hotkeys for both subsystems are put togeth
Am 08.09.2015, 21:04 Uhr, schrieb Nick Østergaard :
What is your intention or goal with this?
Oh, just a contribution to documentation, whether one could use it or not -
that's his or her matter. I created this for an employee who's quite mouse
oriented.
2015-09-08 21:00 GMT+02:00 Rob Mar
I am looking forward to testing/using the changes. Thank you.
2015-09-06 22:03 GMT+02:00 Wayne Stambaugh :
> Since CvPcb being disabled when Eeschema in stand alone mode has been so
> poorly received, I am willing to enable it if no one objects. I did
> some testing last week and I could not find
I think the current situation is as good as we can hope for as far as
blockers for rc1. I'm going to try to create a new version 4 stable
release series on Launchpad Friday if no new show stoppers crop up.
Periodically I will merge any bug fixes from the product branch into the
4 stable series bra
When I export the attached board to VRML. The graphic text on the front
silk screen of the board is not shown. It appears that the graphical
circle on the front silk screen is either obscuring the text or the text
on the front silk screen layer has been completely replaced by the
circle rather th
I think this would be a great usability improvement if the hotkeys are
arranged homogeneously in both applications. This is one usability issue
that seemed very weird to me as trying to switch to KiCad and not used to
complex design programs.
I'm not sure if this change could be substantial to cau
Hi Wayne,
This is a logic fault (definitely a bug). The exporter composes each
layer by
creating a single layer of outlines and a single layer of cutouts. When the
cutouts are applied at a later stage, in this instance the text in the
circle is
obliterated. A little thought is required here; I s
Wayne,
thank you for your reply.
I already noticed that there is the link
http://kicad-pcb.org/help/external-tools/
What I'm missing are the 2 images that I made with hackrf-one in kicad
3d-viewer and in MCAD Catia.
Those images were been included in old kicad web site.
http://confluence.ki
Hi,
I'm trying to import a simple dxf outline that is made from 4 arcs. The
figure was designed in freecad, and exported as dxf.
Importing that dxf in kicad didn't work, so I opened the dxf in librecad
and saved it as DXF R12, and the result was the same.
I know the dxf import is not fully suppo
In response to a message written on 09.09.2015, 05:24, from Marcos Chaparro:
I'm trying to import a simple dxf outline that is made from 4 arcs. The
figure was designed in freecad, and exported as dxf.
Importing that dxf in kicad didn't work, so I opened the dxf in librecad and
saved it as DXF
>
> Seems that is kind of Berzier Curve, not few arcs. Probably that shape
>> needs to
>>
> split to single arcs before import.
Um, I don't know if its converted to a bezier curve, but I'm sure I made it
from 4 arcs, see attached.
___
Mailing list: htt
KiCad DXF import for those kind of segments don't work very well. You
need to re-export the DXF in a DXF R12 format.
You can do that easily by opening the DXF in LibreCAD and then
reexporting in R12 format.
See http://docs.kicad-pcb.org/Pcbnew/Pcbnew.html#_creating_a_board
Section 6.1.2 and
Hi Marcos,
Apologies, but I did not see your original email where you said you
tried the R12 format alreayd.
I tried it as well and and it indeed seems to do something strange with
just connecting the end points of the circles or something.
Regards,
Marco
On 09-Sep-15 14:29, Marco Hess wr
Definitely a problem with the DXF importer I would say as the resulting
data in the PCB file are just straight line segments:
(gr_line (start 42.68541 28.017695) (end 52.25 35.66) (layer
Edge.Cuts) (width 0.1))
(gr_line (start 27.328145 43.265288) (end 42.68541 28.017695) (layer
Edge.Cuts
Timofonic: I'd suggest you to raise your awareness about this and then modify
hotkey assignments from within eeschema resp. pcbnew. You could then evaluate
if such modifications would represent a good path to some more homogenous
appearance.
Having said this, there are of course no bug "danger
25 matches
Mail list logo
