On Fri, Oct 2, 2015 at 8:23 AM, Wayne Stambaugh
wrote:
> On 10/1/2015 5:03 PM, Cirilo Bernardo wrote:
>
[snip]
> > Changes so far which can cause problems:
> > schematic symbols:
> > + many changed size and the location of connection points
> > + Diodes were made consistent so K is always Pin 1
On 1 October 2015 at 13:15, Chris Pavlina wrote:
> It's a right shame we don't have any standalone project archive format that
> holds *everything*. That would be *very* useful for this sort of thing, as
> well as just generally making sure projects can always be opened.
>
> I wonder if there is a
I would prefer that the orientation and scaling match footprint so the
user doesn't have to change anything by default. In other words, the
scaling is always 1 and the offsets and rotation angles are always 0.
that is exactly what I do with my 3D models in VRML and STEP for kicad
StepUp
the l
On 10/1/2015 5:03 PM, Cirilo Bernardo wrote:
> I think in general VRML models suffer from a somewhat random (0,0,0)
> reference
> and even the orientation is typically 1 of 4 common orientations. This
> is due in
> part from the habits of whoever created the model and in part from the
> modeling
>
I think in general VRML models suffer from a somewhat random (0,0,0)
reference
and even the orientation is typically 1 of 4 common orientations. This is
due in
part from the habits of whoever created the model and in part from the
modeling
software used. We will see more such problems when we have
and using FreeCAD VRML models (instead of Wings3D models) you have also
MCAD models to be used for the MCAD exporting/viewing
here there is a video of the FreeCAD VRML models and FreeCAD STEP models
that shows how KiCad is ready for MCAD world! (just now with the stable
release)
https://www.y
The only down side is that as improvements are made to the 3D models,
they would not be visible. I hope at some point in the future our 3D
models could be improved (some of material properties are very wrong)
now that FreeCAD exports vrml files that the 3D viewer can use. I would
think the demos
It's a right shame we don't have any standalone project archive format that
holds *everything*. That would be *very* useful for this sort of thing, as
well as just generally making sure projects can always be opened.
I wonder if there is any developer interest in that besides me. It's
definitely o
Why not to add 3d files (from some old revision of library) to projects
folder and use paths relative to KIPRJMOD? If demos will refer to some
special revision of library with 3d models they will break each time the
models are moved or renamed.
W dniu 01.10.2015 o 16:20, Wayne Stambaugh pisze
I just committed a fix for broken 3D model link in the interf_u demo
https://bugs.launchpad.net/kicad/+bug/1500956. While I was at it, I
looked at the rest of the demos that have board files and they are
broken (one partially) as well. Here is an opportunity for someone to
help out the project an
My test on a stock debian 7 32 bit VM (fresh install, all updates etc)
Now with the Boost 1.53 from kicad directory.
-O0 and -O1 give 12 corners
-O2 and -O3 give 0 corners
--build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.7.2 (Debian 4.7.2-5)
On 06/17/2013 11:29 AM, Dick Hollenbeck wrote:
> Jean-Pierre,
>
>
> I get a 12 point polygon with 4.7.3 regardless of optimization setting, -01,
> -02, -03
> using a *64 bit* program on linux.
>
> With some additional install I can do a 32 bit test also.
Did that install, and found that the 3
Le 17/06/2013 18:29, Dick Hollenbeck a écrit :
Jean-Pierre,
I get a 12 point polygon with 4.7.3 regardless of optimization setting, -01,
-02, -03
using a 64 bit program on linux.
With some additional install I can do a 32 bit test also.
Thanks,
Dick
It is worth only if this is not a lot
Jean-Pierre,
I get a 12 point polygon with 4.7.3 regardless of optimization setting, -01,
-02, -03
using a 64 bit program on linux.
With some additional install I can do a 32 bit test also.
Thanks,
Dick
___
Mailing list: https://launchpad.net/~kic
Le 17/06/2013 16:13, Edwin van den Oetelaar a écrit :
I downloaded this file :
https://svn.boost.org/trac/boost/attachment/ticket/7983/test_polygon_diff.cpp
And compiled it on Debian 7 (Linux debian 3.2.0-4-686-pae #1 SMP
Debian 3.2.41-2+deb7u2 i686 GNU/Linux)
With this info on the C compiler :
I downloaded this file :
https://svn.boost.org/trac/boost/attachment/ticket/7983/test_polygon_diff.cpp
And compiled it on Debian 7 (Linux debian 3.2.0-4-686-pae #1 SMP
Debian 3.2.41-2+deb7u2 i686 GNU/Linux)
With this info on the C compiler :
gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO
On Jun 17, 2013 6:21 AM, "Brian Sidebotham"
wrote:
>
> On 17 June 2013 11:59, Dick Hollenbeck wrote:
>>
>>
>> On Jun 17, 2013 5:02 AM, "Milan Horák" wrote:
>> >
>> > Hello,
>> >
>> > I am getting:
>> >
>> > g++ -Wall -O2 -I /g/boost_1_53_0 test_polygon_diff.cpp
>> >
>> > test_polygon_diff.cpp: I
On 17 June 2013 11:59, Dick Hollenbeck wrote:
>
> On Jun 17, 2013 5:02 AM, "Milan Horák" wrote:
> >
> > Hello,
> >
> > I am getting:
> >
> > g++ -Wall -O2 -I /g/boost_1_53_0 test_polygon_diff.cpp
> >
> > test_polygon_diff.cpp: In function ‘void dumpPolySet(const
> KI_POLYGON_SET&)’:
> > test_pol
On Jun 17, 2013 5:02 AM, "Milan Horák" wrote:
>
> Hello,
>
> I am getting:
>
> g++ -Wall -O2 -I /g/boost_1_53_0 test_polygon_diff.cpp
>
> test_polygon_diff.cpp: In function ‘void dumpPolySet(const
KI_POLYGON_SET&)’:
> test_polygon_diff.cpp:84:60: warning: format ‘%d’ expects argument of
type ‘int’
Hello,
gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1)
g++ -Wall -O2 -I /g/boost_1_53_0 test_polygon_diff.cpp
./polyset polygons count 1 polygon 0, corners count 12
// polyset polygons count 1
polygon 0, corners count 12
10, 10
5, 10
5, 5
5, -5
-5, -5
-5, 5
5, 5
5, 10
-1
You can change to %lu to get rid of the warning if you want, otherwise just
ignore the format warning.
Best Regards, Brian.
On 17 June 2013 11:02, Milan Horák wrote:
> Hello,
>
> I am getting:
>
> g++ -Wall -O2 -I /g/boost_1_53_0 test_polygon_diff.cpp
>
> test_polygon_diff.cpp: In function ‘vo
Hello,
I am getting:
g++ -Wall -O2 -I /g/boost_1_53_0 test_polygon_diff.cpp
test_polygon_diff.cpp: In function ‘void dumpPolySet(const
KI_POLYGON_SET&)’:
test_polygon_diff.cpp:84:60: warning: format ‘%d’ expects argument of
type ‘int’, but argument 2 has type
‘std::vector >::size_type {aka l
Jean-Pierre,
g++ -O2 test_polygon_diff.cpp
gcc version 4.7.1 20120723 [gcc-4_7-branch revision 189773] (SUSE Linux)
failure --> // polyset polygons count 1
polygon 0, corners count 5
10, 10
-10, 10
-10, -10
10, -10
10, 10
gcc version 4.7.2 20130108 [gcc-4_7-branch revision 195012
Some developers know boost::polygon has an issue when compiled with g++
4.7.2 (currently the lasted version on MinGW) using the -O2 (or more)
optimization level.
I am not 100% sure, however I am guessing this issue was also reported
on Linux.
The developer of boost::polygon asked me to test (i
On 6/15/2013 1:49 PM, jp charras wrote:
Le 15/06/2013 16:28, Wayne Stambaugh a écrit :
On 6/15/2013 4:07 AM, jp charras wrote:
Le 14/06/2013 21:08, Wayne Stambaugh a écrit :
I may have found a issue with an exception causing Pcbnew to crash on
release builds on Windows. I would appreciate if
Le 15/06/2013 16:28, Wayne Stambaugh a écrit :
On 6/15/2013 4:07 AM, jp charras wrote:
Le 14/06/2013 21:08, Wayne Stambaugh a écrit :
I may have found a issue with an exception causing Pcbnew to crash on
release builds on Windows. I would appreciate if a some of you Windows
users would run a s
On 6/15/2013 4:07 AM, jp charras wrote:
Le 14/06/2013 21:08, Wayne Stambaugh a écrit :
I may have found a issue with an exception causing Pcbnew to crash on
release builds on Windows. I would appreciate if a some of you Windows
users would run a simple test and let me know if you encounter any
Le 14/06/2013 21:08, Wayne Stambaugh a écrit :
I may have found a issue with an exception causing Pcbnew to crash on
release builds on Windows. I would appreciate if a some of you Windows
users would run a simple test and let me know if you encounter any
problems. Open Pcbnew and load any board
On 06/14/2013 05:10 PM, Wayne Stambaugh wrote:
> On 6/14/2013 5:36 PM, Dick Hollenbeck wrote:
>> On 06/14/2013 04:13 PM, Wayne Stambaugh wrote:
>>> On 6/14/2013 4:25 PM, Brian Sidebotham wrote:
On a release build with Winbuilder (Statically linked wxWidgets 2.9.4)
there is an IO_ERROR com
On 6/14/2013 5:36 PM, Dick Hollenbeck wrote:
On 06/14/2013 04:13 PM, Wayne Stambaugh wrote:
On 6/14/2013 4:25 PM, Brian Sidebotham wrote:
On a release build with Winbuilder (Statically linked wxWidgets 2.9.4)
there is an IO_ERROR complaint. doing what you describe. I've got no
runtime errors.
On 06/14/2013 03:25 PM, Brian Sidebotham wrote:
> On a release build with Winbuilder (Statically linked wxWidgets 2.9.4) there
> is an
> IO_ERROR complaint. doing what you describe. I've got no runtime errors.
>
> I guess your wxWidgets and KiCad build are both built with the same (or at
> least
On 06/14/2013 04:13 PM, Wayne Stambaugh wrote:
> On 6/14/2013 4:25 PM, Brian Sidebotham wrote:
>> On a release build with Winbuilder (Statically linked wxWidgets 2.9.4)
>> there is an IO_ERROR complaint. doing what you describe. I've got no
>> runtime errors.
>
> Brian,
>
> It looks like the prob
On 6/14/2013 4:25 PM, Brian Sidebotham wrote:
On a release build with Winbuilder (Statically linked wxWidgets 2.9.4)
there is an IO_ERROR complaint. doing what you describe. I've got no
runtime errors.
Brian,
It looks like the problem is on my end. Maybe it's a static vs. DLL
problem or my w
On a release build with Winbuilder (Statically linked wxWidgets 2.9.4)
there is an IO_ERROR complaint. doing what you describe. I've got no
runtime errors.
I guess your wxWidgets and KiCad build are both built with the same (or at
least compatible) compilers? There were some incompatibilities betw
I may have found a issue with an exception causing Pcbnew to crash on
release builds on Windows. I would appreciate if a some of you Windows
users would run a simple test and let me know if you encounter any
problems. Open Pcbnew and load any board. Open the netlist dialog and
enter an inval
35 matches
Mail list logo
