Re: [Kicad-developers] 3D refactor

[Nick Østergaard]

Hi All

Adam has prepared some OS X builds of the 3d_intial_merge branch on
http://downloads.kicad-pcb.org/osx/testing/3d_initial_merge/

So OS X users, please test this. When that is done, then it has been
tested on all three platforms.

2016-03-03 7:59 GMT+01:00 Cirilo Bernardo :
> Hi Wayne,
>
>  I believe Bernhard has sorted out the OSX issues; others have compiled and
> installed with Bernhard's changes and haven't had any problems.
>
>  I haven't had any problems when I installed on MSWin via the installer
> package which nickoe built on Jenkins. If you're having problems building
> and installing from source we'd need to have a closer look at the steps
> you're going through to get kicad up and running.
>
>  The 3D refactor code was last synced with r6601 but once we sort out the
> install issues on MSWin it should be trivial to sync.
>
> - Cirilo
>
>
> On Thu, Feb 25, 2016 at 4:51 AM, Wayne Stambaugh 
> wrote:
>>
>> Thanks Bernhard,
>>
>> Before I committed the 3D refactor, I was going to ask our package devs
>> to take a look at it due to the new 3D model plugins.  I would like to
>> get this correct before I commit it.  What's the status on windows.
>> I've built and installed from source and that works find but I'm
>> guessing our installers will need to be changed to accommodate this.
>> Once we have the install issues sorted out, I'll commit it.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 2/24/2016 12:26 PM, Bernhard Stegmaier wrote:
>> > Hi,
>> >
>> > I just tried on OS X and plugin handling doesn’t seem to be OK.
>> > At least, “make install” does directly (try to) install them to
>> > “/Applications/…” which is completely wrong (and also maybe the case why
>> > my built binary doesn’t find them?). Also, the path itself under
>> > SharedSupport I guess isn’t right.
>> >
>> > It also install this here
>> > bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
>> > total 464
>> > drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
>> > drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
>> > -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17
>> > libkicad_3dsg..0.0.dylib
>> > lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17 libkicad_3dsg.dylib
>> > -> libkicad_3dsg..0.0.dylib
>> > which doesn’t look right, what is it good for?
>> >
>> > If you like, I can have a look and try to fix this.
>> >
>> >
>> > Regards,
>> > Bernhard
>> >
>> >> On 23.02.2016, at 22:21, Cirilo Bernardo > >> > wrote:
>> >>
>> >>
>> >>
>> >> On Tue, Feb 23, 2016 at 7:37 PM, jp charras > >> > wrote:
>> >>
>> >> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
>> >> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh
>> >> >
>> >> > wrote:
>> >> >
>> >> >> Cirilo,
>> >> >>
>> >> >> I have one last change request that I missed in my previous
>> >> review.
>> >> >> Please change your debugging output method.  Windows apps have
>> >> no
>> >> >> concept of stdout even when run from the command line.
>> >> wxLogTrace is
>> >> >> the preferred method for debugging output.  It solves two
>> >> problems.  The
>> >> >> debugging strings are redirected to the correct output on all
>> >> supported
>> >> >> platforms and the debugging output is turned off by default.
>> >> Turning on
>> >> >> the debugging output is as simple as:
>> >> >>
>> >> >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
>> >> >>
>> >> >> The is handy so I don't have to sift through everyone's
>> >> debugging output
>> >> >> to find what I'm looking for.  You just need to pick a unique
>> >> string not
>> >> >> used by any other kicad wxLogTrace calls to enable tracing of
>> >> your
>> >> >> debugging output.
>> >> >>
>> >> >>
>> >> > The 3d_initial_merge branch has been updated to use wxLogTrace;
>> >> > it has also been synchronized to the main branch r6527.  The
>> >> latest
>> >> > revision for the 3d_initial_merge branch is r6527. The branch
>> >> builds
>> >> > successfully and I have tested the previewer with various VRML1/2
>> >> and
>> >> > X3D models.
>> >> >
>> >> > - Cirilo
>> >>
>> >> Thanks, Cirilo.
>> >> Very good work.
>> >>
>> >> At least on Windows, 3d_plugin_manager.cpp is missing the line:
>> >> #include 
>> >>
>> >> Without this include, it does not compile.
>> >>
>> >> --
>> >> Jean-Pierre CHARRAS
>> >>
>> >> ___
>> >> Mailing list: https://launchpad.net/~kicad-developers
>> >> Post to : kicad-developers@lists.launchpad.net
>> >> 
>> >> Unsubscribe : https://launchpad.net/~kicad-developers
>> >> More help   : https://help.launchpad.net/ListHelp
>> >>
>> >>
>> >> 

Re: [Kicad-developers] 3D refactor

[Mário Luzeiro]

Hi Bernhard,

The model (pre-)viewer was a quick interface I made, it is work in progress.. 
we can improve it latter.
However, 
as my proposal, I believe in future this model viewer should be replaced with a 
footprint preview.
I think we can have a model viewer when you click and select a model, and when 
you are editing? you will show the footprint...

So that will be very helpful to align models in the footprint.


> Zooming is OK, but doesn’t yet respect touchpad-panning setting (always zooms 
> on mouse-wheel).
I am not sure, I believe it dont have your latest contributions.

This should be what you are looking for:
http://bazaar.launchpad.net/~cirilo-bernardo/kicad/3d_initial_merge/view/head:/3d-viewer/3d_model_viewer/c3d_model_viewer.cpp#L325


> Should panning work in preview (with shift/ctrl-mousewheel)?

It should not.
I found that it may not be useful for the preview.. since you can lost the 
model from the screen and there is no button to reset the view. So in this case 
only rotation of the model works.


> Does it make more sense to check (and probably fix/implement in) Marios 
> branch?

I will want that updates! :) but you can first do it in Cirilo branch.. provide 
that he update his other branch and I will merge back to my branch.

Thanks
Mario Luzeiro

From: Kicad-developers 
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of 
Bernhard Stegmaier [stegma...@sw-systems.de]
Sent: 03 March 2016 17:55
To: Cirilo Bernardo
Cc: KiCad Developers
Subject: Re: [Kicad-developers] 3D refactor

Hi,

just compiled current version and it looks fine to me for OS X.

Rotation of preview is fine.

Zooming is OK, but doesn’t yet respect touchpad-panning setting (always zooms 
on mouse-wheel).
I didn’t test if pinch-to-zoom works.
Auto zoom is pretty decent, so this also can be fixed after merging.

Should panning work in preview (with shift/ctrl-mousewheel)?
It didn’t for me, but I also guess this is simply not needed for preview…

@Cirilo/Mario:
I can try to look into the touchpad-panning and pinch-to-zoom stuff on the 
weekend, but that shouldn’t block merging it.
If I remember correctly this is already Marios new code in preview?
Does it make more sense to check (and probably fix/implement in) Marios branch?


Regards,
Bernhard
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Bernhard Stegmaier]

Hi,

just compiled current version and it looks fine to me for OS X.

Rotation of preview is fine.

Zooming is OK, but doesn’t yet respect touchpad-panning setting (always zooms 
on mouse-wheel).
I didn’t test if pinch-to-zoom works.
Auto zoom is pretty decent, so this also can be fixed after merging.

Should panning work in preview (with shift/ctrl-mousewheel)?
It didn’t for me, but I also guess this is simply not needed for preview…

@Cirilo/Mario: 
I can try to look into the touchpad-panning and pinch-to-zoom stuff on the 
weekend, but that shouldn’t block merging it. 
If I remember correctly this is already Marios new code in preview?
Does it make more sense to check (and probably fix/implement in) Marios branch?


Regards,
Bernhard

> On 03.03.2016, at 07:59, Cirilo Bernardo  wrote:
> 
> Hi Wayne,
> 
>  I believe Bernhard has sorted out the OSX issues; others have compiled and 
> installed with Bernhard's changes and haven't had any problems.
> 
>  I haven't had any problems when I installed on MSWin via the installer 
> package which nickoe built on Jenkins. If you're having problems building and 
> installing from source we'd need to have a closer look at the steps you're 
> going through to get kicad up and running.
> 
>  The 3D refactor code was last synced with r6601 but once we sort out the 
> install issues on MSWin it should be trivial to sync.
> 
> - Cirilo
> 
> 
> On Thu, Feb 25, 2016 at 4:51 AM, Wayne Stambaugh  > wrote:
> Thanks Bernhard,
> 
> Before I committed the 3D refactor, I was going to ask our package devs
> to take a look at it due to the new 3D model plugins.  I would like to
> get this correct before I commit it.  What's the status on windows.
> I've built and installed from source and that works find but I'm
> guessing our installers will need to be changed to accommodate this.
> Once we have the install issues sorted out, I'll commit it.
> 
> Cheers,
> 
> Wayne
> 
> On 2/24/2016 12:26 PM, Bernhard Stegmaier wrote:
> > Hi,
> >
> > I just tried on OS X and plugin handling doesn’t seem to be OK.
> > At least, “make install” does directly (try to) install them to
> > “/Applications/…” which is completely wrong (and also maybe the case why
> > my built binary doesn’t find them?). Also, the path itself under
> > SharedSupport I guess isn’t right.
> >
> > It also install this here
> > bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
> > total 464
> > drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
> > drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
> > -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17
> > libkicad_3dsg..0.0.dylib
> > lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17 libkicad_3dsg.dylib
> > -> libkicad_3dsg..0.0.dylib
> > which doesn’t look right, what is it good for?
> >
> > If you like, I can have a look and try to fix this.
> >
> >
> > Regards,
> > Bernhard
> >
> >> On 23.02.2016, at 22:21, Cirilo Bernardo  >> 
> >> >> 
> >> wrote:
> >>
> >>
> >>
> >> On Tue, Feb 23, 2016 at 7:37 PM, jp charras  >> 
> >> >> wrote:
> >>
> >> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
> >> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh 
> >>  
> >> >>
> >> > wrote:
> >> >
> >> >> Cirilo,
> >> >>
> >> >> I have one last change request that I missed in my previous review.
> >> >> Please change your debugging output method.  Windows apps have no
> >> >> concept of stdout even when run from the command line.  wxLogTrace 
> >> is
> >> >> the preferred method for debugging output.  It solves two problems. 
> >>  The
> >> >> debugging strings are redirected to the correct output on all 
> >> supported
> >> >> platforms and the debugging output is turned off by default.  
> >> Turning on
> >> >> the debugging output is as simple as:
> >> >>
> >> >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
> >> >>
> >> >> The is handy so I don't have to sift through everyone's debugging 
> >> output
> >> >> to find what I'm looking for.  You just need to pick a unique 
> >> string not
> >> >> used by any other kicad wxLogTrace calls to enable tracing of your
> >> >> debugging output.
> >> >>
> >> >>
> >> > The 3d_initial_merge branch has been updated to use wxLogTrace;
> >> > it has also been synchronized to the main branch r6527.  The latest
> >> > revision for the 3d_initial_merge branch is r6527. The branch builds
> >> > successfully and I have tested the previewer with various VRML1/2 and
> >> > X3D models.
> >> >
> >>

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

Hi Wayne,

 I believe Bernhard has sorted out the OSX issues; others have compiled and
installed with Bernhard's changes and haven't had any problems.

 I haven't had any problems when I installed on MSWin via the installer
package which nickoe built on Jenkins. If you're having problems building
and installing from source we'd need to have a closer look at the steps
you're going through to get kicad up and running.

 The 3D refactor code was last synced with r6601 but once we sort out the
install issues on MSWin it should be trivial to sync.

- Cirilo


On Thu, Feb 25, 2016 at 4:51 AM, Wayne Stambaugh 
wrote:

> Thanks Bernhard,
>
> Before I committed the 3D refactor, I was going to ask our package devs
> to take a look at it due to the new 3D model plugins.  I would like to
> get this correct before I commit it.  What's the status on windows.
> I've built and installed from source and that works find but I'm
> guessing our installers will need to be changed to accommodate this.
> Once we have the install issues sorted out, I'll commit it.
>
> Cheers,
>
> Wayne
>
> On 2/24/2016 12:26 PM, Bernhard Stegmaier wrote:
> > Hi,
> >
> > I just tried on OS X and plugin handling doesn’t seem to be OK.
> > At least, “make install” does directly (try to) install them to
> > “/Applications/…” which is completely wrong (and also maybe the case why
> > my built binary doesn’t find them?). Also, the path itself under
> > SharedSupport I guess isn’t right.
> >
> > It also install this here
> > bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
> > total 464
> > drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
> > drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
> > -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17
> > libkicad_3dsg..0.0.dylib
> > lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17 libkicad_3dsg.dylib
> > -> libkicad_3dsg..0.0.dylib
> > which doesn’t look right, what is it good for?
> >
> > If you like, I can have a look and try to fix this.
> >
> >
> > Regards,
> > Bernhard
> >
> >> On 23.02.2016, at 22:21, Cirilo Bernardo  >> > wrote:
> >>
> >>
> >>
> >> On Tue, Feb 23, 2016 at 7:37 PM, jp charras  >> > wrote:
> >>
> >> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
> >> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh <
> stambau...@gmail.com >
> >> > wrote:
> >> >
> >> >> Cirilo,
> >> >>
> >> >> I have one last change request that I missed in my previous
> review.
> >> >> Please change your debugging output method.  Windows apps have no
> >> >> concept of stdout even when run from the command line.
> wxLogTrace is
> >> >> the preferred method for debugging output.  It solves two
> problems.  The
> >> >> debugging strings are redirected to the correct output on all
> supported
> >> >> platforms and the debugging output is turned off by default.
> Turning on
> >> >> the debugging output is as simple as:
> >> >>
> >> >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
> >> >>
> >> >> The is handy so I don't have to sift through everyone's
> debugging output
> >> >> to find what I'm looking for.  You just need to pick a unique
> string not
> >> >> used by any other kicad wxLogTrace calls to enable tracing of
> your
> >> >> debugging output.
> >> >>
> >> >>
> >> > The 3d_initial_merge branch has been updated to use wxLogTrace;
> >> > it has also been synchronized to the main branch r6527.  The
> latest
> >> > revision for the 3d_initial_merge branch is r6527. The branch
> builds
> >> > successfully and I have tested the previewer with various VRML1/2
> and
> >> > X3D models.
> >> >
> >> > - Cirilo
> >>
> >> Thanks, Cirilo.
> >> Very good work.
> >>
> >> At least on Windows, 3d_plugin_manager.cpp is missing the line:
> >> #include 
> >>
> >> Without this include, it does not compile.
> >>
> >> --
> >> Jean-Pierre CHARRAS
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> 
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> >>
> >> Thanks Jean-Pierre,
> >>
> >>  I have added the header and checked that it builds on Windows (W7-64
> >> bit).
> >>
> >> - Cirilo
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> 
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >
> >
> >
> > 

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

Hi Simon,

For the scaling, some people do like to have independent scaling of XYZ.
One example I can think of are users who use a generic box to represent
most components and simply change the X,Y,Z scale to give a rough model
of each component.

Historically the orientation data was entered as Scale, Offset, Rotation;
I don't see a need to change that order so unless the chief devs believe
it would be an improvement to the UI, I wouldn't make such a change.

- Cirilo

On Wed, Mar 2, 2016 at 6:41 PM, Simon Wells  wrote:

> Hey Cirilo,
>
> The performance is much better for me now, and yeah touchpad scroll is
> zoom. Has anyone actually run into a situation where they need to
> scale differently in each axis? as it seems thats one setting that
> could be just made into a single scale amount.
>
> To avoid any confusion is it possible to put xyz on the RGB thing in
> the bottom left corner to avoid confusion as to offset and rotation
> axis?
>
> apart from that its looking good (and thanks for removing the sunken
> border) :)
>
>
>
> On Wed, Mar 2, 2016 at 3:51 PM, Cirilo Bernardo
>  wrote:
> > Thanks Wayne,
> >
> >  I had a look at the code and part of the problem seems to be that
> > the wxGLCanvas derived class wasn't calling event.Skip() on the
> > mouse buttons. I just added event.Skip() and the 3D frame now
> > gets the focus upon clicking. I decided against the ENTER_WINDOW
> > event since that could interfere with the GUI flow by stealing focus
> > when the user really doesn't want that to happen.
> >
> > - Cirilo
> >
> >
> > On Wed, Mar 2, 2016 at 11:15 AM, Wayne Stambaugh 
> > wrote:
> >>
> >> Take a look at the wxEVT_ENTER_WINDOW event.  You can set the canvas
> >> focus on this event.  This event should fire when the mouse enters the
> >> canvas so it should be handled there unless the parent frame window
> >> doesn't pass it down to the child canvas window.
> >>
> >> On 3/1/2016 5:24 PM, Cirilo Bernardo wrote:
> >> > Thanks Bernhard,
> >> >
> >> >  I found on MSWin after adding the SetFocus() as Mario suggested,
> >> > if I click somewhere else the wxGLCanvas loses focus again and
> >> > the rotate etc. no longer works until I use [tab] to set focus to the
> >> > window.
> >> >
> >> >  Are there any GUI experts out there who have some idea how we
> >> > can ensure that the wxGLCanvas frame has focus when the mouse
> >> > is above it?
> >> >
> >> > - Cirilo
> >> >
> >> >
> >> > On Wed, Mar 2, 2016 at 8:03 AM, Bernhard Stegmaier
> >> > > wrote:
> >> >
> >> > I’ll check zoom on OS X hopefully tomorrow.
> >> > I can tell that rotating the preview does work as expected.
> >> > And if I remember correctly, I did accidentally zoom once, but I
> >> > didn’t pay attention how I did it and if it was as it should be.
> >> >
> >> >> On 01 Mar 2016, at 21:52, Cirilo Bernardo
> >> >> >
> >> >> wrote:
> >> >>
> >> >> Thanks Mario,
> >> >>
> >> >>  I'll test that on MSWin soon; hopefully that works now.
> >> >>
> >> >> - Cirilo
> >> >>
> >> >> On Tue, Mar 1, 2016 at 9:03 PM, Mário Luzeiro  >> >> > wrote:
> >> >>
> >> >> > I'd also appreciate some help from anyone on the zoom
> >> >> function for the
> >> >> > 3D preview pane. The zoom works on Linux when using the
> mouse
> >> >> scroll
> >> >> > wheel but in MSWin I can only change the viewing angle, not
> >> >> the zoom. On
> >> >> > OSX I have no idea what the status is for zooming the
> model.
> >> >>
> >> >> Hi Cirilo,
> >> >>
> >> >> Looks like it was an old know wxWidgets issue, I fixed at:
> >> >>
> >> >>
> http://bazaar.launchpad.net/~mrluzeiro/kicad/kicad_new3d-viewer/revision/5897
> >> >>
> >> >> I found it here:
> >> >>
> >> >>
> https://github.com/KiCad/kicad-source-mirror/blob/a9427f899926155e48cab93187415710abc5438a/3d-viewer/3d_frame.cpp#L220
> >> >>
> >> >> In any case, in my windows laptop, the touchpad is not able
> to
> >> >> scrool.. but. I think it is some particularity of this
> >> >> windows/laptop...
> >> >> I tested with a mouse and it worked.
> >> >>
> >> >> Mario Luzeiro
> >> >>
> >> >>
> >> >> ___
> >> >> Mailing list: https://launchpad.net/~kicad-developers
> >> >> Post to : kicad-developers@lists.launchpad.net
> >> >> 
> >> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> >> More help   : https://help.launchpad.net/ListHelp
> >> >
> >> >
> >> >
> >> >
> >> > ___
> >> > Mailing list: https://launchpad.net/~kicad-developers
> >> > Post to : kicad-developers@lists.launchpad.net
> >> > Unsubscribe 

Re: [Kicad-developers] 3D refactor

[Simon Wells]

Hey Cirilo,

The performance is much better for me now, and yeah touchpad scroll is
zoom. Has anyone actually run into a situation where they need to
scale differently in each axis? as it seems thats one setting that
could be just made into a single scale amount.

To avoid any confusion is it possible to put xyz on the RGB thing in
the bottom left corner to avoid confusion as to offset and rotation
axis?

apart from that its looking good (and thanks for removing the sunken border) :)



On Wed, Mar 2, 2016 at 3:51 PM, Cirilo Bernardo
 wrote:
> Thanks Wayne,
>
>  I had a look at the code and part of the problem seems to be that
> the wxGLCanvas derived class wasn't calling event.Skip() on the
> mouse buttons. I just added event.Skip() and the 3D frame now
> gets the focus upon clicking. I decided against the ENTER_WINDOW
> event since that could interfere with the GUI flow by stealing focus
> when the user really doesn't want that to happen.
>
> - Cirilo
>
>
> On Wed, Mar 2, 2016 at 11:15 AM, Wayne Stambaugh 
> wrote:
>>
>> Take a look at the wxEVT_ENTER_WINDOW event.  You can set the canvas
>> focus on this event.  This event should fire when the mouse enters the
>> canvas so it should be handled there unless the parent frame window
>> doesn't pass it down to the child canvas window.
>>
>> On 3/1/2016 5:24 PM, Cirilo Bernardo wrote:
>> > Thanks Bernhard,
>> >
>> >  I found on MSWin after adding the SetFocus() as Mario suggested,
>> > if I click somewhere else the wxGLCanvas loses focus again and
>> > the rotate etc. no longer works until I use [tab] to set focus to the
>> > window.
>> >
>> >  Are there any GUI experts out there who have some idea how we
>> > can ensure that the wxGLCanvas frame has focus when the mouse
>> > is above it?
>> >
>> > - Cirilo
>> >
>> >
>> > On Wed, Mar 2, 2016 at 8:03 AM, Bernhard Stegmaier
>> > > wrote:
>> >
>> > I’ll check zoom on OS X hopefully tomorrow.
>> > I can tell that rotating the preview does work as expected.
>> > And if I remember correctly, I did accidentally zoom once, but I
>> > didn’t pay attention how I did it and if it was as it should be.
>> >
>> >> On 01 Mar 2016, at 21:52, Cirilo Bernardo
>> >> >
>> >> wrote:
>> >>
>> >> Thanks Mario,
>> >>
>> >>  I'll test that on MSWin soon; hopefully that works now.
>> >>
>> >> - Cirilo
>> >>
>> >> On Tue, Mar 1, 2016 at 9:03 PM, Mário Luzeiro > >> > wrote:
>> >>
>> >> > I'd also appreciate some help from anyone on the zoom
>> >> function for the
>> >> > 3D preview pane. The zoom works on Linux when using the mouse
>> >> scroll
>> >> > wheel but in MSWin I can only change the viewing angle, not
>> >> the zoom. On
>> >> > OSX I have no idea what the status is for zooming the model.
>> >>
>> >> Hi Cirilo,
>> >>
>> >> Looks like it was an old know wxWidgets issue, I fixed at:
>> >>
>> >> http://bazaar.launchpad.net/~mrluzeiro/kicad/kicad_new3d-viewer/revision/5897
>> >>
>> >> I found it here:
>> >>
>> >> https://github.com/KiCad/kicad-source-mirror/blob/a9427f899926155e48cab93187415710abc5438a/3d-viewer/3d_frame.cpp#L220
>> >>
>> >> In any case, in my windows laptop, the touchpad is not able to
>> >> scrool.. but. I think it is some particularity of this
>> >> windows/laptop...
>> >> I tested with a mouse and it worked.
>> >>
>> >> Mario Luzeiro
>> >>
>> >>
>> >> ___
>> >> Mailing list: https://launchpad.net/~kicad-developers
>> >> Post to : kicad-developers@lists.launchpad.net
>> >> 
>> >> Unsubscribe : https://launchpad.net/~kicad-developers
>> >> More help   : https://help.launchpad.net/ListHelp
>> >
>> >
>> >
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~kicad-developers
>> > Post to : kicad-developers@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : 

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

Thanks Wayne,

 I had a look at the code and part of the problem seems to be that
the wxGLCanvas derived class wasn't calling event.Skip() on the
mouse buttons. I just added event.Skip() and the 3D frame now
gets the focus upon clicking. I decided against the ENTER_WINDOW
event since that could interfere with the GUI flow by stealing focus
when the user really doesn't want that to happen.

- Cirilo


On Wed, Mar 2, 2016 at 11:15 AM, Wayne Stambaugh 
wrote:

> Take a look at the wxEVT_ENTER_WINDOW event.  You can set the canvas
> focus on this event.  This event should fire when the mouse enters the
> canvas so it should be handled there unless the parent frame window
> doesn't pass it down to the child canvas window.
>
> On 3/1/2016 5:24 PM, Cirilo Bernardo wrote:
> > Thanks Bernhard,
> >
> >  I found on MSWin after adding the SetFocus() as Mario suggested,
> > if I click somewhere else the wxGLCanvas loses focus again and
> > the rotate etc. no longer works until I use [tab] to set focus to the
> > window.
> >
> >  Are there any GUI experts out there who have some idea how we
> > can ensure that the wxGLCanvas frame has focus when the mouse
> > is above it?
> >
> > - Cirilo
> >
> >
> > On Wed, Mar 2, 2016 at 8:03 AM, Bernhard Stegmaier
> > > wrote:
> >
> > I’ll check zoom on OS X hopefully tomorrow.
> > I can tell that rotating the preview does work as expected.
> > And if I remember correctly, I did accidentally zoom once, but I
> > didn’t pay attention how I did it and if it was as it should be.
> >
> >> On 01 Mar 2016, at 21:52, Cirilo Bernardo
> >> >
> wrote:
> >>
> >> Thanks Mario,
> >>
> >>  I'll test that on MSWin soon; hopefully that works now.
> >>
> >> - Cirilo
> >>
> >> On Tue, Mar 1, 2016 at 9:03 PM, Mário Luzeiro  >> > wrote:
> >>
> >> > I'd also appreciate some help from anyone on the zoom
> function for the
> >> > 3D preview pane. The zoom works on Linux when using the mouse
> scroll
> >> > wheel but in MSWin I can only change the viewing angle, not
> the zoom. On
> >> > OSX I have no idea what the status is for zooming the model.
> >>
> >> Hi Cirilo,
> >>
> >> Looks like it was an old know wxWidgets issue, I fixed at:
> >>
> http://bazaar.launchpad.net/~mrluzeiro/kicad/kicad_new3d-viewer/revision/5897
> >>
> >> I found it here:
> >>
> https://github.com/KiCad/kicad-source-mirror/blob/a9427f899926155e48cab93187415710abc5438a/3d-viewer/3d_frame.cpp#L220
> >>
> >> In any case, in my windows laptop, the touchpad is not able to
> >> scrool.. but. I think it is some particularity of this
> >> windows/laptop...
> >> I tested with a mouse and it worked.
> >>
> >> Mario Luzeiro
> >>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> 
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Simon Wells]

i could use touchpad scroll (which was zoom i think the performance
was so terrible that i am unsure whether it was pinch or scroll)  in
the preview window

But yeah the performance is worse for me than cairo

On Wed, Mar 2, 2016 at 1:15 PM, Wayne Stambaugh  wrote:
> Take a look at the wxEVT_ENTER_WINDOW event.  You can set the canvas
> focus on this event.  This event should fire when the mouse enters the
> canvas so it should be handled there unless the parent frame window
> doesn't pass it down to the child canvas window.
>
> On 3/1/2016 5:24 PM, Cirilo Bernardo wrote:
>> Thanks Bernhard,
>>
>>  I found on MSWin after adding the SetFocus() as Mario suggested,
>> if I click somewhere else the wxGLCanvas loses focus again and
>> the rotate etc. no longer works until I use [tab] to set focus to the
>> window.
>>
>>  Are there any GUI experts out there who have some idea how we
>> can ensure that the wxGLCanvas frame has focus when the mouse
>> is above it?
>>
>> - Cirilo
>>
>>
>> On Wed, Mar 2, 2016 at 8:03 AM, Bernhard Stegmaier
>> > wrote:
>>
>> I’ll check zoom on OS X hopefully tomorrow.
>> I can tell that rotating the preview does work as expected.
>> And if I remember correctly, I did accidentally zoom once, but I
>> didn’t pay attention how I did it and if it was as it should be.
>>
>>> On 01 Mar 2016, at 21:52, Cirilo Bernardo
>>> > wrote:
>>>
>>> Thanks Mario,
>>>
>>>  I'll test that on MSWin soon; hopefully that works now.
>>>
>>> - Cirilo
>>>
>>> On Tue, Mar 1, 2016 at 9:03 PM, Mário Luzeiro >> > wrote:
>>>
>>> > I'd also appreciate some help from anyone on the zoom function 
>>> for the
>>> > 3D preview pane. The zoom works on Linux when using the mouse 
>>> scroll
>>> > wheel but in MSWin I can only change the viewing angle, not the 
>>> zoom. On
>>> > OSX I have no idea what the status is for zooming the model.
>>>
>>> Hi Cirilo,
>>>
>>> Looks like it was an old know wxWidgets issue, I fixed at:
>>> 
>>> http://bazaar.launchpad.net/~mrluzeiro/kicad/kicad_new3d-viewer/revision/5897
>>>
>>> I found it here:
>>> 
>>> https://github.com/KiCad/kicad-source-mirror/blob/a9427f899926155e48cab93187415710abc5438a/3d-viewer/3d_frame.cpp#L220
>>>
>>> In any case, in my windows laptop, the touchpad is not able to
>>> scrool.. but. I think it is some particularity of this
>>> windows/laptop...
>>> I tested with a mouse and it worked.
>>>
>>> Mario Luzeiro
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> 
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Wayne Stambaugh]

Take a look at the wxEVT_ENTER_WINDOW event.  You can set the canvas
focus on this event.  This event should fire when the mouse enters the
canvas so it should be handled there unless the parent frame window
doesn't pass it down to the child canvas window.

On 3/1/2016 5:24 PM, Cirilo Bernardo wrote:
> Thanks Bernhard,
> 
>  I found on MSWin after adding the SetFocus() as Mario suggested,
> if I click somewhere else the wxGLCanvas loses focus again and
> the rotate etc. no longer works until I use [tab] to set focus to the
> window.
> 
>  Are there any GUI experts out there who have some idea how we
> can ensure that the wxGLCanvas frame has focus when the mouse
> is above it?
> 
> - Cirilo
> 
> 
> On Wed, Mar 2, 2016 at 8:03 AM, Bernhard Stegmaier
> > wrote:
> 
> I’ll check zoom on OS X hopefully tomorrow.
> I can tell that rotating the preview does work as expected.
> And if I remember correctly, I did accidentally zoom once, but I
> didn’t pay attention how I did it and if it was as it should be.
> 
>> On 01 Mar 2016, at 21:52, Cirilo Bernardo
>> > wrote:
>>
>> Thanks Mario,
>>
>>  I'll test that on MSWin soon; hopefully that works now.
>>
>> - Cirilo
>>
>> On Tue, Mar 1, 2016 at 9:03 PM, Mário Luzeiro > > wrote:
>>
>> > I'd also appreciate some help from anyone on the zoom function for 
>> the
>> > 3D preview pane. The zoom works on Linux when using the mouse 
>> scroll
>> > wheel but in MSWin I can only change the viewing angle, not the 
>> zoom. On
>> > OSX I have no idea what the status is for zooming the model.
>>
>> Hi Cirilo,
>>
>> Looks like it was an old know wxWidgets issue, I fixed at:
>> 
>> http://bazaar.launchpad.net/~mrluzeiro/kicad/kicad_new3d-viewer/revision/5897
>>
>> I found it here:
>> 
>> https://github.com/KiCad/kicad-source-mirror/blob/a9427f899926155e48cab93187415710abc5438a/3d-viewer/3d_frame.cpp#L220
>>
>> In any case, in my windows laptop, the touchpad is not able to
>> scrool.. but. I think it is some particularity of this
>> windows/laptop...
>> I tested with a mouse and it worked.
>>
>> Mario Luzeiro
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> 
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

Thanks Bernhard,

 I found on MSWin after adding the SetFocus() as Mario suggested,
if I click somewhere else the wxGLCanvas loses focus again and
the rotate etc. no longer works until I use [tab] to set focus to the
window.

 Are there any GUI experts out there who have some idea how we
can ensure that the wxGLCanvas frame has focus when the mouse
is above it?

- Cirilo


On Wed, Mar 2, 2016 at 8:03 AM, Bernhard Stegmaier 
wrote:

> I’ll check zoom on OS X hopefully tomorrow.
> I can tell that rotating the preview does work as expected.
> And if I remember correctly, I did accidentally zoom once, but I didn’t
> pay attention how I did it and if it was as it should be.
>
> On 01 Mar 2016, at 21:52, Cirilo Bernardo 
> wrote:
>
> Thanks Mario,
>
>  I'll test that on MSWin soon; hopefully that works now.
>
> - Cirilo
>
> On Tue, Mar 1, 2016 at 9:03 PM, Mário Luzeiro  wrote:
>
>> > I'd also appreciate some help from anyone on the zoom function for the
>> > 3D preview pane. The zoom works on Linux when using the mouse scroll
>> > wheel but in MSWin I can only change the viewing angle, not the zoom. On
>> > OSX I have no idea what the status is for zooming the model.
>>
>> Hi Cirilo,
>>
>> Looks like it was an old know wxWidgets issue, I fixed at:
>>
>> http://bazaar.launchpad.net/~mrluzeiro/kicad/kicad_new3d-viewer/revision/5897
>>
>> I found it here:
>>
>> https://github.com/KiCad/kicad-source-mirror/blob/a9427f899926155e48cab93187415710abc5438a/3d-viewer/3d_frame.cpp#L220
>>
>> In any case, in my windows laptop, the touchpad is not able to scrool..
>> but. I think it is some particularity of this windows/laptop...
>> I tested with a mouse and it worked.
>>
>> Mario Luzeiro
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Bernhard Stegmaier]

I’ll check zoom on OS X hopefully tomorrow.
I can tell that rotating the preview does work as expected.
And if I remember correctly, I did accidentally zoom once, but I didn’t pay 
attention how I did it and if it was as it should be.

> On 01 Mar 2016, at 21:52, Cirilo Bernardo  wrote:
> 
> Thanks Mario,
> 
>  I'll test that on MSWin soon; hopefully that works now.
> 
> - Cirilo
> 
> On Tue, Mar 1, 2016 at 9:03 PM, Mário Luzeiro  > wrote:
> > I'd also appreciate some help from anyone on the zoom function for the
> > 3D preview pane. The zoom works on Linux when using the mouse scroll
> > wheel but in MSWin I can only change the viewing angle, not the zoom. On
> > OSX I have no idea what the status is for zooming the model.
> 
> Hi Cirilo,
> 
> Looks like it was an old know wxWidgets issue, I fixed at:
> http://bazaar.launchpad.net/~mrluzeiro/kicad/kicad_new3d-viewer/revision/5897 
> 
> 
> I found it here:
> https://github.com/KiCad/kicad-source-mirror/blob/a9427f899926155e48cab93187415710abc5438a/3d-viewer/3d_frame.cpp#L220
>  
> 
> 
> In any case, in my windows laptop, the touchpad is not able to scrool.. but. 
> I think it is some particularity of this windows/laptop...
> I tested with a mouse and it worked.
> 
> Mario Luzeiro
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

Thanks Mario,

 I'll test that on MSWin soon; hopefully that works now.

- Cirilo

On Tue, Mar 1, 2016 at 9:03 PM, Mário Luzeiro  wrote:

> > I'd also appreciate some help from anyone on the zoom function for the
> > 3D preview pane. The zoom works on Linux when using the mouse scroll
> > wheel but in MSWin I can only change the viewing angle, not the zoom. On
> > OSX I have no idea what the status is for zooming the model.
>
> Hi Cirilo,
>
> Looks like it was an old know wxWidgets issue, I fixed at:
>
> http://bazaar.launchpad.net/~mrluzeiro/kicad/kicad_new3d-viewer/revision/5897
>
> I found it here:
>
> https://github.com/KiCad/kicad-source-mirror/blob/a9427f899926155e48cab93187415710abc5438a/3d-viewer/3d_frame.cpp#L220
>
> In any case, in my windows laptop, the touchpad is not able to scrool..
> but. I think it is some particularity of this windows/laptop...
> I tested with a mouse and it worked.
>
> Mario Luzeiro
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Mário Luzeiro]

> I'd also appreciate some help from anyone on the zoom function for the
> 3D preview pane. The zoom works on Linux when using the mouse scroll
> wheel but in MSWin I can only change the viewing angle, not the zoom. On
> OSX I have no idea what the status is for zooming the model.

Hi Cirilo,

Looks like it was an old know wxWidgets issue, I fixed at:
http://bazaar.launchpad.net/~mrluzeiro/kicad/kicad_new3d-viewer/revision/5897

I found it here:
https://github.com/KiCad/kicad-source-mirror/blob/a9427f899926155e48cab93187415710abc5438a/3d-viewer/3d_frame.cpp#L220

In any case, in my windows laptop, the touchpad is not able to scrool.. but. I 
think it is some particularity of this windows/laptop...
I tested with a mouse and it worked.

Mario Luzeiro
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

Hi Wayne,

 The latest version of the 3D_initial_merge branch (r6537) has the
following changes:

1. synced with main branch r6601
2. changes to 3D resolver to alleviate the reported problem with KISYS3DMOD
  being a subdirectory of the current working directory
3. changes by Bernhard to ensure a working installation on OSX
4. various small bug fixes and code cleanup
5. UI improvement (path configuration button added to Footprint Properties
editors)

 I haven't had much feedback on MSWin so far. The crash on loading the
3D plugins is likely due to MSWin not finding libraries such as wxwidgets
and
kicad_3dsg to link to the plugins at runtime. If that's the case then this
is a
packaging issue and I'd need some assistance from MSWin experts on how
to address the problem. One obvious method of course is to put the plugins
in the kicad/bin directory on MSWin, but I'd like to avoid that kludge if
possible.

 I'd also appreciate some help from anyone on the zoom function for the
3D preview pane. The zoom works on Linux when using the mouse scroll
wheel but in MSWin I can only change the viewing angle, not the zoom. On
OSX I have no idea what the status is for zooming the model.

- Cirilo


On Thu, Feb 25, 2016 at 4:51 AM, Wayne Stambaugh 
wrote:

> Thanks Bernhard,
>
> Before I committed the 3D refactor, I was going to ask our package devs
> to take a look at it due to the new 3D model plugins.  I would like to
> get this correct before I commit it.  What's the status on windows.
> I've built and installed from source and that works find but I'm
> guessing our installers will need to be changed to accommodate this.
> Once we have the install issues sorted out, I'll commit it.
>
> Cheers,
>
> Wayne
>
> On 2/24/2016 12:26 PM, Bernhard Stegmaier wrote:
> > Hi,
> >
> > I just tried on OS X and plugin handling doesn’t seem to be OK.
> > At least, “make install” does directly (try to) install them to
> > “/Applications/…” which is completely wrong (and also maybe the case why
> > my built binary doesn’t find them?). Also, the path itself under
> > SharedSupport I guess isn’t right.
> >
> > It also install this here
> > bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
> > total 464
> > drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
> > drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
> > -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17
> > libkicad_3dsg..0.0.dylib
> > lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17 libkicad_3dsg.dylib
> > -> libkicad_3dsg..0.0.dylib
> > which doesn’t look right, what is it good for?
> >
> > If you like, I can have a look and try to fix this.
> >
> >
> > Regards,
> > Bernhard
> >
> >> On 23.02.2016, at 22:21, Cirilo Bernardo  >> > wrote:
> >>
> >>
> >>
> >> On Tue, Feb 23, 2016 at 7:37 PM, jp charras  >> > wrote:
> >>
> >> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
> >> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh <
> stambau...@gmail.com >
> >> > wrote:
> >> >
> >> >> Cirilo,
> >> >>
> >> >> I have one last change request that I missed in my previous
> review.
> >> >> Please change your debugging output method.  Windows apps have no
> >> >> concept of stdout even when run from the command line.
> wxLogTrace is
> >> >> the preferred method for debugging output.  It solves two
> problems.  The
> >> >> debugging strings are redirected to the correct output on all
> supported
> >> >> platforms and the debugging output is turned off by default.
> Turning on
> >> >> the debugging output is as simple as:
> >> >>
> >> >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
> >> >>
> >> >> The is handy so I don't have to sift through everyone's
> debugging output
> >> >> to find what I'm looking for.  You just need to pick a unique
> string not
> >> >> used by any other kicad wxLogTrace calls to enable tracing of
> your
> >> >> debugging output.
> >> >>
> >> >>
> >> > The 3d_initial_merge branch has been updated to use wxLogTrace;
> >> > it has also been synchronized to the main branch r6527.  The
> latest
> >> > revision for the 3d_initial_merge branch is r6527. The branch
> builds
> >> > successfully and I have tested the previewer with various VRML1/2
> and
> >> > X3D models.
> >> >
> >> > - Cirilo
> >>
> >> Thanks, Cirilo.
> >> Very good work.
> >>
> >> At least on Windows, 3d_plugin_manager.cpp is missing the line:
> >> #include 
> >>
> >> Without this include, it does not compile.
> >>
> >> --
> >> Jean-Pierre CHARRAS
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> 

Re: [Kicad-developers] 3D refactor

[Bernhard Stegmaier]

Hi Cirilo,

I made all the needed changes to support the new 3d plugins on OS X and pushed 
them to
  lp:~stegmaier/kicad/3d_initial_merge

Most important part is in rev6530 and rev6536.
All other changes starting with rev6529 are cleanups, bugfixes and fixes for 
clang warnings I came across.
You might want to review them.

Everything seems to be fine so far, at least I can see previews in the various 
new dialogs.

Two very minor things I have seen:
(1) When the “Select 3D Model” dialog is opened, the Paths combobox shows a 
correct path - wherever it may come from, is it $KISYS3DMOD?
The path/file sector above shows some (random?) path.
If I click once on the Paths combobox, this path gets selected also in the 
path/file selector.
I guess there is just a small initialization on opening the dialog missing for 
both to be consistent from the beginning.
(2) I guess the path mentioned in (1) comes from $KISYS3DMOD. However, the 
“Configure Paths” shows just an empty table. If $KISYS3DMOD is implicitly used, 
shouldn’t it somehow also show up in that dialog? Maybe just to not confuse 
people and make it obvious that $KISYS3DMOD is also taken into account?


Regards,
Bernhard

> On 24.02.2016, at 22:34, Cirilo Bernardo  wrote:
> 
> Thanks Bernhard,
> 
>  I appreciate all your work sorting this out on OSX.
> 
> - Cirilo
> 
> On Thu, Feb 25, 2016 at 8:31 AM, Bernhard Stegmaier  > wrote:
> Hi Cirilo,
> 
> thanks for the explanation.
> 
> I am half-way done with OS X adaptions… there were some really nasty 
> pitfalls, it is a little more than just putting in some correct paths.
> As of now, plugins are installed into correct locations and are found from 
> plugin manager.
> 
> I have to figure out how to link 3D plugins with correct library paths 
> against libkicad_3dsg.
> That’s not so easy because everything has to be relocatable, i.e. relative to 
> each other.
> I hope I’ll get that done tomorrow evening.
> 
> I’ll push everything to lp, so that you can pull in the changes.
> 
> 
> Regards,
> Bernhard
> 
>> On 24 Feb 2016, at 22:21, Cirilo Bernardo > > wrote:
>> 
>> Hi Bernhard,
>> 
>>  Thanks for testing this.  I don't know anything at all about OSX so I need
>> to rely on OSX users and developers to sort out any issues. The new 3D
>> code has 2 sets of libraries associated:
>> 
>> 1. libkicad_3dsg is a library which both kicad and any 3D plugin must link
>> to at runtime, so this needs to be installed where the OSX dynamic loader
>> will find it.  The install script is in 3d-viewer/3d_cache/CMakeLists.txt and
>> at the moment the destination is ${KICAD_LIB} (defined in the top level
>> CMakeLists.txt) but I can make changes to suit wherever is appropriate
>> for OSX.
>> 
>> 2. 3D plugins: there are currently 2: libs3d_plugin_idf and 
>> libs3d_plugin_vrml.
>> These need to be installed somewhere the 3D Plugin Manager will find them,
>> but it is not necessary for them to be in the  search path of the dynamic
>> loader. Plugins are installed to ${KICAD_USER_PLUGIN}/3d - if we change
>> the location of these files I will also need to make changes to the source
>> code.
>> 
>> So, if you can recommend what paths to install to I can make the changes.
>> 
>> - Cirilo
>> 
>> 
>> On Thu, Feb 25, 2016 at 4:26 AM, Bernhard Stegmaier > > wrote:
>> Hi,
>> 
>> I just tried on OS X and plugin handling doesn’t seem to be OK.
>> At least, “make install” does directly (try to) install them to 
>> “/Applications/…” which is completely wrong (and also maybe the case why my 
>> built binary doesn’t find them?). Also, the path itself under SharedSupport 
>> I guess isn’t right.
>> 
>> It also install this here
>> bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
>> total 464
>> drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
>> drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
>> -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17 libkicad_3dsg..0.0.dylib
>> lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17 libkicad_3dsg.dylib -> 
>> libkicad_3dsg..0.0.dylib
>> which doesn’t look right, what is it good for?
>> 
>> If you like, I can have a look and try to fix this.
>> 
>> 
>> Regards,
>> Bernhard
>> 
>>> On 23.02.2016, at 22:21, Cirilo Bernardo >> > wrote:
>>> 
>>> 
>>> 
>>> On Tue, Feb 23, 2016 at 7:37 PM, jp charras >> > wrote:
>>> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
>>> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh >> > >
>>> > wrote:
>>> >
>>> >> Cirilo,
>>> >>
>>> >> I have one last change request that I missed in my previous review.
>>> >> Please change your debugging output method.  Windows apps have no

Re: [Kicad-developers] 3D refactor

[Nick Østergaard]

2016-02-25 22:41 GMT+01:00 Cirilo Bernardo :
>
>
> On Fri, Feb 26, 2016 at 1:07 AM, Wayne Stambaugh 
> wrote:
>>
>> I found KISYS3DMOD was set to the path where KiCad was installed but I
>> don't think I set it.  Does the windows installer set the KISYSMOD and
>> KISYS3DMOD environment variables for all users?  I deleted the
>> KISYS3DMOD environment variable and Pcbnew did not crash.  However, I
>> still got the warning dialog about the missing model file when Pcbnew
>> was launched.  @Cirilo, would you please change this so that the missing
>> 3D model warning dialog is displayed when the 3D viewer is launched
>> rather than when Pcbnew is launched.  I'm guessing this will annoy users.
>>
>
> Hi Wayne,  which warning dialog do you mean? The only ones which
> should pop up are related to search paths (duplicate search paths etc)
> and are there to alert the user that they may need to make changes
> to the 3D search path configuration. In the case of the dialog you posted
> (3d-refactor-win64-install-1.png) r6531 includes a modification to prevent
> the automatic inclusion of the Current Working DIrectory in the search
> path so that specific warning should no longer appear on MSWin.
>
>>
>> What is most concerning is that when I ran kicad from gdb, it did not
>> crash so there is something at play here that makes me uncomfortable.  I
>> ran it from the mingw64 version of gdb as well as the mingw64 version of
>> QT Creator and it ran fine in both cases.  The bzr version on the
>> installer says r6528 even though the version string says no-bzr.
>>
>
> I'll do a careful check of the top level CMakeLists.txt file as nickoe
> suggests.

FWIW, I am using bzr directly for the 3d_initial_merge branch, where
as I am using git for the normal nightlies. But I wonder why the
create from bzr revno seems broken. I don't think it has been changed
recently, but I could be wrong. I also just tried to compare your
versions of the stuff with the latest form product and it looks the
same, except for the expected changes for the new plugins. So maybe it
is just a broken CMakeModules/CreateBzrVersionHeader.cmake?

I don't really like to use bzr, so I try to avoid that. It was just
easier to use bzr directly in the PKGBUILD I use to build the testing
version.

>
> - Cirilo
>
>>
>> On 2/25/2016 4:46 AM, Nick Østergaard wrote:
>> > Hi Wayne
>> >
>> > It does not crash for me. Does this also happen if the KISYS3DMOD env
>> > var is not set on your system?
>> >
>> > The plugins seems to be loaded correctly because I can see the 3D
>> > models in the preview.
>> >
>> > Also, the build is a debug build, you should be able to run the
>> > pcbnew.exe you installed form the the gdb in msys2, if you can
>> > reproduce the issue when running form msys2.
>> >
>> > 2016-02-24 21:33 GMT+01:00 Wayne Stambaugh :
>> >> The installed windows version is crashing for me.  When I launch Pcbnew
>> >> from KiCad I get a warning dialog about KISYS3DMOD
>> >> (3d-refactor-win64-install-1.png).  When I dismiss this dialog I get a
>> >> windows system warning dialog (3d-refactor-win64-install-2.png.  When I
>> >> dismiss the windows system warning dialog, pcbnew crashes taking kicad
>> >> with it.  I didn't look but is it possible that Pcbnew is not finding
>> >> the 3d plugin library.  Cirilo, would you please verify the windows
>> >> library load and install paths?
>> >>
>> >> On 2/24/2016 1:12 PM, Nick Østergaard wrote:
>> >>> See http://downloads.kicad-pcb.org/windows/testing/3d_initial_merge/
>> >>>
>> >>> I have not tested it recently, it might have some issue, please test
>> >>> it.
>> >>>
>> >>> 2016-02-24 18:51 GMT+01:00 Wayne Stambaugh :
>>  Thanks Bernhard,
>> 
>>  Before I committed the 3D refactor, I was going to ask our package
>>  devs
>>  to take a look at it due to the new 3D model plugins.  I would like
>>  to
>>  get this correct before I commit it.  What's the status on windows.
>>  I've built and installed from source and that works find but I'm
>>  guessing our installers will need to be changed to accommodate this.
>>  Once we have the install issues sorted out, I'll commit it.
>> 
>>  Cheers,
>> 
>>  Wayne
>> 
>>  On 2/24/2016 12:26 PM, Bernhard Stegmaier wrote:
>> > Hi,
>> >
>> > I just tried on OS X and plugin handling doesn’t seem to be OK.
>> > At least, “make install” does directly (try to) install them to
>> > “/Applications/…” which is completely wrong (and also maybe the case
>> > why
>> > my built binary doesn’t find them?). Also, the path itself under
>> > SharedSupport I guess isn’t right.
>> >
>> > It also install this here
>> > bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
>> > total 464
>> > drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
>> > drwxr-xr-x  3 bstegmaier  admin 102 24 

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

On Fri, Feb 26, 2016 at 1:07 AM, Wayne Stambaugh 
wrote:

> I found KISYS3DMOD was set to the path where KiCad was installed but I
> don't think I set it.  Does the windows installer set the KISYSMOD and
> KISYS3DMOD environment variables for all users?  I deleted the
> KISYS3DMOD environment variable and Pcbnew did not crash.  However, I
> still got the warning dialog about the missing model file when Pcbnew
> was launched.  @Cirilo, would you please change this so that the missing
> 3D model warning dialog is displayed when the 3D viewer is launched
> rather than when Pcbnew is launched.  I'm guessing this will annoy users.
>
>
Hi Wayne,  which warning dialog do you mean? The only ones which
should pop up are related to search paths (duplicate search paths etc)
and are there to alert the user that they may need to make changes
to the 3D search path configuration. In the case of the dialog you posted
(3d-refactor-win64-install-1.png) r6531 includes a modification to prevent
the automatic inclusion of the Current Working DIrectory in the search
path so that specific warning should no longer appear on MSWin.


> What is most concerning is that when I ran kicad from gdb, it did not
> crash so there is something at play here that makes me uncomfortable.  I
> ran it from the mingw64 version of gdb as well as the mingw64 version of
> QT Creator and it ran fine in both cases.  The bzr version on the
> installer says r6528 even though the version string says no-bzr.
>
>
I'll do a careful check of the top level CMakeLists.txt file as nickoe
suggests.

- Cirilo


> On 2/25/2016 4:46 AM, Nick Østergaard wrote:
> > Hi Wayne
> >
> > It does not crash for me. Does this also happen if the KISYS3DMOD env
> > var is not set on your system?
> >
> > The plugins seems to be loaded correctly because I can see the 3D
> > models in the preview.
> >
> > Also, the build is a debug build, you should be able to run the
> > pcbnew.exe you installed form the the gdb in msys2, if you can
> > reproduce the issue when running form msys2.
> >
> > 2016-02-24 21:33 GMT+01:00 Wayne Stambaugh :
> >> The installed windows version is crashing for me.  When I launch Pcbnew
> >> from KiCad I get a warning dialog about KISYS3DMOD
> >> (3d-refactor-win64-install-1.png).  When I dismiss this dialog I get a
> >> windows system warning dialog (3d-refactor-win64-install-2.png.  When I
> >> dismiss the windows system warning dialog, pcbnew crashes taking kicad
> >> with it.  I didn't look but is it possible that Pcbnew is not finding
> >> the 3d plugin library.  Cirilo, would you please verify the windows
> >> library load and install paths?
> >>
> >> On 2/24/2016 1:12 PM, Nick Østergaard wrote:
> >>> See http://downloads.kicad-pcb.org/windows/testing/3d_initial_merge/
> >>>
> >>> I have not tested it recently, it might have some issue, please test
> it.
> >>>
> >>> 2016-02-24 18:51 GMT+01:00 Wayne Stambaugh :
>  Thanks Bernhard,
> 
>  Before I committed the 3D refactor, I was going to ask our package
> devs
>  to take a look at it due to the new 3D model plugins.  I would like to
>  get this correct before I commit it.  What's the status on windows.
>  I've built and installed from source and that works find but I'm
>  guessing our installers will need to be changed to accommodate this.
>  Once we have the install issues sorted out, I'll commit it.
> 
>  Cheers,
> 
>  Wayne
> 
>  On 2/24/2016 12:26 PM, Bernhard Stegmaier wrote:
> > Hi,
> >
> > I just tried on OS X and plugin handling doesn’t seem to be OK.
> > At least, “make install” does directly (try to) install them to
> > “/Applications/…” which is completely wrong (and also maybe the case
> why
> > my built binary doesn’t find them?). Also, the path itself under
> > SharedSupport I guess isn’t right.
> >
> > It also install this here
> > bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
> > total 464
> > drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
> > drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
> > -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17
> > libkicad_3dsg..0.0.dylib
> > lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17
> libkicad_3dsg.dylib
> > -> libkicad_3dsg..0.0.dylib
> > which doesn’t look right, what is it good for?
> >
> > If you like, I can have a look and try to fix this.
> >
> >
> > Regards,
> > Bernhard
> >
> >> On 23.02.2016, at 22:21, Cirilo Bernardo  >> > wrote:
> >>
> >>
> >>
> >> On Tue, Feb 23, 2016 at 7:37 PM, jp charras  >> > wrote:
> >>
> >> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
> >> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh <
> 

Re: [Kicad-developers] 3D refactor

[Nick Østergaard]

Den 25/02/2016 15.08 skrev "Wayne Stambaugh" :
>
> I found KISYS3DMOD was set to the path where KiCad was installed but I
> don't think I set it.  Does the windows installer set the KISYSMOD and
> KISYS3DMOD environment variables for all users?  I deleted the
> KISYS3DMOD environment variable and Pcbnew did not crash.  However, I
> still got the warning dialog about the missing model file when Pcbnew
> was launched.  @Cirilo, would you please change this so that the missing
> 3D model warning dialog is displayed when the 3D viewer is launched
> rather than when Pcbnew is launched.  I'm guessing this will annoy users.
>
> What is most concerning is that when I ran kicad from gdb, it did not
> crash so there is something at play here that makes me uncomfortable.  I
> ran it from the mingw64 version of gdb as well as the mingw64 version of
> QT Creator and it ran fine in both cases.  The bzr version on the
> installer says r6528 even though the version string says no-bzr.

Without looking too much into it, I guss if this is ok on the normal
nightlies, which I think is the case, then I suspect the cmakelists to be
outdated in the 3d_initial_merge branch.

> On 2/25/2016 4:46 AM, Nick Østergaard wrote:
> > Hi Wayne
> >
> > It does not crash for me. Does this also happen if the KISYS3DMOD env
> > var is not set on your system?
> >
> > The plugins seems to be loaded correctly because I can see the 3D
> > models in the preview.
> >
> > Also, the build is a debug build, you should be able to run the
> > pcbnew.exe you installed form the the gdb in msys2, if you can
> > reproduce the issue when running form msys2.
> >
> > 2016-02-24 21:33 GMT+01:00 Wayne Stambaugh :
> >> The installed windows version is crashing for me.  When I launch Pcbnew
> >> from KiCad I get a warning dialog about KISYS3DMOD
> >> (3d-refactor-win64-install-1.png).  When I dismiss this dialog I get a
> >> windows system warning dialog (3d-refactor-win64-install-2.png.  When I
> >> dismiss the windows system warning dialog, pcbnew crashes taking kicad
> >> with it.  I didn't look but is it possible that Pcbnew is not finding
> >> the 3d plugin library.  Cirilo, would you please verify the windows
> >> library load and install paths?
> >>
> >> On 2/24/2016 1:12 PM, Nick Østergaard wrote:
> >>> See http://downloads.kicad-pcb.org/windows/testing/3d_initial_merge/
> >>>
> >>> I have not tested it recently, it might have some issue, please test
it.
> >>>
> >>> 2016-02-24 18:51 GMT+01:00 Wayne Stambaugh :
>  Thanks Bernhard,
> 
>  Before I committed the 3D refactor, I was going to ask our package
devs
>  to take a look at it due to the new 3D model plugins.  I would like
to
>  get this correct before I commit it.  What's the status on windows.
>  I've built and installed from source and that works find but I'm
>  guessing our installers will need to be changed to accommodate this.
>  Once we have the install issues sorted out, I'll commit it.
> 
>  Cheers,
> 
>  Wayne
> 
>  On 2/24/2016 12:26 PM, Bernhard Stegmaier wrote:
> > Hi,
> >
> > I just tried on OS X and plugin handling doesn’t seem to be OK.
> > At least, “make install” does directly (try to) install them to
> > “/Applications/…” which is completely wrong (and also maybe the
case why
> > my built binary doesn’t find them?). Also, the path itself under
> > SharedSupport I guess isn’t right.
> >
> > It also install this here
> > bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
> > total 464
> > drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
> > drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
> > -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17
> > libkicad_3dsg..0.0.dylib
> > lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17
libkicad_3dsg.dylib
> > -> libkicad_3dsg..0.0.dylib
> > which doesn’t look right, what is it good for?
> >
> > If you like, I can have a look and try to fix this.
> >
> >
> > Regards,
> > Bernhard
> >
> >> On 23.02.2016, at 22:21, Cirilo Bernardo  >> > wrote:
> >>
> >>
> >>
> >> On Tue, Feb 23, 2016 at 7:37 PM, jp charras  >> > wrote:
> >>
> >> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
> >> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh <
stambau...@gmail.com >
> >> > wrote:
> >> >
> >> >> Cirilo,
> >> >>
> >> >> I have one last change request that I missed in my previous
review.
> >> >> Please change your debugging output method.  Windows apps
have no
> >> >> concept of stdout even when run from the command line.
wxLogTrace is
> >> >> the preferred method for 

Re: [Kicad-developers] 3D refactor

[Wayne Stambaugh]

I found KISYS3DMOD was set to the path where KiCad was installed but I
don't think I set it.  Does the windows installer set the KISYSMOD and
KISYS3DMOD environment variables for all users?  I deleted the
KISYS3DMOD environment variable and Pcbnew did not crash.  However, I
still got the warning dialog about the missing model file when Pcbnew
was launched.  @Cirilo, would you please change this so that the missing
3D model warning dialog is displayed when the 3D viewer is launched
rather than when Pcbnew is launched.  I'm guessing this will annoy users.

What is most concerning is that when I ran kicad from gdb, it did not
crash so there is something at play here that makes me uncomfortable.  I
ran it from the mingw64 version of gdb as well as the mingw64 version of
QT Creator and it ran fine in both cases.  The bzr version on the
installer says r6528 even though the version string says no-bzr.

On 2/25/2016 4:46 AM, Nick Østergaard wrote:
> Hi Wayne
> 
> It does not crash for me. Does this also happen if the KISYS3DMOD env
> var is not set on your system?
> 
> The plugins seems to be loaded correctly because I can see the 3D
> models in the preview.
> 
> Also, the build is a debug build, you should be able to run the
> pcbnew.exe you installed form the the gdb in msys2, if you can
> reproduce the issue when running form msys2.
> 
> 2016-02-24 21:33 GMT+01:00 Wayne Stambaugh :
>> The installed windows version is crashing for me.  When I launch Pcbnew
>> from KiCad I get a warning dialog about KISYS3DMOD
>> (3d-refactor-win64-install-1.png).  When I dismiss this dialog I get a
>> windows system warning dialog (3d-refactor-win64-install-2.png.  When I
>> dismiss the windows system warning dialog, pcbnew crashes taking kicad
>> with it.  I didn't look but is it possible that Pcbnew is not finding
>> the 3d plugin library.  Cirilo, would you please verify the windows
>> library load and install paths?
>>
>> On 2/24/2016 1:12 PM, Nick Østergaard wrote:
>>> See http://downloads.kicad-pcb.org/windows/testing/3d_initial_merge/
>>>
>>> I have not tested it recently, it might have some issue, please test it.
>>>
>>> 2016-02-24 18:51 GMT+01:00 Wayne Stambaugh :
 Thanks Bernhard,

 Before I committed the 3D refactor, I was going to ask our package devs
 to take a look at it due to the new 3D model plugins.  I would like to
 get this correct before I commit it.  What's the status on windows.
 I've built and installed from source and that works find but I'm
 guessing our installers will need to be changed to accommodate this.
 Once we have the install issues sorted out, I'll commit it.

 Cheers,

 Wayne

 On 2/24/2016 12:26 PM, Bernhard Stegmaier wrote:
> Hi,
>
> I just tried on OS X and plugin handling doesn’t seem to be OK.
> At least, “make install” does directly (try to) install them to
> “/Applications/…” which is completely wrong (and also maybe the case why
> my built binary doesn’t find them?). Also, the path itself under
> SharedSupport I guess isn’t right.
>
> It also install this here
> bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
> total 464
> drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
> drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
> -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17
> libkicad_3dsg..0.0.dylib
> lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17 libkicad_3dsg.dylib
> -> libkicad_3dsg..0.0.dylib
> which doesn’t look right, what is it good for?
>
> If you like, I can have a look and try to fix this.
>
>
> Regards,
> Bernhard
>
>> On 23.02.2016, at 22:21, Cirilo Bernardo > > wrote:
>>
>>
>>
>> On Tue, Feb 23, 2016 at 7:37 PM, jp charras > > wrote:
>>
>> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
>> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh 
>> >
>> > wrote:
>> >
>> >> Cirilo,
>> >>
>> >> I have one last change request that I missed in my previous 
>> review.
>> >> Please change your debugging output method.  Windows apps have no
>> >> concept of stdout even when run from the command line.  
>> wxLogTrace is
>> >> the preferred method for debugging output.  It solves two 
>> problems.  The
>> >> debugging strings are redirected to the correct output on all 
>> supported
>> >> platforms and the debugging output is turned off by default.  
>> Turning on
>> >> the debugging output is as simple as:
>> >>
>> >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
>> >>
>> >> The is handy so I don't 

Re: [Kicad-developers] 3D refactor

[Nick Østergaard]

Hi Wayne

It does not crash for me. Does this also happen if the KISYS3DMOD env
var is not set on your system?

The plugins seems to be loaded correctly because I can see the 3D
models in the preview.

Also, the build is a debug build, you should be able to run the
pcbnew.exe you installed form the the gdb in msys2, if you can
reproduce the issue when running form msys2.

2016-02-24 21:33 GMT+01:00 Wayne Stambaugh :
> The installed windows version is crashing for me.  When I launch Pcbnew
> from KiCad I get a warning dialog about KISYS3DMOD
> (3d-refactor-win64-install-1.png).  When I dismiss this dialog I get a
> windows system warning dialog (3d-refactor-win64-install-2.png.  When I
> dismiss the windows system warning dialog, pcbnew crashes taking kicad
> with it.  I didn't look but is it possible that Pcbnew is not finding
> the 3d plugin library.  Cirilo, would you please verify the windows
> library load and install paths?
>
> On 2/24/2016 1:12 PM, Nick Østergaard wrote:
>> See http://downloads.kicad-pcb.org/windows/testing/3d_initial_merge/
>>
>> I have not tested it recently, it might have some issue, please test it.
>>
>> 2016-02-24 18:51 GMT+01:00 Wayne Stambaugh :
>>> Thanks Bernhard,
>>>
>>> Before I committed the 3D refactor, I was going to ask our package devs
>>> to take a look at it due to the new 3D model plugins.  I would like to
>>> get this correct before I commit it.  What's the status on windows.
>>> I've built and installed from source and that works find but I'm
>>> guessing our installers will need to be changed to accommodate this.
>>> Once we have the install issues sorted out, I'll commit it.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> On 2/24/2016 12:26 PM, Bernhard Stegmaier wrote:
 Hi,

 I just tried on OS X and plugin handling doesn’t seem to be OK.
 At least, “make install” does directly (try to) install them to
 “/Applications/…” which is completely wrong (and also maybe the case why
 my built binary doesn’t find them?). Also, the path itself under
 SharedSupport I guess isn’t right.

 It also install this here
 bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
 total 464
 drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
 drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
 -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17
 libkicad_3dsg..0.0.dylib
 lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17 libkicad_3dsg.dylib
 -> libkicad_3dsg..0.0.dylib
 which doesn’t look right, what is it good for?

 If you like, I can have a look and try to fix this.


 Regards,
 Bernhard

> On 23.02.2016, at 22:21, Cirilo Bernardo  > wrote:
>
>
>
> On Tue, Feb 23, 2016 at 7:37 PM, jp charras  > wrote:
>
> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh 
> >
> > wrote:
> >
> >> Cirilo,
> >>
> >> I have one last change request that I missed in my previous review.
> >> Please change your debugging output method.  Windows apps have no
> >> concept of stdout even when run from the command line.  wxLogTrace 
> is
> >> the preferred method for debugging output.  It solves two 
> problems.  The
> >> debugging strings are redirected to the correct output on all 
> supported
> >> platforms and the debugging output is turned off by default.  
> Turning on
> >> the debugging output is as simple as:
> >>
> >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
> >>
> >> The is handy so I don't have to sift through everyone's debugging 
> output
> >> to find what I'm looking for.  You just need to pick a unique 
> string not
> >> used by any other kicad wxLogTrace calls to enable tracing of your
> >> debugging output.
> >>
> >>
> > The 3d_initial_merge branch has been updated to use wxLogTrace;
> > it has also been synchronized to the main branch r6527.  The latest
> > revision for the 3d_initial_merge branch is r6527. The branch builds
> > successfully and I have tested the previewer with various VRML1/2 
> and
> > X3D models.
> >
> > - Cirilo
>
> Thanks, Cirilo.
> Very good work.
>
> At least on Windows, 3d_plugin_manager.cpp is missing the line:
> #include 
>
> Without this include, it does not compile.
>
> --
> Jean-Pierre CHARRAS
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> 

Re: [Kicad-developers] 3D refactor

[Mário Luzeiro]

Hi Cirilo,

I suggest that in CBBOX.cpp
instead of:

void CBBOX::Union( const CBBOX  )
{
wxASSERT( aBBox.IsInitialized() );

you change the assert to something like:

if( !aBBox.IsInitialized() )
 return;

That is safer and compatible with the actual source code.

Mario

From: Cirilo Bernardo [cirilo.berna...@gmail.com]
Sent: 24 February 2016 22:12
To: Mário Luzeiro
Cc: Nick Østergaard; KiCad Developers
Subject: Re: [Kicad-developers] 3D refactor

Hi Mario,

 For the initial merge would it be OK for me to remove that assert?
Although it is useful for debugging, the current 3DViewer works well
even with that assertion failure and the Union() function still behaves
as expected, essentially ignoring the uninitialized BBox.

- Cirilo

On Thu, Feb 25, 2016 at 4:51 AM, Mário Luzeiro 
<mrluze...@ua.pt<mailto:mrluze...@ua.pt>> wrote:
Hi NickOe,
Thanks for trying the branch!

Cirilo is managing that branching. He is "cherry picking" things from my 
working branch on the renders to get a smooth transition between our branches 
and trunk
I guess that is because that cbbox.cpp comes from the new branches and maybe it 
indicated that something is wrong originally in the stable trunk or something 
was not proper integrated with that new cbbox.
It is however a minor issue, since this new cbbox lib have more checks and 
expect the things more strictly... so maybe it is not an issue at all.

The backtrace does not help since it does not show any function that is using 
the cbbox :/
I think if you run it with gdb it will give more precise info if you get the 
backtrace.

Mario


From: Kicad-developers 
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net<mailto:ua...@lists.launchpad.net>]
 on behalf of Nick Østergaard [oe.n...@gmail.com<mailto:oe.n...@gmail.com>]
Sent: 24 February 2016 17:36
To: Cirilo Bernardo
Cc: KiCad Developers
Subject: Re: [Kicad-developers] 3D refactor

Hi Cirilo and Mario,

I just built the 3d_initial_merge branch revno 6528, but I see some
annoying asserts when running the 3d viewer, not the previewer in the
3d properties dialog:

ASSERT INFO:
/somepath/3d_initial_merge/3d-viewer/3d_rendering/3d_render_raytracing/shapes3D/cbbox.cpp(114):
assert "aBBox.IsInitialized()" failed in Union().

BACKTRACE:
[1] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&,
wxEvent&) const
[2] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase
const&, wxEvtHandler*, wxEvent&)
[3] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[4] wxEvtHandler::TryHereOnly(wxEvent&)
[5] wxEvtHandler::ProcessEventLocally(wxEvent&)
[6] wxEvtHandler::ProcessEvent(wxEvent&)
[7] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[8] wxGLCanvas::OnInternalIdle()
[9] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[10] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[11] wxFrame::SendIdleEvents(wxIdleEvent&)
[12] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[13] wxFrame::SendIdleEvents(wxIdleEvent&)
[14] wxAppBase::ProcessIdle()
[15] wxApp::DoIdle()
[16] g_main_context_dispatch
[17] g_main_loop_run
[18] gtk_main
[19] wxGUIEventLoop::DoRun()
[20] wxEventLoopBase::Run()
[21] wxAppConsoleBase::MainLoop()
[22] APP_SINGLE_TOP::OnRun()
/somepath/3d_initial_merge/common/single_top.cpp:173
[23] wxEntry(int&, wchar_t**)
[24] main /somepath/3d_initial_merge/common/single_top.cpp:210
[25] __libc_start_main
[26] _start

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

Hi Mario,

 For the initial merge would it be OK for me to remove that assert?
Although it is useful for debugging, the current 3DViewer works well
even with that assertion failure and the Union() function still behaves
as expected, essentially ignoring the uninitialized BBox.

- Cirilo

On Thu, Feb 25, 2016 at 4:51 AM, Mário Luzeiro <mrluze...@ua.pt> wrote:

> Hi NickOe,
> Thanks for trying the branch!
>
> Cirilo is managing that branching. He is "cherry picking" things from my
> working branch on the renders to get a smooth transition between our
> branches and trunk
> I guess that is because that cbbox.cpp comes from the new branches and
> maybe it indicated that something is wrong originally in the stable trunk
> or something was not proper integrated with that new cbbox.
> It is however a minor issue, since this new cbbox lib have more checks and
> expect the things more strictly... so maybe it is not an issue at all.
>
> The backtrace does not help since it does not show any function that is
> using the cbbox :/
> I think if you run it with gdb it will give more precise info if you get
> the backtrace.
>
> Mario
>
> 
> From: Kicad-developers [kicad-developers-bounces+mrluzeiro=
> ua...@lists.launchpad.net] on behalf of Nick Østergaard [oe.n...@gmail.com
> ]
> Sent: 24 February 2016 17:36
> To: Cirilo Bernardo
> Cc: KiCad Developers
> Subject: Re: [Kicad-developers] 3D refactor
>
> Hi Cirilo and Mario,
>
> I just built the 3d_initial_merge branch revno 6528, but I see some
> annoying asserts when running the 3d viewer, not the previewer in the
> 3d properties dialog:
>
> ASSERT INFO:
>
> /somepath/3d_initial_merge/3d-viewer/3d_rendering/3d_render_raytracing/shapes3D/cbbox.cpp(114):
> assert "aBBox.IsInitialized()" failed in Union().
>
> BACKTRACE:
> [1] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&,
> wxEvent&) const
> [2] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase
> const&, wxEvtHandler*, wxEvent&)
> [3] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
> [4] wxEvtHandler::TryHereOnly(wxEvent&)
> [5] wxEvtHandler::ProcessEventLocally(wxEvent&)
> [6] wxEvtHandler::ProcessEvent(wxEvent&)
> [7] wxEvtHandler::SafelyProcessEvent(wxEvent&)
> [8] wxGLCanvas::OnInternalIdle()
> [9] wxWindowBase::SendIdleEvents(wxIdleEvent&)
> [10] wxWindowBase::SendIdleEvents(wxIdleEvent&)
> [11] wxFrame::SendIdleEvents(wxIdleEvent&)
> [12] wxWindowBase::SendIdleEvents(wxIdleEvent&)
> [13] wxFrame::SendIdleEvents(wxIdleEvent&)
> [14] wxAppBase::ProcessIdle()
> [15] wxApp::DoIdle()
> [16] g_main_context_dispatch
> [17] g_main_loop_run
> [18] gtk_main
> [19] wxGUIEventLoop::DoRun()
> [20] wxEventLoopBase::Run()
> [21] wxAppConsoleBase::MainLoop()
> [22] APP_SINGLE_TOP::OnRun()
> /somepath/3d_initial_merge/common/single_top.cpp:173
> [23] wxEntry(int&, wchar_t**)
> [24] main /somepath/3d_initial_merge/common/single_top.cpp:210
> [25] __libc_start_main
> [26] _start
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

Thanks Bernhard,

 I appreciate all your work sorting this out on OSX.

- Cirilo

On Thu, Feb 25, 2016 at 8:31 AM, Bernhard Stegmaier  wrote:

> Hi Cirilo,
>
> thanks for the explanation.
>
> I am half-way done with OS X adaptions… there were some really nasty
> pitfalls, it is a little more than just putting in some correct paths.
> As of now, plugins are installed into correct locations and are found from
> plugin manager.
>
> I have to figure out how to link 3D plugins with correct library paths
> against libkicad_3dsg.
> That’s not so easy because everything has to be relocatable, i.e. relative
> to each other.
> I hope I’ll get that done tomorrow evening.
>
> I’ll push everything to lp, so that you can pull in the changes.
>
>
> Regards,
> Bernhard
>
> On 24 Feb 2016, at 22:21, Cirilo Bernardo 
> wrote:
>
> Hi Bernhard,
>
>  Thanks for testing this.  I don't know anything at all about OSX so I need
> to rely on OSX users and developers to sort out any issues. The new 3D
> code has 2 sets of libraries associated:
>
> 1. libkicad_3dsg is a library which both kicad and any 3D plugin must link
> to at runtime, so this needs to be installed where the OSX dynamic loader
> will find it.  The install script is in 3d-viewer/3d_cache/CMakeLists.txt
> and
> at the moment the destination is ${KICAD_LIB} (defined in the top level
> CMakeLists.txt) but I can make changes to suit wherever is appropriate
> for OSX.
>
> 2. 3D plugins: there are currently 2: libs3d_plugin_idf and
> libs3d_plugin_vrml.
> These need to be installed somewhere the 3D Plugin Manager will find them,
> but it is not necessary for them to be in the  search path of the dynamic
> loader. Plugins are installed to ${KICAD_USER_PLUGIN}/3d - if we change
> the location of these files I will also need to make changes to the source
> code.
>
> So, if you can recommend what paths to install to I can make the changes.
>
> - Cirilo
>
>
> On Thu, Feb 25, 2016 at 4:26 AM, Bernhard Stegmaier <
> stegma...@sw-systems.de> wrote:
>
>> Hi,
>>
>> I just tried on OS X and plugin handling doesn’t seem to be OK.
>> At least, “make install” does directly (try to) install them to
>> “/Applications/…” which is completely wrong (and also maybe the case why my
>> built binary doesn’t find them?). Also, the path itself under SharedSupport
>> I guess isn’t right.
>>
>> It also install this here
>> bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
>> total 464
>> drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
>> drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
>> -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17
>> libkicad_3dsg..0.0.dylib
>> lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17 libkicad_3dsg.dylib
>> -> libkicad_3dsg..0.0.dylib
>> which doesn’t look right, what is it good for?
>>
>> If you like, I can have a look and try to fix this.
>>
>>
>> Regards,
>> Bernhard
>>
>> On 23.02.2016, at 22:21, Cirilo Bernardo 
>> wrote:
>>
>>
>>
>> On Tue, Feb 23, 2016 at 7:37 PM, jp charras 
>> wrote:
>>
>>> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
>>> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh >> >
>>> > wrote:
>>> >
>>> >> Cirilo,
>>> >>
>>> >> I have one last change request that I missed in my previous review.
>>> >> Please change your debugging output method.  Windows apps have no
>>> >> concept of stdout even when run from the command line.  wxLogTrace is
>>> >> the preferred method for debugging output.  It solves two problems.
>>> The
>>> >> debugging strings are redirected to the correct output on all
>>> supported
>>> >> platforms and the debugging output is turned off by default.  Turning
>>> on
>>> >> the debugging output is as simple as:
>>> >>
>>> >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
>>> >>
>>> >> The is handy so I don't have to sift through everyone's debugging
>>> output
>>> >> to find what I'm looking for.  You just need to pick a unique string
>>> not
>>> >> used by any other kicad wxLogTrace calls to enable tracing of your
>>> >> debugging output.
>>> >>
>>> >>
>>> > The 3d_initial_merge branch has been updated to use wxLogTrace;
>>> > it has also been synchronized to the main branch r6527.  The latest
>>> > revision for the 3d_initial_merge branch is r6527. The branch builds
>>> > successfully and I have tested the previewer with various VRML1/2 and
>>> > X3D models.
>>> >
>>> > - Cirilo
>>>
>>> Thanks, Cirilo.
>>> Very good work.
>>>
>>> At least on Windows, 3d_plugin_manager.cpp is missing the line:
>>> #include 
>>>
>>> Without this include, it does not compile.
>>>
>>> --
>>> Jean-Pierre CHARRAS
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : 

Re: [Kicad-developers] 3D refactor

[Bernhard Stegmaier]

Hi Cirilo,

thanks for the explanation.

I am half-way done with OS X adaptions… there were some really nasty pitfalls, 
it is a little more than just putting in some correct paths.
As of now, plugins are installed into correct locations and are found from 
plugin manager.

I have to figure out how to link 3D plugins with correct library paths against 
libkicad_3dsg.
That’s not so easy because everything has to be relocatable, i.e. relative to 
each other.
I hope I’ll get that done tomorrow evening.

I’ll push everything to lp, so that you can pull in the changes.


Regards,
Bernhard

> On 24 Feb 2016, at 22:21, Cirilo Bernardo  wrote:
> 
> Hi Bernhard,
> 
>  Thanks for testing this.  I don't know anything at all about OSX so I need
> to rely on OSX users and developers to sort out any issues. The new 3D
> code has 2 sets of libraries associated:
> 
> 1. libkicad_3dsg is a library which both kicad and any 3D plugin must link
> to at runtime, so this needs to be installed where the OSX dynamic loader
> will find it.  The install script is in 3d-viewer/3d_cache/CMakeLists.txt and
> at the moment the destination is ${KICAD_LIB} (defined in the top level
> CMakeLists.txt) but I can make changes to suit wherever is appropriate
> for OSX.
> 
> 2. 3D plugins: there are currently 2: libs3d_plugin_idf and 
> libs3d_plugin_vrml.
> These need to be installed somewhere the 3D Plugin Manager will find them,
> but it is not necessary for them to be in the  search path of the dynamic
> loader. Plugins are installed to ${KICAD_USER_PLUGIN}/3d - if we change
> the location of these files I will also need to make changes to the source
> code.
> 
> So, if you can recommend what paths to install to I can make the changes.
> 
> - Cirilo
> 
> 
> On Thu, Feb 25, 2016 at 4:26 AM, Bernhard Stegmaier  > wrote:
> Hi,
> 
> I just tried on OS X and plugin handling doesn’t seem to be OK.
> At least, “make install” does directly (try to) install them to 
> “/Applications/…” which is completely wrong (and also maybe the case why my 
> built binary doesn’t find them?). Also, the path itself under SharedSupport I 
> guess isn’t right.
> 
> It also install this here
> bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
> total 464
> drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
> drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
> -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17 libkicad_3dsg..0.0.dylib
> lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17 libkicad_3dsg.dylib -> 
> libkicad_3dsg..0.0.dylib
> which doesn’t look right, what is it good for?
> 
> If you like, I can have a look and try to fix this.
> 
> 
> Regards,
> Bernhard
> 
>> On 23.02.2016, at 22:21, Cirilo Bernardo > > wrote:
>> 
>> 
>> 
>> On Tue, Feb 23, 2016 at 7:37 PM, jp charras > > wrote:
>> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
>> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh > > >
>> > wrote:
>> >
>> >> Cirilo,
>> >>
>> >> I have one last change request that I missed in my previous review.
>> >> Please change your debugging output method.  Windows apps have no
>> >> concept of stdout even when run from the command line.  wxLogTrace is
>> >> the preferred method for debugging output.  It solves two problems.  The
>> >> debugging strings are redirected to the correct output on all supported
>> >> platforms and the debugging output is turned off by default.  Turning on
>> >> the debugging output is as simple as:
>> >>
>> >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
>> >>
>> >> The is handy so I don't have to sift through everyone's debugging output
>> >> to find what I'm looking for.  You just need to pick a unique string not
>> >> used by any other kicad wxLogTrace calls to enable tracing of your
>> >> debugging output.
>> >>
>> >>
>> > The 3d_initial_merge branch has been updated to use wxLogTrace;
>> > it has also been synchronized to the main branch r6527.  The latest
>> > revision for the 3d_initial_merge branch is r6527. The branch builds
>> > successfully and I have tested the previewer with various VRML1/2 and
>> > X3D models.
>> >
>> > - Cirilo
>> 
>> Thanks, Cirilo.
>> Very good work.
>> 
>> At least on Windows, 3d_plugin_manager.cpp is missing the line:
>> #include 
>> 
>> Without this include, it does not compile.
>> 
>> --
>> Jean-Pierre CHARRAS
>> 
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers 
>> 
>> Post to : kicad-developers@lists.launchpad.net 
>> 
>> Unsubscribe : https://launchpad.net/~kicad-developers 
>> 
>> More help   : 

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

Hi Bernhard,

 Thanks for testing this.  I don't know anything at all about OSX so I need
to rely on OSX users and developers to sort out any issues. The new 3D
code has 2 sets of libraries associated:

1. libkicad_3dsg is a library which both kicad and any 3D plugin must link
to at runtime, so this needs to be installed where the OSX dynamic loader
will find it.  The install script is in 3d-viewer/3d_cache/CMakeLists.txt
and
at the moment the destination is ${KICAD_LIB} (defined in the top level
CMakeLists.txt) but I can make changes to suit wherever is appropriate
for OSX.

2. 3D plugins: there are currently 2: libs3d_plugin_idf and
libs3d_plugin_vrml.
These need to be installed somewhere the 3D Plugin Manager will find them,
but it is not necessary for them to be in the  search path of the dynamic
loader. Plugins are installed to ${KICAD_USER_PLUGIN}/3d - if we change
the location of these files I will also need to make changes to the source
code.

So, if you can recommend what paths to install to I can make the changes.

- Cirilo


On Thu, Feb 25, 2016 at 4:26 AM, Bernhard Stegmaier  wrote:

> Hi,
>
> I just tried on OS X and plugin handling doesn’t seem to be OK.
> At least, “make install” does directly (try to) install them to
> “/Applications/…” which is completely wrong (and also maybe the case why my
> built binary doesn’t find them?). Also, the path itself under SharedSupport
> I guess isn’t right.
>
> It also install this here
> bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
> total 464
> drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
> drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
> -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17
> libkicad_3dsg..0.0.dylib
> lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17 libkicad_3dsg.dylib
> -> libkicad_3dsg..0.0.dylib
> which doesn’t look right, what is it good for?
>
> If you like, I can have a look and try to fix this.
>
>
> Regards,
> Bernhard
>
> On 23.02.2016, at 22:21, Cirilo Bernardo 
> wrote:
>
>
>
> On Tue, Feb 23, 2016 at 7:37 PM, jp charras  wrote:
>
>> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
>> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh 
>> > wrote:
>> >
>> >> Cirilo,
>> >>
>> >> I have one last change request that I missed in my previous review.
>> >> Please change your debugging output method.  Windows apps have no
>> >> concept of stdout even when run from the command line.  wxLogTrace is
>> >> the preferred method for debugging output.  It solves two problems.
>> The
>> >> debugging strings are redirected to the correct output on all supported
>> >> platforms and the debugging output is turned off by default.  Turning
>> on
>> >> the debugging output is as simple as:
>> >>
>> >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
>> >>
>> >> The is handy so I don't have to sift through everyone's debugging
>> output
>> >> to find what I'm looking for.  You just need to pick a unique string
>> not
>> >> used by any other kicad wxLogTrace calls to enable tracing of your
>> >> debugging output.
>> >>
>> >>
>> > The 3d_initial_merge branch has been updated to use wxLogTrace;
>> > it has also been synchronized to the main branch r6527.  The latest
>> > revision for the 3d_initial_merge branch is r6527. The branch builds
>> > successfully and I have tested the previewer with various VRML1/2 and
>> > X3D models.
>> >
>> > - Cirilo
>>
>> Thanks, Cirilo.
>> Very good work.
>>
>> At least on Windows, 3d_plugin_manager.cpp is missing the line:
>> #include 
>>
>> Without this include, it does not compile.
>>
>> --
>> Jean-Pierre CHARRAS
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> Thanks Jean-Pierre,
>
>  I have added the header and checked that it builds on Windows (W7-64 bit).
>
> - Cirilo
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

I'll use the install package from Jenkins and see if I can work out
what goes wrong.

The first dialog (regarding bad alias) pops up because the current
project directory (C:\Program Files\KiCad) is a parent directory
of KISYS3DMOD. I need to think a little about how to handle that
specific case, but I think KiCad should never use that path for
the working directory anyway.

The second dialog is as vague as it can get. I've seen kicad crash
because the new scenegraph library (libkicad_3dsg) wasn't found,
but on Windows it should be installed with the exe files so that
shouldn't be a problem. The plugins themselves may fail that way
if kicad's executable directory is not in the Windows PATH since
they need to run components of wxWidgets and libkicad_3dsg.
If that is the case, we either need to set PATH appropriately or
move the plugins to the exe directory.  I would prefer to set
PATH if that's possible, but I know next to nothing about the
Windows setup and would have to take advice from Windows
users and packagers.

The plugins themselves would not cause a crash if they are not
found - there simply would be no support for the 3D file preview
if no plugins were found.

- Cirilo


On Thu, Feb 25, 2016 at 7:33 AM, Wayne Stambaugh 
wrote:

> The installed windows version is crashing for me.  When I launch Pcbnew
> from KiCad I get a warning dialog about KISYS3DMOD
> (3d-refactor-win64-install-1.png).  When I dismiss this dialog I get a
> windows system warning dialog (3d-refactor-win64-install-2.png.  When I
> dismiss the windows system warning dialog, pcbnew crashes taking kicad
> with it.  I didn't look but is it possible that Pcbnew is not finding
> the 3d plugin library.  Cirilo, would you please verify the windows
> library load and install paths?
>
> On 2/24/2016 1:12 PM, Nick Østergaard wrote:
> > See http://downloads.kicad-pcb.org/windows/testing/3d_initial_merge/
> >
> > I have not tested it recently, it might have some issue, please test it.
> >
> > 2016-02-24 18:51 GMT+01:00 Wayne Stambaugh :
> >> Thanks Bernhard,
> >>
> >> Before I committed the 3D refactor, I was going to ask our package devs
> >> to take a look at it due to the new 3D model plugins.  I would like to
> >> get this correct before I commit it.  What's the status on windows.
> >> I've built and installed from source and that works find but I'm
> >> guessing our installers will need to be changed to accommodate this.
> >> Once we have the install issues sorted out, I'll commit it.
> >>
> >> Cheers,
> >>
> >> Wayne
> >>
> >> On 2/24/2016 12:26 PM, Bernhard Stegmaier wrote:
> >>> Hi,
> >>>
> >>> I just tried on OS X and plugin handling doesn’t seem to be OK.
> >>> At least, “make install” does directly (try to) install them to
> >>> “/Applications/…” which is completely wrong (and also maybe the case
> why
> >>> my built binary doesn’t find them?). Also, the path itself under
> >>> SharedSupport I guess isn’t right.
> >>>
> >>> It also install this here
> >>> bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
> >>> total 464
> >>> drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
> >>> drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
> >>> -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17
> >>> libkicad_3dsg..0.0.dylib
> >>> lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17
> libkicad_3dsg.dylib
> >>> -> libkicad_3dsg..0.0.dylib
> >>> which doesn’t look right, what is it good for?
> >>>
> >>> If you like, I can have a look and try to fix this.
> >>>
> >>>
> >>> Regards,
> >>> Bernhard
> >>>
>  On 23.02.2016, at 22:21, Cirilo Bernardo   > wrote:
> 
> 
> 
>  On Tue, Feb 23, 2016 at 7:37 PM, jp charras   > wrote:
> 
>  Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
>  > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh <
> stambau...@gmail.com >
>  > wrote:
>  >
>  >> Cirilo,
>  >>
>  >> I have one last change request that I missed in my previous
> review.
>  >> Please change your debugging output method.  Windows apps have
> no
>  >> concept of stdout even when run from the command line.
> wxLogTrace is
>  >> the preferred method for debugging output.  It solves two
> problems.  The
>  >> debugging strings are redirected to the correct output on all
> supported
>  >> platforms and the debugging output is turned off by default.
> Turning on
>  >> the debugging output is as simple as:
>  >>
>  >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
>  >>
>  >> The is handy so I don't have to sift through everyone's
> debugging output
>  >> to find what I'm looking for.  You just need to pick a unique
> string not
>  >> used by any other kicad 

Re: [Kicad-developers] 3D refactor

[Wayne Stambaugh]

The installed windows version is crashing for me.  When I launch Pcbnew
from KiCad I get a warning dialog about KISYS3DMOD
(3d-refactor-win64-install-1.png).  When I dismiss this dialog I get a
windows system warning dialog (3d-refactor-win64-install-2.png.  When I
dismiss the windows system warning dialog, pcbnew crashes taking kicad
with it.  I didn't look but is it possible that Pcbnew is not finding
the 3d plugin library.  Cirilo, would you please verify the windows
library load and install paths?

On 2/24/2016 1:12 PM, Nick Østergaard wrote:
> See http://downloads.kicad-pcb.org/windows/testing/3d_initial_merge/
> 
> I have not tested it recently, it might have some issue, please test it.
> 
> 2016-02-24 18:51 GMT+01:00 Wayne Stambaugh :
>> Thanks Bernhard,
>>
>> Before I committed the 3D refactor, I was going to ask our package devs
>> to take a look at it due to the new 3D model plugins.  I would like to
>> get this correct before I commit it.  What's the status on windows.
>> I've built and installed from source and that works find but I'm
>> guessing our installers will need to be changed to accommodate this.
>> Once we have the install issues sorted out, I'll commit it.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 2/24/2016 12:26 PM, Bernhard Stegmaier wrote:
>>> Hi,
>>>
>>> I just tried on OS X and plugin handling doesn’t seem to be OK.
>>> At least, “make install” does directly (try to) install them to
>>> “/Applications/…” which is completely wrong (and also maybe the case why
>>> my built binary doesn’t find them?). Also, the path itself under
>>> SharedSupport I guess isn’t right.
>>>
>>> It also install this here
>>> bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
>>> total 464
>>> drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
>>> drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
>>> -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17
>>> libkicad_3dsg..0.0.dylib
>>> lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17 libkicad_3dsg.dylib
>>> -> libkicad_3dsg..0.0.dylib
>>> which doesn’t look right, what is it good for?
>>>
>>> If you like, I can have a look and try to fix this.
>>>
>>>
>>> Regards,
>>> Bernhard
>>>
 On 23.02.2016, at 22:21, Cirilo Bernardo > wrote:



 On Tue, Feb 23, 2016 at 7:37 PM, jp charras > wrote:

 Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
 > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh 
 >
 > wrote:
 >
 >> Cirilo,
 >>
 >> I have one last change request that I missed in my previous review.
 >> Please change your debugging output method.  Windows apps have no
 >> concept of stdout even when run from the command line.  wxLogTrace 
 is
 >> the preferred method for debugging output.  It solves two problems. 
  The
 >> debugging strings are redirected to the correct output on all 
 supported
 >> platforms and the debugging output is turned off by default.  
 Turning on
 >> the debugging output is as simple as:
 >>
 >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
 >>
 >> The is handy so I don't have to sift through everyone's debugging 
 output
 >> to find what I'm looking for.  You just need to pick a unique 
 string not
 >> used by any other kicad wxLogTrace calls to enable tracing of your
 >> debugging output.
 >>
 >>
 > The 3d_initial_merge branch has been updated to use wxLogTrace;
 > it has also been synchronized to the main branch r6527.  The latest
 > revision for the 3d_initial_merge branch is r6527. The branch builds
 > successfully and I have tested the previewer with various VRML1/2 and
 > X3D models.
 >
 > - Cirilo

 Thanks, Cirilo.
 Very good work.

 At least on Windows, 3d_plugin_manager.cpp is missing the line:
 #include 

 Without this include, it does not compile.

 --
 Jean-Pierre CHARRAS

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp


 Thanks Jean-Pierre,

  I have added the header and checked that it builds on Windows (W7-64
 bit).

 - Cirilo

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 

Re: [Kicad-developers] 3D refactor

[Nick Østergaard]

See http://downloads.kicad-pcb.org/windows/testing/3d_initial_merge/

I have not tested it recently, it might have some issue, please test it.

2016-02-24 18:51 GMT+01:00 Wayne Stambaugh :
> Thanks Bernhard,
>
> Before I committed the 3D refactor, I was going to ask our package devs
> to take a look at it due to the new 3D model plugins.  I would like to
> get this correct before I commit it.  What's the status on windows.
> I've built and installed from source and that works find but I'm
> guessing our installers will need to be changed to accommodate this.
> Once we have the install issues sorted out, I'll commit it.
>
> Cheers,
>
> Wayne
>
> On 2/24/2016 12:26 PM, Bernhard Stegmaier wrote:
>> Hi,
>>
>> I just tried on OS X and plugin handling doesn’t seem to be OK.
>> At least, “make install” does directly (try to) install them to
>> “/Applications/…” which is completely wrong (and also maybe the case why
>> my built binary doesn’t find them?). Also, the path itself under
>> SharedSupport I guess isn’t right.
>>
>> It also install this here
>> bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
>> total 464
>> drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
>> drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
>> -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17
>> libkicad_3dsg..0.0.dylib
>> lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17 libkicad_3dsg.dylib
>> -> libkicad_3dsg..0.0.dylib
>> which doesn’t look right, what is it good for?
>>
>> If you like, I can have a look and try to fix this.
>>
>>
>> Regards,
>> Bernhard
>>
>>> On 23.02.2016, at 22:21, Cirilo Bernardo >> > wrote:
>>>
>>>
>>>
>>> On Tue, Feb 23, 2016 at 7:37 PM, jp charras >> > wrote:
>>>
>>> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
>>> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh 
>>> >
>>> > wrote:
>>> >
>>> >> Cirilo,
>>> >>
>>> >> I have one last change request that I missed in my previous review.
>>> >> Please change your debugging output method.  Windows apps have no
>>> >> concept of stdout even when run from the command line.  wxLogTrace is
>>> >> the preferred method for debugging output.  It solves two problems.  
>>> The
>>> >> debugging strings are redirected to the correct output on all 
>>> supported
>>> >> platforms and the debugging output is turned off by default.  
>>> Turning on
>>> >> the debugging output is as simple as:
>>> >>
>>> >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
>>> >>
>>> >> The is handy so I don't have to sift through everyone's debugging 
>>> output
>>> >> to find what I'm looking for.  You just need to pick a unique string 
>>> not
>>> >> used by any other kicad wxLogTrace calls to enable tracing of your
>>> >> debugging output.
>>> >>
>>> >>
>>> > The 3d_initial_merge branch has been updated to use wxLogTrace;
>>> > it has also been synchronized to the main branch r6527.  The latest
>>> > revision for the 3d_initial_merge branch is r6527. The branch builds
>>> > successfully and I have tested the previewer with various VRML1/2 and
>>> > X3D models.
>>> >
>>> > - Cirilo
>>>
>>> Thanks, Cirilo.
>>> Very good work.
>>>
>>> At least on Windows, 3d_plugin_manager.cpp is missing the line:
>>> #include 
>>>
>>> Without this include, it does not compile.
>>>
>>> --
>>> Jean-Pierre CHARRAS
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> 
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>> Thanks Jean-Pierre,
>>>
>>>  I have added the header and checked that it builds on Windows (W7-64
>>> bit).
>>>
>>> - Cirilo
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> 
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : 

Re: [Kicad-developers] 3D refactor

[Nick Østergaard]

Ok, I have attached the gdb backtrace if it is of any helpt.

It is very reproduceable for me, but of course, it is "just" an assert for now.

2016-02-24 18:51 GMT+01:00 Mário Luzeiro <mrluze...@ua.pt>:
> Hi NickOe,
> Thanks for trying the branch!
>
> Cirilo is managing that branching. He is "cherry picking" things from my 
> working branch on the renders to get a smooth transition between our branches 
> and trunk
> I guess that is because that cbbox.cpp comes from the new branches and maybe 
> it indicated that something is wrong originally in the stable trunk or 
> something was not proper integrated with that new cbbox.
> It is however a minor issue, since this new cbbox lib have more checks and 
> expect the things more strictly... so maybe it is not an issue at all.
>
> The backtrace does not help since it does not show any function that is using 
> the cbbox :/
> I think if you run it with gdb it will give more precise info if you get the 
> backtrace.
>
> Mario
>
> 
> From: Kicad-developers 
> [kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of 
> Nick Østergaard [oe.n...@gmail.com]
> Sent: 24 February 2016 17:36
> To: Cirilo Bernardo
> Cc: KiCad Developers
> Subject: Re: [Kicad-developers] 3D refactor
>
> Hi Cirilo and Mario,
>
> I just built the 3d_initial_merge branch revno 6528, but I see some
> annoying asserts when running the 3d viewer, not the previewer in the
> 3d properties dialog:
>
> ASSERT INFO:
> /somepath/3d_initial_merge/3d-viewer/3d_rendering/3d_render_raytracing/shapes3D/cbbox.cpp(114):
> assert "aBBox.IsInitialized()" failed in Union().
>
> BACKTRACE:
> [1] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&,
> wxEvent&) const
> [2] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase
> const&, wxEvtHandler*, wxEvent&)
> [3] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
> [4] wxEvtHandler::TryHereOnly(wxEvent&)
> [5] wxEvtHandler::ProcessEventLocally(wxEvent&)
> [6] wxEvtHandler::ProcessEvent(wxEvent&)
> [7] wxEvtHandler::SafelyProcessEvent(wxEvent&)
> [8] wxGLCanvas::OnInternalIdle()
> [9] wxWindowBase::SendIdleEvents(wxIdleEvent&)
> [10] wxWindowBase::SendIdleEvents(wxIdleEvent&)
> [11] wxFrame::SendIdleEvents(wxIdleEvent&)
> [12] wxWindowBase::SendIdleEvents(wxIdleEvent&)
> [13] wxFrame::SendIdleEvents(wxIdleEvent&)
> [14] wxAppBase::ProcessIdle()
> [15] wxApp::DoIdle()
> [16] g_main_context_dispatch
> [17] g_main_loop_run
> [18] gtk_main
> [19] wxGUIEventLoop::DoRun()
> [20] wxEventLoopBase::Run()
> [21] wxAppConsoleBase::MainLoop()
> [22] APP_SINGLE_TOP::OnRun()
> /somepath/3d_initial_merge/common/single_top.cpp:173
> [23] wxEntry(int&, wchar_t**)
> [24] main /somepath/3d_initial_merge/common/single_top.cpp:210
> [25] __libc_start_main
> [26] _start
(gdb) bt
#0  0x74025c39 in raise () from /usr/lib/libpthread.so.0
#1  0x76c6bd10 in wxGUIAppTraits::ShowAssertDialog(wxString const&) () 
from /usr/lib/libwx_gtk2u_core-3.0.so.0
#2  0x763503d2 in ?? () from /usr/lib/libwx_baseu-3.0.so.0
#3  0x76353757 in wxAppConsoleBase::OnAssertFailure(wchar_t const*, 
int, wchar_t const*, wchar_t const*, wchar_t const*) ()
   from /usr/lib/libwx_baseu-3.0.so.0
#4  0x76c2a090 in wxApp::OnAssertFailure(wchar_t const*, int, wchar_t 
const*, wchar_t const*, wchar_t const*) ()
   from /usr/lib/libwx_gtk2u_core-3.0.so.0
#5  0x76353a62 in ?? () from /usr/lib/libwx_baseu-3.0.so.0
#6  0x7634e27a in wxOnAssert(char const*, int, char const*, char 
const*, char const*) () from /usr/lib/libwx_baseu-3.0.so.0
#7  0x7fffe509c913 in CBBOX::Union (this=0x7fffc9b0, aBBox=...)
at 
/somepath/3d_initial_merge/3d-viewer/3d_rendering/3d_render_raytracing/shapes3D/cbbox.cpp:114
#8  0x7fffe50ae94d in EDA_3D_CANVAS::calcBBox (this=0x2213de0) at 
/somepath/3d_initial_merge/3d-viewer/3d_draw.cpp:946
#9  0x7fffe50ae3e8 in EDA_3D_CANVAS::CreateDrawGL_List (this=0x2213de0, 
aErrorMessages=0x7fffcdf0, aActivity=0x7fffcdd0)
at /somepath/3d_initial_merge/3d-viewer/3d_draw.cpp:879
#10 0x7fffe50aca7e in EDA_3D_CANVAS::Redraw (this=0x2213de0) at 
/somepath/3d_initial_merge/3d-viewer/3d_draw.cpp:416
#11 0x7fffe50a9e0a in EDA_3D_CANVAS::OnPaint (this=0x2213de0, event=...) at 
/somepath/3d_initial_merge/3d-viewer/3d_canvas.cpp:526
#12 0x7634c43e in wxAppConsoleBase::CallEventHandler(wxEvtHandler*, 
wxEventFunctor&, wxEvent&) const () from /usr/lib/libwx_baseu-3.0.so.0
#13 0x764d2a77 in 
wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, 
wxEvtHandler*, wxEvent&) () from /usr/lib/libwx_baseu-3.0.so.0

Re: [Kicad-developers] 3D refactor

[Wayne Stambaugh]

Thanks Bernhard,

Before I committed the 3D refactor, I was going to ask our package devs
to take a look at it due to the new 3D model plugins.  I would like to
get this correct before I commit it.  What's the status on windows.
I've built and installed from source and that works find but I'm
guessing our installers will need to be changed to accommodate this.
Once we have the install issues sorted out, I'll commit it.

Cheers,

Wayne

On 2/24/2016 12:26 PM, Bernhard Stegmaier wrote:
> Hi,
> 
> I just tried on OS X and plugin handling doesn’t seem to be OK.
> At least, “make install” does directly (try to) install them to
> “/Applications/…” which is completely wrong (and also maybe the case why
> my built binary doesn’t find them?). Also, the path itself under
> SharedSupport I guess isn’t right.
> 
> It also install this here
> bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
> total 464
> drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
> drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
> -rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17
> libkicad_3dsg..0.0.dylib
> lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17 libkicad_3dsg.dylib
> -> libkicad_3dsg..0.0.dylib
> which doesn’t look right, what is it good for?
> 
> If you like, I can have a look and try to fix this.
> 
> 
> Regards,
> Bernhard
> 
>> On 23.02.2016, at 22:21, Cirilo Bernardo > > wrote:
>>
>>
>>
>> On Tue, Feb 23, 2016 at 7:37 PM, jp charras > > wrote:
>>
>> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
>> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh > >
>> > wrote:
>> >
>> >> Cirilo,
>> >>
>> >> I have one last change request that I missed in my previous review.
>> >> Please change your debugging output method.  Windows apps have no
>> >> concept of stdout even when run from the command line.  wxLogTrace is
>> >> the preferred method for debugging output.  It solves two problems.  
>> The
>> >> debugging strings are redirected to the correct output on all 
>> supported
>> >> platforms and the debugging output is turned off by default.  Turning 
>> on
>> >> the debugging output is as simple as:
>> >>
>> >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
>> >>
>> >> The is handy so I don't have to sift through everyone's debugging 
>> output
>> >> to find what I'm looking for.  You just need to pick a unique string 
>> not
>> >> used by any other kicad wxLogTrace calls to enable tracing of your
>> >> debugging output.
>> >>
>> >>
>> > The 3d_initial_merge branch has been updated to use wxLogTrace;
>> > it has also been synchronized to the main branch r6527.  The latest
>> > revision for the 3d_initial_merge branch is r6527. The branch builds
>> > successfully and I have tested the previewer with various VRML1/2 and
>> > X3D models.
>> >
>> > - Cirilo
>>
>> Thanks, Cirilo.
>> Very good work.
>>
>> At least on Windows, 3d_plugin_manager.cpp is missing the line:
>> #include 
>>
>> Without this include, it does not compile.
>>
>> --
>> Jean-Pierre CHARRAS
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> 
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> Thanks Jean-Pierre,
>>
>>  I have added the header and checked that it builds on Windows (W7-64
>> bit).
>>
>> - Cirilo
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> 
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Mário Luzeiro]

Hi NickOe,
Thanks for trying the branch!

Cirilo is managing that branching. He is "cherry picking" things from my 
working branch on the renders to get a smooth transition between our branches 
and trunk
I guess that is because that cbbox.cpp comes from the new branches and maybe it 
indicated that something is wrong originally in the stable trunk or something 
was not proper integrated with that new cbbox.
It is however a minor issue, since this new cbbox lib have more checks and 
expect the things more strictly... so maybe it is not an issue at all.

The backtrace does not help since it does not show any function that is using 
the cbbox :/
I think if you run it with gdb it will give more precise info if you get the 
backtrace.

Mario


From: Kicad-developers 
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of 
Nick Østergaard [oe.n...@gmail.com]
Sent: 24 February 2016 17:36
To: Cirilo Bernardo
Cc: KiCad Developers
Subject: Re: [Kicad-developers] 3D refactor

Hi Cirilo and Mario,

I just built the 3d_initial_merge branch revno 6528, but I see some
annoying asserts when running the 3d viewer, not the previewer in the
3d properties dialog:

ASSERT INFO:
/somepath/3d_initial_merge/3d-viewer/3d_rendering/3d_render_raytracing/shapes3D/cbbox.cpp(114):
assert "aBBox.IsInitialized()" failed in Union().

BACKTRACE:
[1] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&,
wxEvent&) const
[2] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase
const&, wxEvtHandler*, wxEvent&)
[3] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[4] wxEvtHandler::TryHereOnly(wxEvent&)
[5] wxEvtHandler::ProcessEventLocally(wxEvent&)
[6] wxEvtHandler::ProcessEvent(wxEvent&)
[7] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[8] wxGLCanvas::OnInternalIdle()
[9] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[10] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[11] wxFrame::SendIdleEvents(wxIdleEvent&)
[12] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[13] wxFrame::SendIdleEvents(wxIdleEvent&)
[14] wxAppBase::ProcessIdle()
[15] wxApp::DoIdle()
[16] g_main_context_dispatch
[17] g_main_loop_run
[18] gtk_main
[19] wxGUIEventLoop::DoRun()
[20] wxEventLoopBase::Run()
[21] wxAppConsoleBase::MainLoop()
[22] APP_SINGLE_TOP::OnRun()
/somepath/3d_initial_merge/common/single_top.cpp:173
[23] wxEntry(int&, wchar_t**)
[24] main /somepath/3d_initial_merge/common/single_top.cpp:210
[25] __libc_start_main
[26] _start

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Nick Østergaard]

Hi Cirilo and Mario,

I just built the 3d_initial_merge branch revno 6528, but I see some
annoying asserts when running the 3d viewer, not the previewer in the
3d properties dialog:

ASSERT INFO:
/somepath/3d_initial_merge/3d-viewer/3d_rendering/3d_render_raytracing/shapes3D/cbbox.cpp(114):
assert "aBBox.IsInitialized()" failed in Union().

BACKTRACE:
[1] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&,
wxEvent&) const
[2] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase
const&, wxEvtHandler*, wxEvent&)
[3] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[4] wxEvtHandler::TryHereOnly(wxEvent&)
[5] wxEvtHandler::ProcessEventLocally(wxEvent&)
[6] wxEvtHandler::ProcessEvent(wxEvent&)
[7] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[8] wxGLCanvas::OnInternalIdle()
[9] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[10] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[11] wxFrame::SendIdleEvents(wxIdleEvent&)
[12] wxWindowBase::SendIdleEvents(wxIdleEvent&)
[13] wxFrame::SendIdleEvents(wxIdleEvent&)
[14] wxAppBase::ProcessIdle()
[15] wxApp::DoIdle()
[16] g_main_context_dispatch
[17] g_main_loop_run
[18] gtk_main
[19] wxGUIEventLoop::DoRun()
[20] wxEventLoopBase::Run()
[21] wxAppConsoleBase::MainLoop()
[22] APP_SINGLE_TOP::OnRun()
/somepath/3d_initial_merge/common/single_top.cpp:173
[23] wxEntry(int&, wchar_t**)
[24] main /somepath/3d_initial_merge/common/single_top.cpp:210
[25] __libc_start_main
[26] _start



2016-02-22 1:28 GMT+01:00 Cirilo Bernardo :
> Hi Folks,
>
>  Any thoughts on merging the 3d_initial_merge branch? Between
> mainly Mario and myself and a few reports by others (nickoe,
> reportingsjr) we have sorted out quite a few bugs and other
> deficiencies but I think the only way to get more testing from users
> is to merge the code. I believe that the new parsers all offer much
> better specifications compliance compared to the old parsers and
> the code is more robust. As an example, there is this post by a
> user:
>
> https://forum.kicad.info/t/trouble-with-3d-models-vrml/2320/7
>
>  The user's models, D_Pak.wrl (VRML1) and D_Pakx.wrl (VRML2)
> load and display correctly in the file preview which uses the new
> parsers. In the legacy parsers, D_Pak.wrl causes a segfault and
> D_Pakx.wrl does not display correctly. Note: the 3d_initial_merge
> branch still uses the legacy 3DViewer so the 3DViewer will segfault
> on the D_Pak.wrl model, but for me this only serves as a reminder
> of some of the improvements gained with the new 3D plugin system.
>
> - Cirilo
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Bernhard Stegmaier]

Hi,

I just tried on OS X and plugin handling doesn’t seem to be OK.
At least, “make install” does directly (try to) install them to 
“/Applications/…” which is completely wrong (and also maybe the case why my 
built binary doesn’t find them?). Also, the path itself under SharedSupport I 
guess isn’t right.

It also install this here
bstegmaier$ ls -al /Applications/kicad.app/Contents/Macos/
total 464
drwxr-xr-x  4 bstegmaier  admin 136 24 Feb 18:17 .
drwxr-xr-x  3 bstegmaier  admin 102 24 Feb 18:17 ..
-rwxr-xr-x  1 bstegmaier  admin  231560 24 Feb 18:17 libkicad_3dsg..0.0.dylib
lrwxr-xr-x  1 bstegmaier  admin  24 24 Feb 18:17 libkicad_3dsg.dylib -> 
libkicad_3dsg..0.0.dylib
which doesn’t look right, what is it good for?

If you like, I can have a look and try to fix this.


Regards,
Bernhard

> On 23.02.2016, at 22:21, Cirilo Bernardo  wrote:
> 
> 
> 
> On Tue, Feb 23, 2016 at 7:37 PM, jp charras  > wrote:
> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh  > >
> > wrote:
> >
> >> Cirilo,
> >>
> >> I have one last change request that I missed in my previous review.
> >> Please change your debugging output method.  Windows apps have no
> >> concept of stdout even when run from the command line.  wxLogTrace is
> >> the preferred method for debugging output.  It solves two problems.  The
> >> debugging strings are redirected to the correct output on all supported
> >> platforms and the debugging output is turned off by default.  Turning on
> >> the debugging output is as simple as:
> >>
> >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
> >>
> >> The is handy so I don't have to sift through everyone's debugging output
> >> to find what I'm looking for.  You just need to pick a unique string not
> >> used by any other kicad wxLogTrace calls to enable tracing of your
> >> debugging output.
> >>
> >>
> > The 3d_initial_merge branch has been updated to use wxLogTrace;
> > it has also been synchronized to the main branch r6527.  The latest
> > revision for the 3d_initial_merge branch is r6527. The branch builds
> > successfully and I have tested the previewer with various VRML1/2 and
> > X3D models.
> >
> > - Cirilo
> 
> Thanks, Cirilo.
> Very good work.
> 
> At least on Windows, 3d_plugin_manager.cpp is missing the line:
> #include 
> 
> Without this include, it does not compile.
> 
> --
> Jean-Pierre CHARRAS
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers 
> 
> Post to : kicad-developers@lists.launchpad.net 
> 
> Unsubscribe : https://launchpad.net/~kicad-developers 
> 
> More help   : https://help.launchpad.net/ListHelp 
> 
> 
> Thanks Jean-Pierre,
> 
>  I have added the header and checked that it builds on Windows (W7-64 bit).
> 
> - Cirilo
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

On Tue, Feb 23, 2016 at 7:37 PM, jp charras  wrote:

> Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
> > On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh 
> > wrote:
> >
> >> Cirilo,
> >>
> >> I have one last change request that I missed in my previous review.
> >> Please change your debugging output method.  Windows apps have no
> >> concept of stdout even when run from the command line.  wxLogTrace is
> >> the preferred method for debugging output.  It solves two problems.  The
> >> debugging strings are redirected to the correct output on all supported
> >> platforms and the debugging output is turned off by default.  Turning on
> >> the debugging output is as simple as:
> >>
> >> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
> >>
> >> The is handy so I don't have to sift through everyone's debugging output
> >> to find what I'm looking for.  You just need to pick a unique string not
> >> used by any other kicad wxLogTrace calls to enable tracing of your
> >> debugging output.
> >>
> >>
> > The 3d_initial_merge branch has been updated to use wxLogTrace;
> > it has also been synchronized to the main branch r6527.  The latest
> > revision for the 3d_initial_merge branch is r6527. The branch builds
> > successfully and I have tested the previewer with various VRML1/2 and
> > X3D models.
> >
> > - Cirilo
>
> Thanks, Cirilo.
> Very good work.
>
> At least on Windows, 3d_plugin_manager.cpp is missing the line:
> #include 
>
> Without this include, it does not compile.
>
> --
> Jean-Pierre CHARRAS
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

Thanks Jean-Pierre,

 I have added the header and checked that it builds on Windows (W7-64 bit).

- Cirilo
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[jp charras]

Le 23/02/2016 08:56, Cirilo Bernardo a écrit :
> On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh 
> wrote:
> 
>> Cirilo,
>>
>> I have one last change request that I missed in my previous review.
>> Please change your debugging output method.  Windows apps have no
>> concept of stdout even when run from the command line.  wxLogTrace is
>> the preferred method for debugging output.  It solves two problems.  The
>> debugging strings are redirected to the correct output on all supported
>> platforms and the debugging output is turned off by default.  Turning on
>> the debugging output is as simple as:
>>
>> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
>>
>> The is handy so I don't have to sift through everyone's debugging output
>> to find what I'm looking for.  You just need to pick a unique string not
>> used by any other kicad wxLogTrace calls to enable tracing of your
>> debugging output.
>>
>>
> The 3d_initial_merge branch has been updated to use wxLogTrace;
> it has also been synchronized to the main branch r6527.  The latest
> revision for the 3d_initial_merge branch is r6527. The branch builds
> successfully and I have tested the previewer with various VRML1/2 and
> X3D models.
> 
> - Cirilo

Thanks, Cirilo.
Very good work.

At least on Windows, 3d_plugin_manager.cpp is missing the line:
#include 

Without this include, it does not compile.

-- 
Jean-Pierre CHARRAS

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh 
wrote:

> Cirilo,
>
> I have one last change request that I missed in my previous review.
> Please change your debugging output method.  Windows apps have no
> concept of stdout even when run from the command line.  wxLogTrace is
> the preferred method for debugging output.  It solves two problems.  The
> debugging strings are redirected to the correct output on all supported
> platforms and the debugging output is turned off by default.  Turning on
> the debugging output is as simple as:
>
> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
>
> The is handy so I don't have to sift through everyone's debugging output
> to find what I'm looking for.  You just need to pick a unique string not
> used by any other kicad wxLogTrace calls to enable tracing of your
> debugging output.
>
>
The 3d_initial_merge branch has been updated to use wxLogTrace;
it has also been synchronized to the main branch r6527.  The latest
revision for the 3d_initial_merge branch is r6527. The branch builds
successfully and I have tested the previewer with various VRML1/2 and
X3D models.

- Cirilo



> I'm still not thrilled about using a list of paths to search for 3D
> model files.  This is broken in the same way the the component library
> search path ordering is broken in Eeschema.  Since it's no worse than
> what we have now and fixes some of the current 3D model file loading
> issues, I'm willing to commit it but in the long run I think we really
> need to think about this more carefully and come up with a better way to
> resolve 3D model file names.
>
> Cheers,
>
> Wayne
>
> On 2/21/2016 7:28 PM, Cirilo Bernardo wrote:
> > Hi Folks,
> >
> >  Any thoughts on merging the 3d_initial_merge branch? Between
> > mainly Mario and myself and a few reports by others (nickoe,
> > reportingsjr) we have sorted out quite a few bugs and other
> > deficiencies but I think the only way to get more testing from users
> > is to merge the code. I believe that the new parsers all offer much
> > better specifications compliance compared to the old parsers and
> > the code is more robust. As an example, there is this post by a
> > user:
> >
> > https://forum.kicad.info/t/trouble-with-3d-models-vrml/2320/7
> >
> >  The user's models, D_Pak.wrl (VRML1) and D_Pakx.wrl (VRML2)
> > load and display correctly in the file preview which uses the new
> > parsers. In the legacy parsers, D_Pak.wrl causes a segfault and
> > D_Pakx.wrl does not display correctly. Note: the 3d_initial_merge
> > branch still uses the legacy 3DViewer so the 3DViewer will segfault
> > on the D_Pak.wrl model, but for me this only serves as a reminder
> > of some of the improvements gained with the new 3D plugin system.
> >
> > - Cirilo
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[easyw]

just to let you know there are some kicad's users asking for what I 
suggested


1) pivot center of rotation
https://forum.kicad.info/t/3d-new-library-for-mechanical-cad-exporting-and-enclosure-design/1763/20

2) show/hide enclosures
https://forum.kicad.info/t/3d-new-library-for-mechanical-cad-exporting-and-enclosure-design/1763/33

Regards
Maurice

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

On Tue, Feb 23, 2016 at 3:00 AM, Wayne Stambaugh 
wrote:

> Cirilo,
>
> I have one last change request that I missed in my previous review.
> Please change your debugging output method.  Windows apps have no
> concept of stdout even when run from the command line.  wxLogTrace is
> the preferred method for debugging output.  It solves two problems.  The
> debugging strings are redirected to the correct output on all supported
> platforms and the debugging output is turned off by default.  Turning on
> the debugging output is as simple as:
>
> export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"
>
> The is handy so I don't have to sift through everyone's debugging output
> to find what I'm looking for.  You just need to pick a unique string not
> used by any other kicad wxLogTrace calls to enable tracing of your
> debugging output.
>

No problem, I'll get to work on that.

- Cirilo


>
> I'm still not thrilled about using a list of paths to search for 3D
> model files.  This is broken in the same way the the component library
> search path ordering is broken in Eeschema.  Since it's no worse than
> what we have now and fixes some of the current 3D model file loading
> issues, I'm willing to commit it but in the long run I think we really
> need to think about this more carefully and come up with a better way to
> resolve 3D model file names.
>
> Cheers,
>
> Wayne
>
> On 2/21/2016 7:28 PM, Cirilo Bernardo wrote:
> > Hi Folks,
> >
> >  Any thoughts on merging the 3d_initial_merge branch? Between
> > mainly Mario and myself and a few reports by others (nickoe,
> > reportingsjr) we have sorted out quite a few bugs and other
> > deficiencies but I think the only way to get more testing from users
> > is to merge the code. I believe that the new parsers all offer much
> > better specifications compliance compared to the old parsers and
> > the code is more robust. As an example, there is this post by a
> > user:
> >
> > https://forum.kicad.info/t/trouble-with-3d-models-vrml/2320/7
> >
> >  The user's models, D_Pak.wrl (VRML1) and D_Pakx.wrl (VRML2)
> > load and display correctly in the file preview which uses the new
> > parsers. In the legacy parsers, D_Pak.wrl causes a segfault and
> > D_Pakx.wrl does not display correctly. Note: the 3d_initial_merge
> > branch still uses the legacy 3DViewer so the 3DViewer will segfault
> > on the D_Pak.wrl model, but for me this only serves as a reminder
> > of some of the improvements gained with the new 3D plugin system.
> >
> > - Cirilo
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Wayne Stambaugh]

Cirilo,

I have one last change request that I missed in my previous review.
Please change your debugging output method.  Windows apps have no
concept of stdout even when run from the command line.  wxLogTrace is
the preferred method for debugging output.  It solves two problems.  The
debugging strings are redirected to the correct output on all supported
platforms and the debugging output is turned off by default.  Turning on
the debugging output is as simple as:

export WXTRACE="SOME_DEBUGGING_OUTPUT_TO_ENABLE"

The is handy so I don't have to sift through everyone's debugging output
to find what I'm looking for.  You just need to pick a unique string not
used by any other kicad wxLogTrace calls to enable tracing of your
debugging output.

I'm still not thrilled about using a list of paths to search for 3D
model files.  This is broken in the same way the the component library
search path ordering is broken in Eeschema.  Since it's no worse than
what we have now and fixes some of the current 3D model file loading
issues, I'm willing to commit it but in the long run I think we really
need to think about this more carefully and come up with a better way to
resolve 3D model file names.

Cheers,

Wayne

On 2/21/2016 7:28 PM, Cirilo Bernardo wrote:
> Hi Folks,
> 
>  Any thoughts on merging the 3d_initial_merge branch? Between
> mainly Mario and myself and a few reports by others (nickoe,
> reportingsjr) we have sorted out quite a few bugs and other
> deficiencies but I think the only way to get more testing from users
> is to merge the code. I believe that the new parsers all offer much
> better specifications compliance compared to the old parsers and
> the code is more robust. As an example, there is this post by a
> user:
> 
> https://forum.kicad.info/t/trouble-with-3d-models-vrml/2320/7
> 
>  The user's models, D_Pak.wrl (VRML1) and D_Pakx.wrl (VRML2)
> load and display correctly in the file preview which uses the new
> parsers. In the legacy parsers, D_Pak.wrl causes a segfault and
> D_Pakx.wrl does not display correctly. Note: the 3d_initial_merge
> branch still uses the legacy 3DViewer so the 3DViewer will segfault
> on the D_Pak.wrl model, but for me this only serves as a reminder
> of some of the improvements gained with the new 3D plugin system.
> 
> - Cirilo
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[easyw]

Hi Cirilo,
I tested Mario branch and I found something that I think it would be 
nice to implement:


1) 3d-viewer 'Fit in Page' option doesn't fit correctly the board and 
moreover resets the zoom, but not the board orientation (as it is done 
in standard kicad 3d-viewer)

2) 3d-viewer-Render Option-Render material Properties
   doesn't work
I think is still an useful option because of the following reasons:
  a) a lot of 3d-models in official libs (not mine 3D MCAD libs) have 
bad material properties, so not implementing this feature will give you 
a lot of 'rumors' from kicad users
  b) when inspecting a board in 3d-viewer I don't like been 'flashed' 
from pads and pins reflex ... properties are useful only to get a 
realistic screenshot of the board and parts
  c) as I already mailed to Mario, disable material properties could be 
*very* useful for toggle the visibility of e.g. enclosure objects
  if you put an enclosure transparency value to 100%, it will not be 
displayed if material properties are on, but it will appear if the 
material properties are off... that will give kicad the ability to 
switch ON/OFF enclosure for a better mechanical design (ability that 
Altium has)
3) pivot center of rotation: it would be nice/necessary to add a pivot 
center of rotation for board an parts (as it is available in most (E)CAD 
sw) to let user to inspect objects on the perimeter of the board (option 
much more necessary when the board it is not small)

use zoom 'Fit in Page' to reset the pivot

Regards
Maurice


On 22/02/2016 01.28, Cirilo Bernardo wrote:

Hi Folks,

  Any thoughts on merging the 3d_initial_merge branch? Between
mainly Mario and myself and a few reports by others (nickoe,
reportingsjr) we have sorted out quite a few bugs and other
deficiencies but I think the only way to get more testing from users
is to merge the code. I believe that the new parsers all offer much
better specifications compliance compared to the old parsers and
the code is more robust. As an example, there is this post by a
user:

https://forum.kicad.info/t/trouble-with-3d-models-vrml/2320/7

  The user's models, D_Pak.wrl (VRML1) and D_Pakx.wrl (VRML2)
load and display correctly in the file preview which uses the new
parsers. In the legacy parsers, D_Pak.wrl causes a segfault and
D_Pakx.wrl does not display correctly. Note: the 3d_initial_merge
branch still uses the legacy 3DViewer so the 3DViewer will segfault
on the D_Pak.wrl model, but for me this only serves as a reminder
of some of the improvements gained with the new 3D plugin system.

- Cirilo



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor 3D model path: dropped env vars?

[Mário Luzeiro]

Nice!

"now I can test the models in the new 3D environment :)"

In relation to the openGL render mode, you should expect similar results. There 
are still things missing and some tweaks need, but visually it should be 
similar.
(supposing you choose in current kicad to use model materials and choose to NOT 
use model normals)

On Raytracing render mode, the materials differences are more noticeable. You 
will experience a "per pixel" shading and materials will play a big deal on 
that. Special the shininess and transparency. The transparency will make the 
material with refractable capabilities  and shininess (big values) will make 
the material reflective.

Have fun!
Mario

From: easyw [ea...@katamail.com]
Sent: 16 February 2016 23:26
To: Cirilo Bernardo; KiCad Developers
Cc: Mário Luzeiro
Subject: Re: [Kicad-developers] 3D refactor 3D model path: dropped env vars?

thanks Cirilo and Mario,
after having moved
libs3d_plugin_idf.dll, libs3d_plugin_vrml.dll in the dir bin/plugins/3d
dir everything became fine! :)

now I can test the models in the new 3D environment :)

keep in touch
Maurice
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor 3D model path: dropped env vars?

[Mário Luzeiro]

Hi Maurice, thanks for trying it !

Cirilo can give more details, but because of the 3D plugins, you have to 
build.. and install it.
I am testing in on Windows once in a while, building it on a MSYS2
I run 'make install -j4'
and run kicad

I got help on IRC from nickoe (thanks!) on setup and running this on Windows 
and Linux.

On linux I am using the following:
make DESTDIR=/tmp/kicad install -j7
LD_LIBRARY_PATH=/tmp/kicad/usr/local/lib:$LD_LIBRARY_PATH 
/tmp/kicad/usr/local/bin/pcbnew

but on windows MSYS2 this is not need for me...

Mario Luzeiro


From: Kicad-developers 
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of 
easyw [ea...@katamail.com]
Sent: 16 February 2016 22:26
To: Cirilo Bernardo
Cc: KiCad Developers
Subject: Re: [Kicad-developers] 3D refactor 3D model path: dropped env vars?

Hi Cirilo and Mario,
thank you for your reply ...
I'm testing the new 3D refactoring, built from this repo
https://code.launchpad.net/~mrluzeiro/kicad/kicad_new3d-viewer
in windows 8/64b
what I'm experiencing is that I cannot display any 3D model at all...
I tried also with an absolute path, and I also don't have any model
displayed on the preview...
I can see the board and tracks in 3d-viewer both on OpenGL and in
Raytracing, but nope for 3D models ...
Is there anyone that has tested that in windows?
If I build the standard bzr6558 everything goes fine

thank you for feedback
Maurice


On 16/02/2016 22.43, Cirilo Bernardo wrote:
> Hi Maurice,
>
>   For legacy support ${KISYS3DMOD} is magically and invisibly supported
> by the filename resolver. The resolver will also correctly resolve any
> path specified like ${ENV_VAR}/some/path.  However, once the new 3D
> plugin code is merged I would discourage any future use of ${KISYS3DMOD}
> and ${KIPRJMOD} in the names of files - these will still work but in my
> opinion is a bad habit and will work against the filename resolver's
> concept to eliminate environment variables in filename resolution and to
> use a configurable text file to store root paths instead.
>
>   The ${KIPRJMOD} in fact does not need to be specified at all and can
> be completely removed from names. By default the filename resolver will
> attempt to resolve partial paths by checking in the current project
> directory first. This was done as part of the plan to ensure better
> portability of a project directory.
>
> - Cirilo
>
>
> On Wed, Feb 17, 2016 at 6:46 AM, easyw <ea...@katamail.com
> <mailto:ea...@katamail.com>> wrote:
>
> have the environment variables
> ${KIPRJMOD}
> ${KISYS3DMOD}
> been dropped by the new 3D refactoring?
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> <mailto:kicad-developers@lists.launchpad.net>
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor 3D model path: dropped env vars?

[easyw]

Hi Cirilo and Mario,
thank you for your reply ...
I'm testing the new 3D refactoring, built from this repo
https://code.launchpad.net/~mrluzeiro/kicad/kicad_new3d-viewer
in windows 8/64b
what I'm experiencing is that I cannot display any 3D model at all...
I tried also with an absolute path, and I also don't have any model 
displayed on the preview...
I can see the board and tracks in 3d-viewer both on OpenGL and in 
Raytracing, but nope for 3D models ...

Is there anyone that has tested that in windows?
If I build the standard bzr6558 everything goes fine

thank you for feedback
Maurice


On 16/02/2016 22.43, Cirilo Bernardo wrote:

Hi Maurice,

  For legacy support ${KISYS3DMOD} is magically and invisibly supported
by the filename resolver. The resolver will also correctly resolve any
path specified like ${ENV_VAR}/some/path.  However, once the new 3D
plugin code is merged I would discourage any future use of ${KISYS3DMOD}
and ${KIPRJMOD} in the names of files - these will still work but in my
opinion is a bad habit and will work against the filename resolver's
concept to eliminate environment variables in filename resolution and to
use a configurable text file to store root paths instead.

  The ${KIPRJMOD} in fact does not need to be specified at all and can
be completely removed from names. By default the filename resolver will
attempt to resolve partial paths by checking in the current project
directory first. This was done as part of the plan to ensure better
portability of a project directory.

- Cirilo


On Wed, Feb 17, 2016 at 6:46 AM, easyw > wrote:

have the environment variables
${KIPRJMOD}
${KISYS3DMOD}
been dropped by the new 3D refactoring?

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net

Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor 3D model path: dropped env vars?

[Cirilo Bernardo]

Hi Maurice,

 For legacy support ${KISYS3DMOD} is magically and invisibly supported by
the filename resolver. The resolver will also correctly resolve any path
specified like ${ENV_VAR}/some/path.  However, once the new 3D plugin code
is merged I would discourage any future use of ${KISYS3DMOD} and
${KIPRJMOD} in the names of files - these will still work but in my opinion
is a bad habit and will work against the filename resolver's concept to
eliminate environment variables in filename resolution and to use a
configurable text file to store root paths instead.

 The ${KIPRJMOD} in fact does not need to be specified at all and can be
completely removed from names. By default the filename resolver will
attempt to resolve partial paths by checking in the current project
directory first. This was done as part of the plan to ensure better
portability of a project directory.

- Cirilo


On Wed, Feb 17, 2016 at 6:46 AM, easyw  wrote:

> have the environment variables
> ${KIPRJMOD}
> ${KISYS3DMOD}
> been dropped by the new 3D refactoring?
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor 3D model path: dropped env vars?

[Mário Luzeiro]

Hi Maurice,

Cirilo will be the best person to reply.
I know that the KISYS3DMOD is working for me...

I dont know about KIPRJMOD (on relation of 3d models plugins) but I guess there 
is no change on that since the rest of the source code is the same as the 
trunk. ( I checked and it is used by the sources)

Mario

From: Kicad-developers 
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of 
easyw [ea...@katamail.com]
Sent: 16 February 2016 19:46
To: KiCad Developers
Subject: [Kicad-developers] 3D refactor 3D model path: dropped env vars?

have the environment variables
${KIPRJMOD}
${KISYS3DMOD}
been dropped by the new 3D refactoring?

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor update

[Mário Luzeiro]

Hi,

For a) I think for this cache mechanisms there should be some way to versioning 
the files or folders or what.. so it will be automatically possible to the 
application to delete that files.
A possibility would be to hash the file with his own version, so a future 
version will create a different hash.. and maybe there is need for a size limit 
of the folder..

Just some ideas..

Mario


From: Kicad-developers 
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of 
Clemens Koller [c...@embeon.de]
Sent: 18 January 2016 11:06
To: kicad-developers@lists.launchpad.net
Subject: Re: [Kicad-developers] 3D refactor update

Hello, Cirilo!

On 2016-01-18 09:59, Cirilo Bernardo wrote:
>  I have reworked the new 3D code and would appreciate some testing/feedback
>  Those who have tried previous versions will need to:
> a. delete all cache files (in the kicad config. directory under 3d/cache) and
> b. delete the older 3D search path list (in the kicad config. dir 
> 3d/3Dresolver.cfg)

What happens if somebody forgets to delete these files upfront?
Are these two steps also necessary in the production version later on?

Regards,

Clemens

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor update

[Bernhard Stegmaier]

Hi,

I didn’t try(check it, so maybe just dumb questions:
What is the difference between the cached and original files?
I guess most of the time the config folder will be on the same storage as the 
original files (== home folder), so what’s the point of copying them to a cache 
folder?
It would probably make sense to be able to configure the cache folder (or use 
sth like $XDG_CACHE_HOME), so it could be directed to e.g. a tmpfs in RAM.


Regards,
Bernhard

> On 18 Jan 2016, at 19:02, Mário Luzeiro <mrluze...@ua.pt> wrote:
> 
> Hi,
> 
> For a) I think for this cache mechanisms there should be some way to 
> versioning the files or folders or what.. so it will be automatically 
> possible to the application to delete that files.
> A possibility would be to hash the file with his own version, so a future 
> version will create a different hash.. and maybe there is need for a size 
> limit of the folder..
> 
> Just some ideas..
> 
> Mario
> 
> 
> From: Kicad-developers 
> [kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of 
> Clemens Koller [c...@embeon.de]
> Sent: 18 January 2016 11:06
> To: kicad-developers@lists.launchpad.net
> Subject: Re: [Kicad-developers] 3D refactor update
> 
> Hello, Cirilo!
> 
> On 2016-01-18 09:59, Cirilo Bernardo wrote:
>> I have reworked the new 3D code and would appreciate some testing/feedback
>> Those who have tried previous versions will need to:
>> a. delete all cache files (in the kicad config. directory under 3d/cache) and
>> b. delete the older 3D search path list (in the kicad config. dir 
>> 3d/3Dresolver.cfg)
> 
> What happens if somebody forgets to delete these files upfront?
> Are these two steps also necessary in the production version later on?
> 
> Regards,
> 
> Clemens
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor update

[Clemens Koller]

Hello, Cirilo!

On 2016-01-18 09:59, Cirilo Bernardo wrote:
>  I have reworked the new 3D code and would appreciate some testing/feedback
>  Those who have tried previous versions will need to:
> a. delete all cache files (in the kicad config. directory under 3d/cache) and
> b. delete the older 3D search path list (in the kicad config. dir 
> 3d/3Dresolver.cfg)

What happens if somebody forgets to delete these files upfront?
Are these two steps also necessary in the production version later on?

Regards,

Clemens

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor update

[Cirilo Bernardo]

I've made a number of bug fixes; the latest version committed is 6462.

- Cirilo

On Mon, Jan 18, 2016 at 7:59 PM, Cirilo Bernardo 
wrote:

> Hi folks,
>
>  I have reworked the new 3D code and would appreciate some testing/feedback
> on the 3D path configuration and name resolution. This is (hopefully) the
> last
> hurdle before merging the code with the main branch, which in turn will be
> the
> first step towards implementing the new 3D Viewer.
>
>  Those who have tried previous versions will need to:
> a. delete all cache files (in the kicad config. directory under 3d/cache)
> and
> b. delete the older 3D search path list (in the kicad config. dir
> 3d/3Dresolver.cfg)
>
>  All existing projects should be able to locate and render their VRML
> models;
> X3D models are not yet supported (the code hasn't been converted to a
> plugin
> module yet) but from feedback I have received, X3D models are not commonly
> used.
>
> bazaar.launchpad.net/~cirilo-bernardo/kicad/3d_initial_merge
>
> - Cirilo
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor update (segfaults here)

[Clemens Koller]

Hi, Cirilo!

> Perhaps a debug build would help. From the backtrace it's not obvious to me
> where the problem might be; it seems to be unrelated to the code changes
> which I made.
> If there's a possibility that the code is being linked to other existing
> libraries, try running 'ldd' on kicad/pcbnew and checking that the linker
> is pointing to the expected instance of the library.
> Thanks for trying the code; reports like these are always helpful.
> - Cirilo

I'll do my very best.

-DCMAKE_BUILD_TYPE=Debug added.

It seems like libkicad_3dsg.so.1.0.0 doesn't get installed to the
correct directory?!
It's in ~/SW/lib and not in ~/SW/lib/kicad/ where I would expect it.
You know, I am installing kicad as user. An ls -laR output of my
installation target ~/SW is attached.

The crash reporter of pcbnew, when run directly, complains:

$ ./pcbnew
LIB_ENV_VAR:'/home/admin/SW/bin:/opt/opencascade/lib'
00:43:56: Debug: Adding locale lookup path: /usr/local/share/kicad/internat
ElemsClear: clearing all _ELEMS for project 

-- crash log.txt -
00:23:43: libkicad_3dsg.so.1.0.0: cannot open shared object file: No such file 
or directory
00:23:43: IO_ERROR: Fatal Installation Bug. File:
'/home/admin/SW/bin/_pcbnew.kiface'
could not be loaded
Perhaps a shared library (.dll or .so) file is missing.
>From command line: argv[0]:
'/home/admin/SW/bin/pcbnew'

from kiway.cpp : KiFACE() : line 225
the file '/home/admin/SW/bin/_pcbnew.kiface' is where it's supposed to be.
- 8< -


Anyway, kicad should not crash with a segfault
when pcbnew is running into troubles:

$ gdb ./kicad 
GNU gdb (GDB) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./kicad...done.
(gdb) run
Starting program: /home/admin/SW/bin/kicad 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
LIB_ENV_VAR:'/home/admin/SW/bin:/opt/opencascade/lib'
00:42:11: Debug: Adding locale lookup path: /usr/local/share/kicad/internat
ElemsClear: clearing all _ELEMS for project 
SetProjectFullName: old:'' 
new:'/home/admin/share/project/kicad-4/pro/test2/Test2.pro'
00:42:11: Debug: Test2.pro: noname.pro
[New Thread 0x7fffe7583700 (LWP 2189)]
[New Thread 0x7fffe6d82700 (LWP 2190)]
FileWatcherReset: watched paths:
 /home/admin/share/project/kicad-4/pro/test2/

Program received signal SIGSEGV, Segmentation fault.
0x731488c0 in ?? () from /usr/lib/libgobject-2.0.so.0
(gdb) bt
#0  0x731488c0 in ?? () from /usr/lib/libgobject-2.0.so.0
#1  0x73151dfc in g_signal_emit_valist () from 
/usr/lib/libgobject-2.0.so.0
#2  0x7315212f in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#3  0x73785e00 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#4  0x7313d7b8 in g_object_run_dispose () from 
/usr/lib/libgobject-2.0.so.0
#5  0x736e5f7f in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#6  0x73137015 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#7  0x7314957e in ?? () from /usr/lib/libgobject-2.0.so.0
#8  0x73151dfc in g_signal_emit_valist () from 
/usr/lib/libgobject-2.0.so.0
#9  0x7315212f in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#10 0x73785e00 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#11 0x7313d7b8 in g_object_run_dispose () from 
/usr/lib/libgobject-2.0.so.0
#12 0x76cbc840 in wxButtonBase::GetDefaultSize() () from 
/usr/lib/libwx_gtk2u_core-3.0.so.0
#13 0x76cbc89a in wxButton::DoGetBestSize() const () from 
/usr/lib/libwx_gtk2u_core-3.0.so.0
#14 0x76e5c219 in wxWindowBase::GetBestSize() const () from 
/usr/lib/libwx_gtk2u_core-3.0.so.0
#15 0x76e5c348 in wxWindowBase::GetEffectiveMinSize() const () from 
/usr/lib/libwx_gtk2u_core-3.0.so.0
#16 0x76e5c440 in wxWindowBase::SetInitialSize(wxSize const&) () from 
/usr/lib/libwx_gtk2u_core-3.0.so.0
#17 0x76cbc60e in wxButton::Create(wxWindow*, int, wxString const&, 
wxPoint const&, wxSize const&, long, wxValidator const&, wxString const&) () 
from /usr/lib/libwx_gtk2u_core-3.0.so.0
#18 0x76ea6d3d in ?? () from /usr/lib/libwx_gtk2u_core-3.0.so.0
#19 0x76ea7d41 in wxLogGui::DoShowMultipleLogMessages(wxArrayString 
const&, wxArrayInt const&, wxArrayLong const&, wxString const&, int) () from 
/usr/lib/libwx_gtk2u_core-3.0.so.0

Re: [Kicad-developers] 3D refactor update

[Mário Luzeiro]

Hi Clemens,

I think I may be related with that issue in Cirilo branch as I am working on 
render.

This need investigation. I know what it is related but I dont know how to solve 
it at this moment. 
This looks like because wxWidgets decide in some situations to ask to redraw 
twice on the first time it shows the windows.
So .. if I remember I managed to remove what it causes to render twice the 
first time..
but.. maybe that was some workarround to cases like your issue.

I will check what I did and revert it or try get a solution for that... then I 
will ask you for testing :)

Mario


From: Kicad-developers 
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of 
Clemens Koller [c...@embeon.de]
Sent: 19 January 2016 01:24
To: kicad-developers@lists.launchpad.net
Subject: Re: [Kicad-developers] 3D refactor update

Testing bzr6462:

Hrmm... after ignoring the asserts now, I get some destroyed
3D content when the 3D viewer opens until I start to move the view.
This happens only on the very first start after installation.

Before bzr6462 I was able to see the 3D view correctly / as usual
straight from start, IIRC.

Regression?

I will call it a day for today and enter sleep mode.

Clemens


On 2016-01-19 01:34, Cirilo Bernardo wrote:
> I've made a number of bug fixes; the latest version committed is 6462.
>
> - Cirilo
>
> On Mon, Jan 18, 2016 at 7:59 PM, Cirilo Bernardo <cirilo.berna...@gmail.com 
> <mailto:cirilo.berna...@gmail.com>> wrote:
>
> Hi folks,
>
>  I have reworked the new 3D code and would appreciate some 
> testing/feedback
> on the 3D path configuration and name resolution. This is (hopefully) the 
> last
> hurdle before merging the code with the main branch, which in turn will 
> be the
> first step towards implementing the new 3D Viewer.
>
>  Those who have tried previous versions will need to:
> a. delete all cache files (in the kicad config. directory under 3d/cache) 
> and
> b. delete the older 3D search path list (in the kicad config. dir 
> 3d/3Dresolver.cfg)
>
>  All existing projects should be able to locate and render their VRML 
> models;
> X3D models are not yet supported (the code hasn't been converted to a 
> plugin
> module yet) but from feedback I have received, X3D models are not commonly
> used.
>
> bazaar.launchpad.net/~cirilo-bernardo/kicad/3d_initial_merge 
> <http://bazaar.launchpad.net/~cirilo-bernardo/kicad/3d_initial_merge>
>
> - Cirilo
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor update

[Bernhard Stegmaier]

OK, understood… thanks!


Regards,
Bernhard

> On 18 Jan 2016, at 21:35, Cirilo Bernardo <cirilo.berna...@gmail.com> wrote:
> 
> On Tue, Jan 19, 2016 at 5:14 AM, Bernhard Stegmaier <stegma...@sw-systems.de 
> <mailto:stegma...@sw-systems.de>> wrote:
> Hi,
> 
> I didn’t try(check it, so maybe just dumb questions:
> What is the difference between the cached and original files?
> I guess most of the time the config folder will be on the same storage as the 
> original files (== home folder), so what’s the point of copying them to a 
> cache folder?
> It would probably make sense to be able to configure the cache folder (or use 
> sth like $XDG_CACHE_HOME), so it could be directed to e.g. a tmpfs in RAM.
> 
> 
> The cache files are a binary format and are an intermediate data 
> representation.
> The existing scheme for 3D models is to parse them and put data into an
> S3D_MASTER object. The translated data is not suitable for caching and
> each instance of the same model file takes up more and more memory.
> With the intermediate format each model is loaded only once so less memory
> is used. In foreseeable future cases the intermediate format will also make
> the subsequent model load times much faster in cases where creating the
> display data is a compute-intensive operation, for example with rendering
> MCAD data. The intermediate representation also means that each 3D
> model plugin must translate to this one common data format which is
> understood by the cache system; this also makes it possible to implement
> a VRML output without much additional code since there is now a single
> point of translation from intermediate format to VRML. In the legacy scheme
> this would have been very messy to implement with each parser
> implementing its own translator and VRML export routines - the parsers would
> essentially be translating the model twice (once to S3D_MASTER then again
> to VRML).
> 
> The cache file also speeds up model loading because it stores its own
> computed normals. In our collection of VRML models I have noticed that
> in the majority of cases there is either no normals data or the normals
> data is bad. In the 3D plugin implementation all normals are calculated;
> at this point I can't think of a scheme to select between calculated and
> in-model normals on a per-model basis. Perhaps we can make such a
> refinement in the future.
> 
> You can always link your cache directory to a RAMFS if you wish.
> 
> - Cirilo
>  
> 
> Regards,
> Bernhard
> 
> > On 18 Jan 2016, at 19:02, Mário Luzeiro <mrluze...@ua.pt 
> > <mailto:mrluze...@ua.pt>> wrote:
> >
> > Hi,
> >
> > For a) I think for this cache mechanisms there should be some way to 
> > versioning the files or folders or what.. so it will be automatically 
> > possible to the application to delete that files.
> > A possibility would be to hash the file with his own version, so a future 
> > version will create a different hash.. and maybe there is need for a size 
> > limit of the folder..
> >
> > Just some ideas..
> >
> > Mario
> >
> > 
> > From: Kicad-developers 
> > [kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net 
> > <mailto:ua...@lists.launchpad.net>] on behalf of Clemens Koller 
> > [c...@embeon.de <mailto:c...@embeon.de>]
> > Sent: 18 January 2016 11:06
> > To: kicad-developers@lists.launchpad.net 
> > <mailto:kicad-developers@lists.launchpad.net>
> > Subject: Re: [Kicad-developers] 3D refactor update
> >
> > Hello, Cirilo!
> >
> > On 2016-01-18 09:59, Cirilo Bernardo wrote:
> >> I have reworked the new 3D code and would appreciate some testing/feedback
> >> Those who have tried previous versions will need to:
> >> a. delete all cache files (in the kicad config. directory under 3d/cache) 
> >> and
> >> b. delete the older 3D search path list (in the kicad config. dir 
> >> 3d/3Dresolver.cfg)
> >
> > What happens if somebody forgets to delete these files upfront?
> > Are these two steps also necessary in the production version later on?
> >
> > Regards,
> >
> > Clemens
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers 
> > <https://launchpad.net/~kicad-developers>
> > Post to : kicad-developers@lists.launchpad.net 
> > <mailto:kicad-developers@lists.launchpad.net>
> > Unsubscribe : https://launchpad.net/~kicad-developers 
> > <https://launchpad.net/~kicad-developers>
> > More help   : ht

Re: [Kicad-developers] 3D refactor update (segfaults here)

[Nick Østergaard]

FWIW, on my archlinux machine it seems to run fine. This is 6459 on
Cirilo's branch.

2016-01-18 23:06 GMT+01:00 Cirilo Bernardo :
> Hi Clemens,
>
>  Perhaps a debug build would help.  From the backtrace it's not obvious to
> me
> where the problem might be; it seems to be unrelated to the code changes
> which I made.
>
>  If there's a possibility that the code is being linked to other existing
> libraries, try running 'ldd' on kicad/pcbnew and checking that the linker
> is pointing to the expected instance of the library.
>
>  Thanks for trying the code; reports like these are always helpful.
>
> - Cirilo
>
>
> On Tue, Jan 19, 2016 at 8:17 AM, Clemens Koller  wrote:
>>
>> Hi, Cirilo
>>
>> On 2016-01-18 09:59, Cirilo Bernardo wrote:
>> >  I have reworked the new 3D code and would appreciate some
>> > testing/feedback
>> > on the 3D path configuration and name resolution. This is (hopefully)
>> > the last
>> > hurdle before merging the code with the main branch, which in turn will
>> > be the
>> > first step towards implementing the new 3D Viewer.
>> >
>> >  Those who have tried previous versions will need to:
>> > a. delete all cache files (in the kicad config. directory under
>> > 3d/cache) and
>> > b. delete the older 3D search path list (in the kicad config. dir
>> > 3d/3Dresolver.cfg)
>> >
>> >  All existing projects should be able to locate and render their VRML
>> > models;
>> > X3D models are not yet supported (the code hasn't been converted to a
>> > plugin
>> > module yet) but from feedback I have received, X3D models are not
>> > commonly
>> > used.
>> >
>> > bazaar.launchpad.net/~cirilo-bernardo/kicad/3d_initial_merge
>> > 
>>
>>
>> As you know, I am usually on the git side, but since you asked
>> politely, I branched your 3d_initial_merge to give it a try... ;-)
>>
>> So I do my usual:
>> $ bzr clone
>> http://bazaar.launchpad.net/~cirilo-bernardo/kicad/3d_initial_merge
>> $ cd 3d_initial_merge
>> $ rm -r build
>> $ mkdir -p build/release
>> $ cd build/release
>> $ cmake -DCMAKE_INSTALL_PREFIX=~/SW \
>> -DDEFAULT_INSTALL_PATH=~/SW \
>> -DKICAD_SKIP_BOOST=ON \
>> -DKICAD_SCRIPTING=ON \
>> -DKICAD_SCRIPTING_MODULES=ON \
>> -DKICAD_SCRIPTING_WXPYTHON=ON \
>> ../../
>> $ make -j8
>> $ make install
>>
>> ... seems to compile fine and gets installed as usual.
>>
>> An optional:
>> $ rm -r ~/.config/kicad
>> made sure, we start from scratch, but without any effect.
>>
>> $ cd ~/SW/bin
>> $ PYTHONPATH=~/SW/lib/python2.7/site-packages/ ./kicad
>>
>> runs kicad, but I get a segfault when I open pcbnew or
>> the footprint editor by clicking on the buttons.
>>
>> Details:
>> $ gdb ./kicad
>> GNU gdb (GDB) 7.10.1
>> Copyright (C) 2015 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later
>> 
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
>> and "show warranty" for details.
>> This GDB was configured as "x86_64-unknown-linux-gnu".
>> Type "show configuration" for configuration details.
>> For bug reporting instructions, please see:
>> .
>> Find the GDB manual and other documentation resources online at:
>> .
>> For help, type "help".
>> Type "apropos word" to search for commands related to "word"...
>> Reading symbols from ./kicad...(no debugging symbols found)...done.
>> (gdb) run
>> Starting program: /home/admin/SW/bin/kicad
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/usr/lib/libthread_db.so.1".
>> [New Thread 0x7fffe7583700 (LWP 21633)]
>> [New Thread 0x7fffe6d82700 (LWP 21634)]
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x731488c0 in ?? () from /usr/lib/libgobject-2.0.so.0
>> (gdb) bt
>> #0  0x731488c0 in ?? () from /usr/lib/libgobject-2.0.so.0
>> #1  0x73151dfc in g_signal_emit_valist () from
>> /usr/lib/libgobject-2.0.so.0
>> #2  0x7315212f in g_signal_emit () from
>> /usr/lib/libgobject-2.0.so.0
>> #3  0x73785e00 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
>> #4  0x7313d7b8 in g_object_run_dispose () from
>> /usr/lib/libgobject-2.0.so.0
>> #5  0x76cbc840 in wxButtonBase::GetDefaultSize() () from
>> /usr/lib/libwx_gtk2u_core-3.0.so.0
>> #6  0x76cbc89a in wxButton::DoGetBestSize() const () from
>> /usr/lib/libwx_gtk2u_core-3.0.so.0
>> #7  0x76e5c219 in wxWindowBase::GetBestSize() const () from
>> /usr/lib/libwx_gtk2u_core-3.0.so.0
>> #8  0x76e5c348 in wxWindowBase::GetEffectiveMinSize() const ()
>> from /usr/lib/libwx_gtk2u_core-3.0.so.0
>> #9  0x76e5c440 in wxWindowBase::SetInitialSize(wxSize const&) ()
>> from /usr/lib/libwx_gtk2u_core-3.0.so.0
>> 

Re: [Kicad-developers] 3D refactor update

[Cirilo Bernardo]

On Tue, Jan 19, 2016 at 5:14 AM, Bernhard Stegmaier <stegma...@sw-systems.de
> wrote:

> Hi,
>
> I didn’t try(check it, so maybe just dumb questions:
> What is the difference between the cached and original files?
> I guess most of the time the config folder will be on the same storage as
> the original files (== home folder), so what’s the point of copying them to
> a cache folder?
> It would probably make sense to be able to configure the cache folder (or
> use sth like $XDG_CACHE_HOME), so it could be directed to e.g. a tmpfs in
> RAM.
>
>
The cache files are a binary format and are an intermediate data
representation.
The existing scheme for 3D models is to parse them and put data into an
S3D_MASTER object. The translated data is not suitable for caching and
each instance of the same model file takes up more and more memory.
With the intermediate format each model is loaded only once so less memory
is used. In foreseeable future cases the intermediate format will also make
the subsequent model load times much faster in cases where creating the
display data is a compute-intensive operation, for example with rendering
MCAD data. The intermediate representation also means that each 3D
model plugin must translate to this one common data format which is
understood by the cache system; this also makes it possible to implement
a VRML output without much additional code since there is now a single
point of translation from intermediate format to VRML. In the legacy scheme
this would have been very messy to implement with each parser
implementing its own translator and VRML export routines - the parsers would
essentially be translating the model twice (once to S3D_MASTER then again
to VRML).

The cache file also speeds up model loading because it stores its own
computed normals. In our collection of VRML models I have noticed that
in the majority of cases there is either no normals data or the normals
data is bad. In the 3D plugin implementation all normals are calculated;
at this point I can't think of a scheme to select between calculated and
in-model normals on a per-model basis. Perhaps we can make such a
refinement in the future.

You can always link your cache directory to a RAMFS if you wish.

- Cirilo


>
> Regards,
> Bernhard
>
> > On 18 Jan 2016, at 19:02, Mário Luzeiro <mrluze...@ua.pt> wrote:
> >
> > Hi,
> >
> > For a) I think for this cache mechanisms there should be some way to
> versioning the files or folders or what.. so it will be automatically
> possible to the application to delete that files.
> > A possibility would be to hash the file with his own version, so a
> future version will create a different hash.. and maybe there is need for a
> size limit of the folder..
> >
> > Just some ideas..
> >
> > Mario
> >
> > 
> > From: Kicad-developers [kicad-developers-bounces+mrluzeiro=
> ua...@lists.launchpad.net] on behalf of Clemens Koller [c...@embeon.de]
> > Sent: 18 January 2016 11:06
> > To: kicad-developers@lists.launchpad.net
> > Subject: Re: [Kicad-developers] 3D refactor update
> >
> > Hello, Cirilo!
> >
> > On 2016-01-18 09:59, Cirilo Bernardo wrote:
> >> I have reworked the new 3D code and would appreciate some
> testing/feedback
> >> Those who have tried previous versions will need to:
> >> a. delete all cache files (in the kicad config. directory under
> 3d/cache) and
> >> b. delete the older 3D search path list (in the kicad config. dir
> 3d/3Dresolver.cfg)
> >
> > What happens if somebody forgets to delete these files upfront?
> > Are these two steps also necessary in the production version later on?
> >
> > Regards,
> >
> > Clemens
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor update (segfaults here)

[Cirilo Bernardo]

Hi Clemens,

 Perhaps a debug build would help.  From the backtrace it's not obvious to
me
where the problem might be; it seems to be unrelated to the code changes
which I made.

 If there's a possibility that the code is being linked to other existing
libraries, try running 'ldd' on kicad/pcbnew and checking that the linker
is pointing to the expected instance of the library.

 Thanks for trying the code; reports like these are always helpful.

- Cirilo


On Tue, Jan 19, 2016 at 8:17 AM, Clemens Koller  wrote:

> Hi, Cirilo
>
> On 2016-01-18 09:59, Cirilo Bernardo wrote:
> >  I have reworked the new 3D code and would appreciate some
> testing/feedback
> > on the 3D path configuration and name resolution. This is (hopefully)
> the last
> > hurdle before merging the code with the main branch, which in turn will
> be the
> > first step towards implementing the new 3D Viewer.
> >
> >  Those who have tried previous versions will need to:
> > a. delete all cache files (in the kicad config. directory under
> 3d/cache) and
> > b. delete the older 3D search path list (in the kicad config. dir
> 3d/3Dresolver.cfg)
> >
> >  All existing projects should be able to locate and render their VRML
> models;
> > X3D models are not yet supported (the code hasn't been converted to a
> plugin
> > module yet) but from feedback I have received, X3D models are not
> commonly
> > used.
> >
> > bazaar.launchpad.net/~cirilo-bernardo/kicad/3d_initial_merge <
> http://bazaar.launchpad.net/~cirilo-bernardo/kicad/3d_initial_merge>
>
>
> As you know, I am usually on the git side, but since you asked
> politely, I branched your 3d_initial_merge to give it a try... ;-)
>
> So I do my usual:
> $ bzr clone
> http://bazaar.launchpad.net/~cirilo-bernardo/kicad/3d_initial_merge
> $ cd 3d_initial_merge
> $ rm -r build
> $ mkdir -p build/release
> $ cd build/release
> $ cmake -DCMAKE_INSTALL_PREFIX=~/SW \
> -DDEFAULT_INSTALL_PATH=~/SW \
> -DKICAD_SKIP_BOOST=ON \
> -DKICAD_SCRIPTING=ON \
> -DKICAD_SCRIPTING_MODULES=ON \
> -DKICAD_SCRIPTING_WXPYTHON=ON \
> ../../
> $ make -j8
> $ make install
>
> ... seems to compile fine and gets installed as usual.
>
> An optional:
> $ rm -r ~/.config/kicad
> made sure, we start from scratch, but without any effect.
>
> $ cd ~/SW/bin
> $ PYTHONPATH=~/SW/lib/python2.7/site-packages/ ./kicad
>
> runs kicad, but I get a segfault when I open pcbnew or
> the footprint editor by clicking on the buttons.
>
> Details:
> $ gdb ./kicad
> GNU gdb (GDB) 7.10.1
> Copyright (C) 2015 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-unknown-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from ./kicad...(no debugging symbols found)...done.
> (gdb) run
> Starting program: /home/admin/SW/bin/kicad
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/usr/lib/libthread_db.so.1".
> [New Thread 0x7fffe7583700 (LWP 21633)]
> [New Thread 0x7fffe6d82700 (LWP 21634)]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x731488c0 in ?? () from /usr/lib/libgobject-2.0.so.0
> (gdb) bt
> #0  0x731488c0 in ?? () from /usr/lib/libgobject-2.0.so.0
> #1  0x73151dfc in g_signal_emit_valist () from
> /usr/lib/libgobject-2.0.so.0
> #2  0x7315212f in g_signal_emit () from
> /usr/lib/libgobject-2.0.so.0
> #3  0x73785e00 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
> #4  0x7313d7b8 in g_object_run_dispose () from
> /usr/lib/libgobject-2.0.so.0
> #5  0x76cbc840 in wxButtonBase::GetDefaultSize() () from
> /usr/lib/libwx_gtk2u_core-3.0.so.0
> #6  0x76cbc89a in wxButton::DoGetBestSize() const () from
> /usr/lib/libwx_gtk2u_core-3.0.so.0
> #7  0x76e5c219 in wxWindowBase::GetBestSize() const () from
> /usr/lib/libwx_gtk2u_core-3.0.so.0
> #8  0x76e5c348 in wxWindowBase::GetEffectiveMinSize() const ()
> from /usr/lib/libwx_gtk2u_core-3.0.so.0
> #9  0x76e5c440 in wxWindowBase::SetInitialSize(wxSize const&) ()
> from /usr/lib/libwx_gtk2u_core-3.0.so.0
> #10 0x76cbc60e in wxButton::Create(wxWindow*, int, wxString
> const&, wxPoint const&, wxSize const&, long, wxValidator const&, wxString
> const&) () from /usr/lib/libwx_gtk2u_core-3.0.so.0
> #11 0x76ea6d3d in ?? () from /usr/lib/libwx_gtk2u_core-3.0.so.0
> #12 0x76ea7d41 in
> 

Re: [Kicad-developers] 3D refactor update

[Cirilo Bernardo]

On Mon, Jan 18, 2016 at 10:06 PM, Clemens Koller  wrote:

> Hello, Cirilo!
>
> On 2016-01-18 09:59, Cirilo Bernardo wrote:
> >  I have reworked the new 3D code and would appreciate some
> testing/feedback
> >  Those who have tried previous versions will need to:
> > a. delete all cache files (in the kicad config. directory under
> 3d/cache) and
> > b. delete the older 3D search path list (in the kicad config. dir
> 3d/3Dresolver.cfg)
>
> What happens if somebody forgets to delete these files upfront?
> Are these two steps also necessary in the production version later on?
>
>
Deleting the search path file was necessary because of a change in format;
it
doesn't matter if it's not deleted since the configuration  tool can write
over it.
Deleting the cache data was only necessary because some bugs were fixed
which affect the cache data. For production it is extremely unlikely that
deleting this data will be necessary unless there are changes to the format
of the files. If it's necessary some version information can always be
written.

- Cirilo

  Regards,

Clemens

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor update (segfaults here)

[Clemens Koller]

Hi, Cirilo

On 2016-01-18 09:59, Cirilo Bernardo wrote:
>  I have reworked the new 3D code and would appreciate some testing/feedback
> on the 3D path configuration and name resolution. This is (hopefully) the last
> hurdle before merging the code with the main branch, which in turn will be the
> first step towards implementing the new 3D Viewer.
> 
>  Those who have tried previous versions will need to:
> a. delete all cache files (in the kicad config. directory under 3d/cache) and
> b. delete the older 3D search path list (in the kicad config. dir 
> 3d/3Dresolver.cfg)
> 
>  All existing projects should be able to locate and render their VRML models;
> X3D models are not yet supported (the code hasn't been converted to a plugin
> module yet) but from feedback I have received, X3D models are not commonly
> used.
> 
> bazaar.launchpad.net/~cirilo-bernardo/kicad/3d_initial_merge 
> 


As you know, I am usually on the git side, but since you asked
politely, I branched your 3d_initial_merge to give it a try... ;-)

So I do my usual:
$ bzr clone http://bazaar.launchpad.net/~cirilo-bernardo/kicad/3d_initial_merge
$ cd 3d_initial_merge
$ rm -r build
$ mkdir -p build/release
$ cd build/release
$ cmake -DCMAKE_INSTALL_PREFIX=~/SW \
-DDEFAULT_INSTALL_PATH=~/SW \
-DKICAD_SKIP_BOOST=ON \
-DKICAD_SCRIPTING=ON \
-DKICAD_SCRIPTING_MODULES=ON \
-DKICAD_SCRIPTING_WXPYTHON=ON \
../../
$ make -j8
$ make install

... seems to compile fine and gets installed as usual.

An optional:
$ rm -r ~/.config/kicad
made sure, we start from scratch, but without any effect.

$ cd ~/SW/bin
$ PYTHONPATH=~/SW/lib/python2.7/site-packages/ ./kicad

runs kicad, but I get a segfault when I open pcbnew or
the footprint editor by clicking on the buttons.

Details:
$ gdb ./kicad
GNU gdb (GDB) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./kicad...(no debugging symbols found)...done.
(gdb) run
Starting program: /home/admin/SW/bin/kicad 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe7583700 (LWP 21633)]
[New Thread 0x7fffe6d82700 (LWP 21634)]

Program received signal SIGSEGV, Segmentation fault.
0x731488c0 in ?? () from /usr/lib/libgobject-2.0.so.0
(gdb) bt
#0  0x731488c0 in ?? () from /usr/lib/libgobject-2.0.so.0
#1  0x73151dfc in g_signal_emit_valist () from 
/usr/lib/libgobject-2.0.so.0
#2  0x7315212f in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#3  0x73785e00 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#4  0x7313d7b8 in g_object_run_dispose () from 
/usr/lib/libgobject-2.0.so.0
#5  0x76cbc840 in wxButtonBase::GetDefaultSize() () from 
/usr/lib/libwx_gtk2u_core-3.0.so.0
#6  0x76cbc89a in wxButton::DoGetBestSize() const () from 
/usr/lib/libwx_gtk2u_core-3.0.so.0
#7  0x76e5c219 in wxWindowBase::GetBestSize() const () from 
/usr/lib/libwx_gtk2u_core-3.0.so.0
#8  0x76e5c348 in wxWindowBase::GetEffectiveMinSize() const () from 
/usr/lib/libwx_gtk2u_core-3.0.so.0
#9  0x76e5c440 in wxWindowBase::SetInitialSize(wxSize const&) () from 
/usr/lib/libwx_gtk2u_core-3.0.so.0
#10 0x76cbc60e in wxButton::Create(wxWindow*, int, wxString const&, 
wxPoint const&, wxSize const&, long, wxValidator const&, wxString const&) () 
from /usr/lib/libwx_gtk2u_core-3.0.so.0
#11 0x76ea6d3d in ?? () from /usr/lib/libwx_gtk2u_core-3.0.so.0
#12 0x76ea7d41 in wxLogGui::DoShowMultipleLogMessages(wxArrayString 
const&, wxArrayInt const&, wxArrayLong const&, wxString const&, int) () from 
/usr/lib/libwx_gtk2u_core-3.0.so.0
#13 0x76ea26d2 in wxLogGui::Flush() () from 
/usr/lib/libwx_gtk2u_core-3.0.so.0
#14 0x763ee9c1 in wxLog::SetActiveTarget(wxLog*) () from 
/usr/lib/libwx_baseu-3.0.so.0
#15 0x763deaf8 in wxEntryCleanup() () from /usr/lib/libwx_baseu-3.0.so.0
#16 0x763debac in wxUninitialize() () from /usr/lib/libwx_baseu-3.0.so.0
#17 0x763e01f4 in wxEntry(int&, wchar_t**) () from 
/usr/lib/libwx_baseu-3.0.so.0
#18 0x0041fd08 in ?? ()
#19 0x73c91610 in __libc_start_main () from /usr/lib/libc.so.6
#20 0x00424e79 in _start ()


Let 

Re: [Kicad-developers] 3D refactor

[Cirilo Bernardo]

No problem, I'm looking forward to some comments on the code.

- Cirilo

On Sat, Jan 9, 2016 at 7:27 AM, Wayne Stambaugh 
wrote:

> Cirilo,
>
> Please hold off on putting any more effort into this until I can comment
> on it.  I've look over the merge request and saw a bunch of things that
> will need to be changed before I am willing accept it.  I will try to
> build and test your merge request and get back to you by the end of the
> weekend.
>
> Cheers,
>
> Wayne
>
> On 1/8/2016 3:03 AM, Cirilo Bernardo wrote:
> > For those interested in the ongoing 3D work, the VRML parsers have been
> > greatly improved in the last few days so you can expect to view all your
> > VRML models in the preview panel of the Footprint Properties editors.
> >
> > There's still a way to go to replace 3DViewer but the code as it is
> provides
> > a tool (preview) which people may find useful and of course the new
> > 3D model file path resolver and a much improved selection dialog.
> >
> > I used the new interface to help select my models for the pic_programmer
> > demo:
> >
> >
> https://drive.google.com/file/d/0By_XTJN-s8aXSDU2VXVQNUJoM1k/view?usp=sharing
> >
> > That's a rendering of course from the current 3DViewer, but I can assure
> > you all
> > that selecting the models was much easier with this new interface.
> >
> > One down side of the new 3D plugins: since the 3DViewer has not yet been
> > replaced, 3DViewer still uses the legacy parsers and I've found that they
> > segfault on quite a number of test files which the plugins + preview
> display
> > without problems. So the good (and bad) news is that I know there are
> > problems in the current parsers. The other bad news of course is that
> > there's
> > no point in spending time fixing those parsers. Of course more testing
> and
> > comments would be appreciated.  I'm nagging a handful of people to test
> on
> > MSWin, Linux, and OSX but I know they're all very busy with other things
> and
> > I get tired of nagging.
> >
> > - Cirilo
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[easyw]

Hi Cirilo, 
is there a way to build it as a standalone 3D viewer?
I could do some test on win and osx

Maurice

On 8 January 2016 09:03:47 CET, Cirilo Bernardo  
wrote:
>For those interested in the ongoing 3D work, the VRML parsers have been
>greatly improved in the last few days so you can expect to view all
>your
>VRML models in the preview panel of the Footprint Properties editors.
>
>There's still a way to go to replace 3DViewer but the code as it is
>provides
>a tool (preview) which people may find useful and of course the new
>3D model file path resolver and a much improved selection dialog.
>
>I used the new interface to help select my models for the
>pic_programmer
>demo:
>
>https://drive.google.com/file/d/0By_XTJN-s8aXSDU2VXVQNUJoM1k/view?usp=sharing
>
>That's a rendering of course from the current 3DViewer, but I can
>assure
>you all
>that selecting the models was much easier with this new interface.
>
>One down side of the new 3D plugins: since the 3DViewer has not yet
>been
>replaced, 3DViewer still uses the legacy parsers and I've found that
>they
>segfault on quite a number of test files which the plugins + preview
>display
>without problems. So the good (and bad) news is that I know there are
>problems in the current parsers. The other bad news of course is that
>there's
>no point in spending time fixing those parsers. Of course more testing
>and
>comments would be appreciated.  I'm nagging a handful of people to test
>on
>MSWin, Linux, and OSX but I know they're all very busy with other
>things and
>I get tired of nagging.
>
>- Cirilo
>
>
>
>
>___
>Mailing list: https://launchpad.net/~kicad-developers
>Post to : kicad-developers@lists.launchpad.net
>Unsubscribe : https://launchpad.net/~kicad-developers
>More help   : https://help.launchpad.net/ListHelp

-- 
Sent from Mobile___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor

[Henner Zeller]

On 18 December 2015 at 23:07, Cirilo Bernardo  wrote:
> Hi folks,
>
>  I've gone over the changes in the 3d_initial_merge branch and it looks like
> it's ready for people to inspect the code and merge with the main branch.
>
>  At the moment the legacy 3DViewer is left intact but the Footprint
> Properties dialogs in pcbnew and the Footprint Editor have an improved
> GUI which includes a special widget on the 3D File Browser to configure
> the 3D search paths and of course the model preview in the Footprint
> Properties dialog.
>
> So far only an IDF Component Outline plugin has been implemented
> (I'm not counting the plugins developed for demo/tutorials) but I'd like
> the code to get into the main branch as soon as practical so people
> can test it more and help find any remaining bugs. A merge would
> also give the 2x 3D branches (Mario's and mine) a more solid foundation
> in the main branch and help prevent a fork-like situation where it
> becomes very difficult to stage a merge.  Even this relatively small
> initial merge has taken a few weeks of my spare time to prepare and
> I've already encountered some instances of code divergence which
> have broken the build.
>
> https://code.launchpad.net/~cirilo-bernardo/kicad/3d_initial_merge

For testing: Is there a simple way to extract a patch from launchpad ?
(I am using git, so I need to get the patch out of bzr first...)

>
> Added approx. 17k sloc
>
> - Cirilo
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D Refactor: screenshots

[Wayne Stambaugh]

What are the eight buttons buttons below the 3D veiw panel?  I hope you
do not intend to use I, T, L, R, etc. as button text.  Abbreviations are
frowned upon unless they are well know like PCB.  Also, the alignment of
the orientation coordinate controls needs fixed.  I do like the idea of
the view panel.

On 10/24/2015 12:38 AM, Cirilo Bernardo wrote:
> I have a few screenshots showing the 3D model selector and editors in the
> existing code and the 3D refactor branch:
> 
> https://drive.google.com/folderview?id=0By_XTJN-s8aXQ2RMOTZrWGtCSTQ=drive_web
> 
> Any comments on the layout etc would be welcome. If anyone wants to play
> with
> this new selection tool they can check out my 3D refactor branch. Just a
> few notes:
> (1) integration is not yet completed so the 3D viewer can't actually
> find the model files,
> but I hope to get that part done soon. (2) The large blank space shows
> where the 3D
> preview will eventually go, but there's a long way to go yet before that
> part is implemented.
> (3) the various buttons under the blank part are intended to have icons
> in the future; these
> buttons implement isometric view, front/back, left/right, top/bottom,
> and update - ideally
> the buttons will be icons in the future, but naturally these buttons
> will do nothing until
> the new renderer is ready to show previews.
> 
> - Cirilo
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D Refactor: screenshots

[Cirilo Bernardo]

On Tue, Nov 3, 2015 at 4:03 AM, Wayne Stambaugh 
wrote:

> What are the eight buttons buttons below the 3D veiw panel?  I hope you
> do not intend to use I, T, L, R, etc. as button text.  Abbreviations are
> frowned upon unless they are well know like PCB.  Also, the alignment of
> the orientation coordinate controls needs fixed.  I do like the idea of
> the view panel.
>
>
The text are only place holders; the buttons are intended to be icons for
Top, Bottom, Left, Right, Front, Back, Isometric view, and Update.  The
Update
button was intended to recalculate the view given the Offset/Rotation/Scale
parameters but I'm still thinking about what to present in that particular
GUI;
a few people have reported that my file selector is inconvenient on their
computer
because it takes up a large part of the screen, so I'm thinking of ways to
trim
things without sacrificing the preview.

- Cirilo


> On 10/24/2015 12:38 AM, Cirilo Bernardo wrote:
> > I have a few screenshots showing the 3D model selector and editors in the
> > existing code and the 3D refactor branch:
> >
> >
> https://drive.google.com/folderview?id=0By_XTJN-s8aXQ2RMOTZrWGtCSTQ=drive_web
> >
> > Any comments on the layout etc would be welcome. If anyone wants to play
> > with
> > this new selection tool they can check out my 3D refactor branch. Just a
> > few notes:
> > (1) integration is not yet completed so the 3D viewer can't actually
> > find the model files,
> > but I hope to get that part done soon. (2) The large blank space shows
> > where the 3D
> > preview will eventually go, but there's a long way to go yet before that
> > part is implemented.
> > (3) the various buttons under the blank part are intended to have icons
> > in the future; these
> > buttons implement isometric view, front/back, left/right, top/bottom,
> > and update - ideally
> > the buttons will be icons in the future, but naturally these buttons
> > will do nothing until
> > the new renderer is ready to show previews.
> >
> > - Cirilo
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor update

[easyw]

Hi Cirilo,
here some feedback in mswin:

first I had an error on building with dlfcn.h
then I solved adding dlfcn.c and dlfcn.h from
https://github.com/dlfcn-win32/dlfcn-win32
and changing
#include 
to
#include "dlfcn.h"

but then I have this file missing:
#include 

and I cannot find a correspondent in mswin...
may be someone of the dev could help?

thank you
Maurice

On 08/10/2015 12.31, easyw wrote:

Hi Cirilo,

thanks for the info
... I will try to build test3dmm only program...

If I can get it in linux, then I will try to build it also in win, and
if I succeed I will give you some feedback and tips for mswin :)

Maurice


On 08/10/2015 12.18, Cirilo Bernardo wrote:

Hi Maurice,

  The instructions are in the README file in the 3dv directory. You will
need a build environment which can build KiCad though and I know nothing
about how to set that up on MSWin, which is why I ask if there are any
devs who can help on OSX and MSWin. :)  I'm only working on a refactor
to allow better management of the models and also to make it easier to
add exporters and plugins to support more model formats. Mario Luzeiro
is working more on 3DViewer and the renderer.

- Cirilo



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor update

[easyw]

Hi Cirilo,

thanks for the info
... I will try to build test3dmm only program...

If I can get it in linux, then I will try to build it also in win, and 
if I succeed I will give you some feedback and tips for mswin :)


Maurice


On 08/10/2015 12.18, Cirilo Bernardo wrote:

Hi Maurice,

  The instructions are in the README file in the 3dv directory. You will
need a build environment which can build KiCad though and I know nothing
about how to set that up on MSWin, which is why I ask if there are any
devs who can help on OSX and MSWin. :)  I'm only working on a refactor
to allow better management of the models and also to make it easier to
add exporters and plugins to support more model formats. Mario Luzeiro
is working more on 3DViewer and the renderer.

- Cirilo



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 3D refactor branch

[Mário Luzeiro]

Hi Cirilo,

I agree in generally with the necessities you pointed. Except the ones I will 
comment below :)

Still don't agree with the necessity of tracking a pointer to display data in 
S3D_ENTRY, special if you also agree that we need decoupling.

Your S3D_ENTRY, the (current/old) S3D_MASTER was used by 3d-viewer, the 3d file 
parsers, the pcbnew dialogs, 3d exporters, etc
https://github.com/KiCad/kicad-source-mirror/search?p=1=S3D_MASTER=%E2%9C%93

The S3D_ENTRY content have data in relation of the description and parameter 
definition.
Removing all that "3d model data related" from the S3D_MASTER we get the 
S3D_ENTRY.
And I believe the propose was to decouple any relation between that description 
with any 3d-viewer data.
If you search in that link for the use of S3D_MASTER you will see that pcbnew 
is using it for other internal proposes that will not be related with handling 
any 3d-model data. (ex: the pcbnew dialogs just use it to store the 
transformation information and filename..etc.)

So keeping that pointer to 3d-data in S3D_ENTRY is forcing an relation with the 
use of that data.
It will force a relation with 3d-viewer(that will display that data), a 
relation with module manager and parses, etc and there is no need for that 
relation because it is not the main propose of the use of the S3D_ENTRY.

I will add some more of my points below.



> otherwise we would waste a ridiculous amount of time searching for
> the related data in other places. In this design if display data is needed 
> and none is
> available yet then it is requested from the model manager, and if the data 
> already
> exists then it is used.

I don't see why "ridiculous amount of time searching for the related data in 
other places", you said yourself later:
"it can request such data from the model manager. Since we do not access such 
data frequently, the O( sqrt(N) ) search operation should not be a problem;"

I believe a normal use of kicad, you will never have more than 100, 1K, (10K..) 
modules to search. So should be in any case any problems search for any 
relation.


> For convenience pcbnew will have an instance of the model manager, probably 
> inside BOARD initially,
> but personally I think we will need to think of a way to move it somewhere 
> else -
> but that's a job for the future.

My previous suggestion was to implement it as a "singleton pattern" and put it 
in a global space.
In that case it will be instantiated only the first time someone use it and it 
there will only be one instance of that module "model manager". (So it will be 
available for other boards..etc)
I think that is a design decision that can be made at this point.




> The model manager will need some cues to help manage information since, for 
> example, browsing for a model to use will
> cause the manager to call the parser and create display data for each model 
> you preview in the file browser.

IMO the only cue the model manager need is the fullPathFilename/URL to pass it 
to the parser and store the "whatever structure, original scale, model data".
I will explain again below.




> The relationships will be more
> complex since there is the reference instance (DISPLAY_DATA_3D - maybe I
> will change the name later) and each model actually displayed needs a
> specific instantiation which is derived from the reference. Only the 
> reference is
> cached; specific instances are created/destroyed as required.

IMO only the original reference data need to be created and cache managed, the 
specific necessities in relation with how to display in relation of the 
parameters in a S3D_ENTRY are for the responsibility of who will use that 
data/information (ex some 3d-viewer implementation, or a 3d-exporter).

I don't see any complex relation, I see no relation at all.

If I understand it, if you mean that
store a "needs a specific instantiation" = ApplyTransformation( S3D_ENTRY, 
"original reference" )

That will not be needed and should be avoided. That will be assume a lot about 
the use of that 3D Data and we should let it to the implementation (of a 
3d-viewer, or a exporter, etc) that will use the original data to decide what 
is the best way of handle it. Also, there is no noticeable penalty to apply the 
transformations "on the fly" because:
- You will only apply the transformation when you will really use it (ex: the 
3D display convert the model data to be transformed to display at pre-load 
before start the rendering)
- Apply transformations with CPU is fast and the models are not huge complex, 
(and you do it only once when load the model to GPU in case of 3dviewer)
- If you consider use GPU shaders, that transformation can be performed by the 
shader on the fly, so no CPU is used at all (this is specific to an 
implementation)
- If you consider using GPU memory, a 3d-viewer implementation can implement 
its own cache manager, so while you have your (ex: opengl) context you can 
cache the it GPU to be reused latter. (this is