On 12.03.2016 05:20, Carl Poirier wrote:
Sooo:
- If the size is not specified, then assume it is 60mils
- From now on, default size is 50mils (as per KLC)
- From now on, never omit the size (or specify it in a header)
It would be great if developers add grid origin and user grid size to
file he
Sooo:
- If the size is not specified, then assume it is 60mils
- From now on, default size is 50mils (as per KLC)
- From now on, never omit the size (or specify it in a header)
Then we have the backwards compatibility and contributors don't get caught
by submitting pull requests using a 60mils si
As part of the translation code rework that i am working on (and
auto-detection) part of it is moving the need for changing anything in
code to add a new language. As part of this involves the flags i was
wondering whether anyone would be against moving them into the i18n
repo (and distributed in t
I just tried to build on ubuntu 14.04 with the first patch from Simon
and it built without any problems. And that is with boost 1.54 and not
python scripting enabled. This was tested in a docker container.
2016-03-11 21:52 GMT+01:00 Wayne Stambaugh :
> I would prefer a solution to fix this before
I would prefer a solution to fix this before I commit the patch.
On 3/11/2016 1:01 PM, Mark Roszko wrote:
> The issue is with gcc 4.8 which has C++11 but funny #defines. Boost
> 1.55 only adds flags that have to be enabled manually to work around it.
> Ubuntu 14 has gcc4.8. Debian Jessie has gcc4.
I'm not opposed to adding a global font definition but adding the
default parameters for every single text definition would be
unacceptable. I'm assuming you are going to include the font, weight,
italics, orientation, etc. information to this as well as they all have
default values which are curr
I hope we don't add more things like this in the future.
Adding a header to the file with "default font size is 60 mils" or
whatever, and setting omitted font size in the file to use the header
value, would add only a few bytes over what the current is--except there
wouldn't be a magic constant in
The issue is with gcc 4.8 which has C++11 but funny #defines. Boost
1.55 only adds flags that have to be enabled manually to work around it.
Ubuntu 14 has gcc4.8. Debian Jessie has gcc4.9.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to
Hi,
On 11.03.2016 17:48, Wayne Stambaugh wrote:
> It still sounds to me that boost needs to be bumped to 1.55 and possibly
> some definitions need to added to the build configuration for Boost to
> build properly.
Hm, compiling worked for me with Boost 1.55 on Debian with no further
changes.
It still sounds to me that boost needs to be bumped to 1.55 and possibly
some definitions need to added to the build configuration for Boost to
build properly. If someone can include those changes along with Simon's
original patch. I'll give it go and commit it if I don't have any
issues. If the
Patch committed in r6617. Thanks.
On 3/7/2016 10:09 AM, Simon Wells wrote:
> Please find updated patch, This should be final version
>
> On Sun, Mar 6, 2016 at 8:00 AM, jp charras wrote:
>> Le 05/03/2016 19:48, Simon Wells a écrit :
>>> thanks jp
>>>
>>> damn, i meant to do that as i saw the wa
On 3/11/2016 2:55 AM, jp charras wrote:
> Le 11/03/2016 00:01, Jon Neal a écrit :
>> Oh, I should add that to prevent breaking backwards compatibility the
>> parser could just continue interpreting a missing size and thickness value
>> with the current defaults hard coded there.
>
> No problem for
Patch committed in r6616. Thanks.
On 3/4/2016 1:26 PM, Nick Østergaard wrote:
> I noticed that there is a depends missing in the msys2 the hard way
> instructions. The attached patch adds glm and the mingw toolchain.
>
> Add missing depends to the msys2 instructions
>
>
>
> __
Hi,
yes, but this is an optional setting just as now the touchpad-panning
is.
Regards,
Bernhard
On 2016-03-11 09:37, Mário Luzeiro wrote:
Hi Bernhard,
Current (stable) KiCad already has the PANing functionality on the
middle button.
The feature I added in my branch for the "pivot center" i
Hi Mario and Bernhard,
I found myself the "space bar" more useful / fast to use than the "middle
button" actually..
it is possible to pan in OSX with magic mouse / trackpad using Shift key
... that should work also for pivot I think...
Moreover many MCAD sw use middle click to PAN and change
Hi Mário,
Yes, I know that "Simplifying polygons" is most time consuming
pre-process. On Windows 64-bit freezing as JP describing do not appear.
I tried it in the bounding box of board. But now it is working correctly?!
No, middle button and spacebar should working same as until now. I
point
Hi Bernhard,
Current (stable) KiCad already has the PANing functionality on the middle
button.
The feature I added in my branch for the "pivot center" is on "middle button"
and "space bar" so I guess Apple users can use just the "space bar".
I found myself the "space bar" more useful / fast to u
On 11.03.2016 00:59, Jon Neal wrote:
Hi,
What I would like to request is that we remove the bit of code that
omits text size and thickness if they are default. This increases file
size by about 40ish chars/bytes. I think it is reasonable to still omit
bold, italic, justification, and whether t
18 matches
Mail list logo
