Le 28/11/2015 22:23, Mark Roszko a écrit :
> KiCad is graphically really broken on high DPI screens like my Surface
> Book and Surface Pro. (I literally just got a Book a few days ago so I
> never knew)
>
> On the high DPI display, it gets really bad with say the pcbcalculator
> where the images a
Examples of how it looks:
http://i.imgur.com/vFsKhBR.png
http://i.imgur.com/v1nkL7u.png
Not unusable but incredibly annoying
On Sat, Nov 28, 2015 at 4:23 PM, Mark Roszko wrote:
> KiCad is graphically really broken on high DPI screens like my Surface
> Book and Surface Pro. (I literally just got
KiCad is graphically really broken on high DPI screens like my Surface
Book and Surface Pro. (I literally just got a Book a few days ago so I
never knew)
On the high DPI display, it gets really bad with say the pcbcalculator
where the images are tiny and unreadable.
But if anything should be a "
Just a quick update on the license front. I received permission to use
the gEDA symbol library exception license for use in our libraries. I
have sent an initial draft to the FSF for comment just to make sure it's
sane. As soon as I hear back from them, I will forward the license text
to be adde
If there is any reason not to roll out the stable release tomorrow,
speak now or forever hold your peace. I will roll it out tomorrow
evening assuming there are no serious bugs between now and then. If you
have any last minute bug fixes, please submit or commit them.
If you have any developers t
I would tag them. User's who get their footprints via the github plugin
are going to get the latest and greatest. This would only impact
packages that distribute the footprint libraries. Same goes for the
symbols and 3D model libraries. We may want to create a 4.0 archive of
the symbol and 3D m
I'll let you manage it on KiCad's side and I'll take care of tagging.
On Sat, Nov 28, 2015 at 5:03 AM, Nick Østergaard wrote:
> I vote for tagging, I don't think we will have much use of branching the
> libs. When they are tagged on all repos we can easily fetch a consistent
> package, and we ca
I vote for tagging, I don't think we will have much use of branching the
libs. When they are tagged on all repos we can easily fetch a consistent
package, and we can provide that as a download for those who wants that. I
can tag them if you want.
Den 28/11/2015 01.08 skrev "Carl Poirier" :
> So wh
8 matches
Mail list logo
