Re: [Kicad-developers] 3D modules path strange behaviour
Le 03/08/2014 12:59, Mário Luzeiro a écrit : Hi yann, I've reported that issue some time ago: https://bugs.launchpad.net/kicad/+bug/1343904 Hi I don't think it is the exact same problem. In my case, the path to the system installed 3D models is ok, but it that folder the path point to, there are some folders with models inside, and it's only those subfolders that are case-sensitive. Well case-sensitive is not the right term, because even if the path defined in the module properties is ok, it won't show up if there is one uppercase letter at the beginning of the folder name. And also what about the path to the 3D models directory that cannot be edited ? Is there a place where we can edit it ? The version I use now is : Version: (2014-07-30 BZR 5036)-product Release build wxWidgets: Version 2.8.12 (release,Unicode,compiler with C++ ABI 1002,GCC 4.8.1,wx containers,compatible with 2.6) Platform: Linux 3.11.0-22-generic i686, 32 bit, Little endian, wxGTK Boost version: 1.54.0 USE_WX_GRAPHICS_CONTEXT=OFF USE_WX_OVERLAY=OFF KICAD_SCRIPTING=OFF KICAD_SCRIPTING_MODULES=OFF KICAD_SCRIPTING_WXPYTHON=OFF USE_FP_LIB_TABLE=HARD_CODED_ON BUILD_GITHUB_PLUGIN=ON but I got the problem with all the previous versions I tested. Well, it's 4 days old now, but was the latest when I started writing the first mail :) I'm upgrading now. regards, yann it says that a fix was commited. I didnt try it yet, but since you say you tested the latest one.. so probably is not full fixed yet. Mario From: Kicad-developers [kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of yann jautard [brico...@free.fr] Sent: 03 August 2014 11:52 To: kicad-developers@lists.launchpad.net Subject: [Kicad-developers] 3D modules path strange behaviour Hi I just installed the latest bzr with the install script on my ubuntu system. I see that some new 3D modules comes along with the fresh install. Great. But lots of them are not displayed in the 3D view. I tried with an older version, to see if it was due to the recent changes in 3D view, but no luck. I checked the wrml files with view3dscene, they opens ok. investigating a little more, it turns out that the exact same file, e.g. /usr/local/share/kicad/modules/packages3d/conn_DBxx/db9_female.wrl displays ok, but when selecting the same file, but in that directory : /usr/local/share/kicad/modules/packages3d/Conn_DBxx/db9_female.wrl It does not show up anymore. So the problem seems to be only with directories beginning with an uppercase letter. Uppercase letters in filenames don't seems to cause problems. I copied the files I need to a new directory in my project folder. And now, they works ok only if I select them using full path. When I answer OK to the dialog box that asks Use relative path ? they do not show up anymore. I thought I need to change default path $KSYS3DMOD in the selection dialog to point to my new directory, but that line is not editable. One interesting thing is the local directory can be uppercase, this time it is not a problem. regards, yann ___ 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 modules path strange behaviour
2014-08-04 10:00 GMT+02:00 yann jautard brico...@free.fr: And also what about the path to the 3D models directory that cannot be edited ? Is there a place where we can edit it ? That is a bug I believe, it is supposed to be set with an environment variable, but I guess it is just not catched anywhere. ___ 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
[Kicad-developers] Build failed in Jenkins: kicad-qa #262
See http://ci.kicad-pcb.org/job/kicad-qa/262/changes Changes: [jean-pierre charras] 3D viewer: move helper functions from 3d_draw.cpp to 3d_draw_helper_functions.cpp. Add comments in .h sources. Better management of background color. coding style fixes. -- Started by an SCM change Building in workspace http://ci.kicad-pcb.org/job/kicad-qa/ws/ $ bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ info result: bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ returned 0. Command output: 5048 maciej.sumin...@cern.ch-20140804084326-w1wmryf2u4v0t0ww stderr: [kicad-qa] $ bzr pull --overwrite lp:kicad You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See bzr help launchpad-login. http://bazaar.launchpad.net/~kicad-product-committers/kicad/product is permanently redirected to http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/changes You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See bzr help launchpad-login. +N 3d-viewer/3d_draw_helper_functions.cpp M 3d-viewer/3d_canvas.cpp M 3d-viewer/3d_canvas.h M 3d-viewer/3d_draw.cpp M 3d-viewer/3d_frame.cpp M 3d-viewer/CMakeLists.txt M demos/kit-dev-coldfire-xilinx_5213/kit-dev-coldfire-xilinx_5213.kicad_pcb All changes applied successfully. Now on revision 5049. [kicad-qa] $ bzr revert $ bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ info result: bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ returned 0. Command output: 5049 jp.char...@wanadoo.fr-20140804112829-ylw5edep5gg58x5m stderr: [kicad-qa] $ bzr log -v -r revid:maciej.sumin...@cern.ch-20140804084326-w1wmryf2u4v0t0ww..revid:jp.char...@wanadoo.fr-20140804112829-ylw5edep5gg58x5m --long --show-ids Getting local revision... $ bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ info result: bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ returned 0. Command output: 5049 jp.char...@wanadoo.fr-20140804112829-ylw5edep5gg58x5m stderr: RevisionState revno:5049 revid:jp.char...@wanadoo.fr-20140804112829-ylw5edep5gg58x5m [kicad-qa] $ /bin/sh -xe /tmp/hudson5730237897856735368.sh + OPTS=' -DCMAKE_BUILD_TYPE=Debug -DBUILD_GITHUB_PLUGIN=ON -DKICAD_SCRIPTING=ON -DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXPYTHON=ON' + '[' -d build ']' + cd build + /usr/bin/cmake .. -DCMAKE_BUILD_TYPE=Debug -DBUILD_GITHUB_PLUGIN=ON -DKICAD_SCRIPTING=ON -DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXPYTHON=ON -- Check for installed OpenGL -- found -- Found Glew: /usr/lib64/libGLEW.so -- Check for installed GLEW -- found -- Check for installed Cairo -- found -- Check for installed wxWidgets -- found -- Check for installed Python Interpreter -- found -- Python module install path: /usr/lib/python2.6/site-packages -- Bazaar version control system version found. -- Kicad Bazaar build version: (2014-08-04 BZR 5049) -- Configuring done -- Generating done -- Build files have been written to: http://ci.kicad-pcb.org/job/kicad-qa/ws/build + rm -f pcbnew/scripting/pcbnewPYTHON_wrap.cxx.o + rm -f pcbnew/scripting/pcbnewPYTHON_wrap.cxx + make -j4 _pcbnew [ 1%] [ 1%] Built target boost [ 1%] Built target idf3 Built target lib-dependencies [ 3%] Built target lib_dxf [ 3%] Built target avhttp [ 3%] Generating headers containing GLSL source code Headers are up-to-date [ 3%] Built target shader_headers [ 50%] Built target bitmaps [ 52%] Built target pcad2kicadpcb [ 52%] Built target polygon [ 52%] Built target github_plugin Scanning dependencies of target 3d-viewer [ 53%] Built target gal [ 53%] [ 53%] Building CXX object 3d-viewer/CMakeFiles/3d-viewer.dir/3d_aux.cpp.o Building CXX object 3d-viewer/CMakeFiles/3d-viewer.dir/3d_canvas.cpp.o [ 60%] Built target pcbcommon Scanning dependencies of target common [ 63%] Built target pnsrouter [ 63%] Building CXX object 3d-viewer/CMakeFiles/3d-viewer.dir/3d_draw.cpp.o [ 63%] Building CXX object common/CMakeFiles/common.dir/build_version.cpp.o Linking CXX static library libcommon.a [ 63%] Building CXX object 3d-viewer/CMakeFiles/3d-viewer.dir/3d_draw_helper_functions.cpp.o http://ci.kicad-pcb.org/job/kicad-qa/ws/3d-viewer/3d_draw_helper_functions.cpp:30:22: error: Polyline.h: No such file or directory [ 74%] Built target common [ 74%] Building CXX object 3d-viewer/CMakeFiles/3d-viewer.dir/3d_frame.cpp.o make[3]: *** [3d-viewer/CMakeFiles/3d-viewer.dir/3d_draw_helper_functions.cpp.o] Error 1 make[3]: *** Waiting for unfinished jobs make[2]: *** [3d-viewer/CMakeFiles/3d-viewer.dir/all] Error 2 make[1]: *** [pcbnew/CMakeFiles/_pcbnew.dir/rule] Error 2 make: *** [_pcbnew] Error 2 Build step 'Execute shell' marked build as failure ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :
Re: [Kicad-developers] 3D modules path strange behaviour
Le 04/08/2014 10:57, Nick Østergaard a écrit : 2014-08-04 10:00 GMT+02:00 yann jautard brico...@free.fr: And also what about the path to the 3D models directory that cannot be edited ? Is there a place where we can edit it ? That is a bug I believe, it is supposed to be set with an environment variable, but I guess it is just not catched anywhere. I noticed also we can't edit the KIPRJMOD and KISYSMOD variables related to the library table. I'm not sure that this should me environnement settings. In my opinion they should be project-specific, and stored in the project file. ( Like it was before the fp-lib table, I think. ) Maybe the KISYS3DMOD variable should also be added to the library table window, and can be edited there ? Also I don't feel right about those variables relative to library tables : why only two variables ? I think there should be the same buttons under the variables list than under the libraries list, so we can add other research pathes. Like in eeschema. ___ 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 modules path strange behaviour
As a kicad user I agree, I was missing also the feature to load 3D modules from the current project folder path. It looks it is not possible at moment. Also, I do believe that it is very hard to non expert linux/windows users to set that variables in the environment.. :/ From: Kicad-developers [kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of yann jautard [brico...@free.fr] Sent: 04 August 2014 13:34 To: kicad-developers@lists.launchpad.net Subject: Re: [Kicad-developers] 3D modules path strange behaviour Le 04/08/2014 10:57, Nick Østergaard a écrit : 2014-08-04 10:00 GMT+02:00 yann jautard brico...@free.fr: And also what about the path to the 3D models directory that cannot be edited ? Is there a place where we can edit it ? That is a bug I believe, it is supposed to be set with an environment variable, but I guess it is just not catched anywhere. I noticed also we can't edit the KIPRJMOD and KISYSMOD variables related to the library table. I'm not sure that this should me environnement settings. In my opinion they should be project-specific, and stored in the project file. ( Like it was before the fp-lib table, I think. ) Maybe the KISYS3DMOD variable should also be added to the library table window, and can be edited there ? Also I don't feel right about those variables relative to library tables : why only two variables ? I think there should be the same buttons under the variables list than under the libraries list, so we can add other research pathes. Like in eeschema. ___ 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
[Kicad-developers] Jenkins build is back to normal : kicad-qa #263
See http://ci.kicad-pcb.org/job/kicad-qa/263/changes ___ 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] [PATCH] Anti-aliasing for the 3D-Viewer
Le 03/08/2014 12:00, mj a écrit : On 03.08.2014 10:14, jp charras wrote: Le 03/08/2014 03:24, Martin Janitschke a écrit : Heyho, please feel free to test and apply the attached patch for the 3D viewer. It'll enable anti-aliasing - if the renderer supports it with up to factor 8 (beyond this there was no difference in the subtracted images). The code also deals with the possible changes to the attributes array (avoiding fixed indices). For the results see http://imgur.com/a/TgaXT . Bye, imp Thanks for your patch. However it has a potential bug in loops: for( ii = 0; ii sizeof( attrs ); ii += 2) does not stop the iteration at the end of the table. Ah, good catch, forgot / sizeof( attrs[0] )... and the code expects WX_GL_SAMPLES is the last item in attrs table, which is currently true, but could be modified later (and there is no comment to explain this constraint). No. It _is_ build to avoid depending on special positions / indices in that array - that's why there are 2 for loops searching for those elements. But it's expected to be on an even position in that array, see below. The attrs array is: attribute-id, value for that attribute, another attribute-id, value for another attribute, , 0. (Or at least what I've thought it would be first). That's the reason for the += 2 (skipping the value of the attribute we checked). BUT wxwidgets made some strage exceptions for boolean attributes that don't have a value (likely copying it from opengl 13...). This can lead to an exception of the 2*n + 1 rule. Added a comment for this and put in those attributes in a second time as padding (thus enforcing the tuples / attributes on even positions). Additionally we can change the condition to ii sizeof( attrs ) / sizeof( attrs[0] ) - 1 and save 2x one iteration (avoiding to check the null termination against WX_GL_...). New patch attached. Bye, imp Committed, Thanks. Unfortunately, my graphic card does not support anti aliasing, and I am not able to test this enhancement. -- 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
[Kicad-developers] Build failed in Jenkins: kicad-qa #264
See http://ci.kicad-pcb.org/job/kicad-qa/264/changes Changes: [jean-pierre charras] Anti-aliasing patch for the 3D-Viewer from Martin Janitschke -- Started by an SCM change Building in workspace http://ci.kicad-pcb.org/job/kicad-qa/ws/ $ bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ info result: bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ returned 0. Command output: 5050 jp.char...@wanadoo.fr-20140804121733-wbeubhqm711bqp7x stderr: [kicad-qa] $ bzr pull --overwrite lp:kicad You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See bzr help launchpad-login. http://bazaar.launchpad.net/~kicad-product-committers/kicad/product is permanently redirected to http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/changes You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data. See bzr help launchpad-login. M 3d-viewer/3d_frame.cpp All changes applied successfully. Now on revision 5051. [kicad-qa] $ bzr revert $ bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ info result: bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ returned 0. Command output: 5051 jp.char...@wanadoo.fr-20140804122128-31btxatm0g7tsll4 stderr: [kicad-qa] $ bzr log -v -r revid:jp.char...@wanadoo.fr-20140804121733-wbeubhqm711bqp7x..revid:jp.char...@wanadoo.fr-20140804122128-31btxatm0g7tsll4 --long --show-ids Getting local revision... $ bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ info result: bzr revision-info -d http://ci.kicad-pcb.org/job/kicad-qa/ws/ returned 0. Command output: 5051 jp.char...@wanadoo.fr-20140804122128-31btxatm0g7tsll4 stderr: RevisionState revno:5051 revid:jp.char...@wanadoo.fr-20140804122128-31btxatm0g7tsll4 [kicad-qa] $ /bin/sh -xe /tmp/hudson8811108518454774478.sh + OPTS=' -DCMAKE_BUILD_TYPE=Debug -DBUILD_GITHUB_PLUGIN=ON -DKICAD_SCRIPTING=ON -DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXPYTHON=ON' + '[' -d build ']' + cd build + /usr/bin/cmake .. -DCMAKE_BUILD_TYPE=Debug -DBUILD_GITHUB_PLUGIN=ON -DKICAD_SCRIPTING=ON -DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXPYTHON=ON -- Check for installed OpenGL -- found -- Found Glew: /usr/lib64/libGLEW.so -- Check for installed GLEW -- found -- Check for installed Cairo -- found -- Check for installed wxWidgets -- found -- Check for installed Python Interpreter -- found -- Python module install path: /usr/lib/python2.6/site-packages -- Bazaar version control system version found. -- Kicad Bazaar build version: (2014-08-04 BZR 5051) -- Configuring done -- Generating done -- Build files have been written to: http://ci.kicad-pcb.org/job/kicad-qa/ws/build + rm -f pcbnew/scripting/pcbnewPYTHON_wrap.cxx.o + rm -f pcbnew/scripting/pcbnewPYTHON_wrap.cxx + make -j4 _pcbnew [ 1%] [ 1%] Built target boost [ 1%] Built target idf3 Built target lib-dependencies [ 3%] [ 3%] Built target avhttp Built target lib_dxf [ 3%] Generating headers containing GLSL source code Headers are up-to-date [ 3%] Built target shader_headers [ 50%] Built target bitmaps [ 52%] Built target pcad2kicadpcb [ 52%] Built target polygon [ 52%] Built target github_plugin Scanning dependencies of target 3d-viewer [ 52%] [ 53%] Built target gal Building CXX object 3d-viewer/CMakeFiles/3d-viewer.dir/3d_frame.cpp.o [ 60%] Built target pcbcommon Scanning dependencies of target common [ 63%] Built target pnsrouter [ 63%] Building CXX object common/CMakeFiles/common.dir/build_version.cpp.o http://ci.kicad-pcb.org/job/kicad-qa/ws/3d-viewer/3d_frame.cpp: In constructor ‘EDA_3D_FRAME::EDA_3D_FRAME(KIWAY*, PCB_BASE_FRAME*, const wxString, long int)’: http://ci.kicad-pcb.org/job/kicad-qa/ws/3d-viewer/3d_frame.cpp:125: error: ‘WX_GL_SAMPLE_BUFFERS’ was not declared in this scope http://ci.kicad-pcb.org/job/kicad-qa/ws/3d-viewer/3d_frame.cpp:126: error: ‘WX_GL_SAMPLES’ was not declared in this scope http://ci.kicad-pcb.org/job/kicad-qa/ws/3d-viewer/3d_frame.cpp:132: error: ‘IsDisplaySupported’ is not a member of ‘EDA_3D_CANVAS’ http://ci.kicad-pcb.org/job/kicad-qa/ws/3d-viewer/3d_frame.cpp:149: error: ‘IsDisplaySupported’ is not a member of ‘EDA_3D_CANVAS’ make[3]: *** [3d-viewer/CMakeFiles/3d-viewer.dir/3d_frame.cpp.o] Error 1 make[2]: *** [3d-viewer/CMakeFiles/3d-viewer.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs Linking CXX static library libcommon.a [ 74%] Built target common make[1]: *** [pcbnew/CMakeFiles/_pcbnew.dir/rule] Error 2 make: *** [_pcbnew] Error 2 Build step 'Execute shell' marked build as failure ___ 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] [PATCH] Anti-aliasing for the 3D-Viewer
Committed, Thanks. Unfortunately, my graphic card does not support anti aliasing, and I am not able to test this enhancement. -- Jean-Pierre CHARRAS That will be a good oldschool test platform! ;) Thank you for your fast commits! Mario ___ 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
[Kicad-developers] Jenkins build is back to normal : kicad-qa #265
See http://ci.kicad-pcb.org/job/kicad-qa/265/changes ___ 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] [PATCH] Anti-aliasing for the 3D-Viewer
For the number of elements in an array, you can use: ./include/macros.h:#define DIM( x )unsigned( sizeof(x) / sizeof( (x)[0] ) ) which is more consistent in the KiCad source code. Best Regards, Brian. ___ 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 modules path strange behaviour
On 8/4/2014 7:34 AM, yann jautard wrote: Le 04/08/2014 10:57, Nick Østergaard a écrit : 2014-08-04 10:00 GMT+02:00 yann jautard brico...@free.fr: And also what about the path to the 3D models directory that cannot be edited ? Is there a place where we can edit it ? That is a bug I believe, it is supposed to be set with an environment variable, but I guess it is just not catched anywhere. I noticed also we can't edit the KIPRJMOD and KISYSMOD variables related to the library table. I'm not sure that this should me environnement You can edit KIPRJMOD, KISYSMOD, AND KISYS3DMOD. They are environment variables so you have to edit them either system wide or user specific depending on your needs using your preferred method for editing environment variables on your system. You are not obligated to use any of these variables. You can specify the full path and/or file name (depending on the library type) for each library. settings. In my opinion they should be project-specific, and stored in the project file. ( Like it was before the fp-lib table, I think. ) You can use project specific footprint library tables if you prefer rather than using the global footprint table. This is fairly well documented in both the CvPcb and Pcbnew reference manuals. Maybe the KISYS3DMOD variable should also be added to the library table window, and can be edited there ? KISYS3DMOD does not impact the loading of footprint libraries so has no context in the footprint library table. It is only used for loading 3D models. Putting it in the footprint library table editor would be confusing. Also I don't feel right about those variables relative to library tables : why only two variables ? I think there should be the same buttons under the variables list than under the libraries list, so we can add You are not limited to these 3 variables. You are free to define as many environment variables as you like or until you system runs out of memory. I use KILCLMOD to point to all my custom libraries. other research pathes. Like in eeschema. This will not happen. The path look up method is so broken that it's hard to know where to begin to explain it. There have been at least a dozen bug reports due to wrong footprints and components being loaded due to path search order issues. This has been discussed many times and the issue still exists in Eeschema. You can search the bug and mailing lists and find plenty of discussion about this issue. ___ 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 modules path strange behaviour
Wayne, In our 3/20/2014 project planning conversation I mentioned: newstring = Prj().Substitute( oldstring ); and 6 or so other suggestions for your project planning document. Just curious, where is that document, and did these get recorded? Dick BTW, the PROJECT::Substitute() function can consult project specific variables, and if not found, it escalates to environment variables. /** * Function Substitute * replaces any project variable references found within @a aString with their * values. Any referenced variable is first sought in the PROJECT space, and if * not found, then sought in the environment. */ VTBL_ENTRY const wxString Substitute( const wxString aString ); It should be possible to stuff these variables into the top side of a PROJECT using the python project manager. ___ 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
[Kicad-developers] compiler warning
Can someone please fix this: /svn/kicad/product/common/common.cpp:48:13: warning: #warning You must use '--with-gnomeprint' or '--with-gtkprint' in your wx library configuration for full print capabilities. [-Wcpp] # warning You must use '--with-gnomeprint' or '--with-gtkprint' in your wx library configuration for full print capabilities. ^ /svn/kicad/product/3d-viewer/vrml_v2_modelparser.cpp: In member function ‘int VRML2_MODEL_PARSER::read_Transform()’: /svn/kicad/product/3d-viewer/vrml_v2_modelparser.cpp:160:143: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result] fscanf( m_file, %f %f %f %f, m_model-m_rotation[0], m_model-m_rotation[1], m_model-m_rotation[2], m_model-m_rotation[3]); ^ /svn/kicad/product/3d-viewer/vrml_v2_modelparser.cpp:167:175: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result] fscanf( m_file, %f %f %f %f, m_model-m_scaleOrientation[0], m_model-m_scaleOrientation[1], m_model-m_scaleOrientation[2], m_model-m_scaleOrientation[3]); ^ /svn/kicad/product/3d-viewer/vrml_v2_modelparser.cpp:180:43: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result] fscanf( m_file, %d, dummy ); ^ ___ 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 modules path strange behaviour
On 8/4/2014 11:24 AM, Dick Hollenbeck wrote: Wayne, In our 3/20/2014 project planning conversation I mentioned: newstring = Prj().Substitute( oldstring ); and 6 or so other suggestions for your project planning document. Just curious, where is that document, and did these get recorded? Dick Dick, It may have gotten lost in the chaos. I had about 25 emails plus converting the information from the CERN web-site when I created the road map and I may have just over looked it. I looked at the road map and didn't see anything specific to converting variables use the new project substitute method. If I missed anything I apologize for the oversight. Now that the initial road map is in place, the goal is to keep it up to date rather than me trying to keep track of ideas from a bunch of different input sources. If I missed anything, please let me know and I can update it or feel free to update it yourself if you find that works better for you. The source for the project road map can be found in the Documentation/development folder. The road map is built as part of the KiCad source documentation. You an also build the road map as a stand alone document by running `make dev-docs`. I used the Doxgen mark down syntax for plain text readability when editing. The road map is in the Documentation/development/road-map.md file. Wayne BTW, the PROJECT::Substitute() function can consult project specific variables, and if not found, it escalates to environment variables. /** * Function Substitute * replaces any project variable references found within @a aString with their * values. Any referenced variable is first sought in the PROJECT space, and if * not found, then sought in the environment. */ VTBL_ENTRY const wxString Substitute( const wxString aString ); It should be possible to stuff these variables into the top side of a PROJECT using the python project manager. ___ 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 modules path strange behaviour
2014-08-04 16:00 GMT+02:00 Wayne Stambaugh stambau...@verizon.net: On 8/4/2014 7:34 AM, yann jautard wrote: Le 04/08/2014 10:57, Nick Østergaard a écrit : 2014-08-04 10:00 GMT+02:00 yann jautard brico...@free.fr: And also what about the path to the 3D models directory that cannot be edited ? Is there a place where we can edit it ? That is a bug I believe, it is supposed to be set with an environment variable, but I guess it is just not catched anywhere. I noticed also we can't edit the KIPRJMOD and KISYSMOD variables related to the library table. I'm not sure that this should me environnement You can edit KIPRJMOD, KISYSMOD, AND KISYS3DMOD. They are environment variables so you have to edit them either system wide or user specific depending on your needs using your preferred method for editing environment variables on your system. You are not obligated to use any of these variables. You can specify the full path and/or file name (depending on the library type) for each library. Well, that is the thing... it does not work for me to define a KISYS3DMOD environment variable. I does not seem to be defined anywere already on my sytem, when I echo $KISYS3DMOD it is empty. But if I try to export it in a new terminal session as export KISYS3DMOD=foo, I do get foo when I echo it -- as expected, but kicad do not catch this. I open pcbnew from the same terminal as I set the env var in, then add a random footprint to the canvas, open the properties for it, then I go to the 3D settings tab, here the path is still listed as /usr/share/kicad/modules/packages3d, which I expected to be foo. I am on Archlinux, with 5041. Also in that regard I cannot use custom enviroment variables in the 3D Shape Name list IIRC. (at least last time I tested, I did not test this now, I can do that if requested) settings. In my opinion they should be project-specific, and stored in the project file. ( Like it was before the fp-lib table, I think. ) You can use project specific footprint library tables if you prefer rather than using the global footprint table. This is fairly well documented in both the CvPcb and Pcbnew reference manuals. Maybe the KISYS3DMOD variable should also be added to the library table window, and can be edited there ? KISYS3DMOD does not impact the loading of footprint libraries so has no context in the footprint library table. It is only used for loading 3D models. Putting it in the footprint library table editor would be confusing. Also I don't feel right about those variables relative to library tables : why only two variables ? I think there should be the same buttons under the variables list than under the libraries list, so we can add You are not limited to these 3 variables. You are free to define as many environment variables as you like or until you system runs out of memory. I use KILCLMOD to point to all my custom libraries. other research pathes. Like in eeschema. This will not happen. The path look up method is so broken that it's hard to know where to begin to explain it. There have been at least a dozen bug reports due to wrong footprints and components being loaded due to path search order issues. This has been discussed many times and the issue still exists in Eeschema. You can search the bug and mailing lists and find plenty of discussion about this issue. ___ 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
[Kicad-developers] eeschema modular kicad work
On 07/29/2014 02:02 PM, Wayne Stambaugh wrote: On 7/27/2014 1:33 PM, Dick Hollenbeck wrote: Gentlemen: In the course of trying to load the schematic editor directly under kicad.exe, by-passing eeschema top frame itself, I was exposed to a range of issues in the design of eeschema. Firstly, I discovered the most excellent work by Wayne Stambaugh regarding the schematic library containers. Thanks Dick. I wasn't really expecting any credit. I was just one of those things that needed fixed so I fixed it. I knew that that only way to move Eeschema forward was to fix the underlying library containers. I wish I had the time to finish the SCHEMATIC object and come up with a better way to handle sheet hierarchies. With those two pieces of the puzzle in place, we could start moving towards the new file format and other enhancement that we have discussed over the years. There are a long chain of dependencies here. LIB_EDIT_FRAME, to come up first, needs the libraries. That is obvious in words. But SCH_EDIT_FRAME typically loads the libraries before popping up LIB_EDIT_FRAME. You have a similar discussion about LIB_VIEW_FRAME. (I believe I solved all these similar problems for PCBNEW.) So now I went to solve them for EESCHEMA and produced an 11,000 line patch in 2.5 days. Remember that about only 1/7th of a patch line count are actual changed lines. The eeschema libraries were global, even if hidden behind a static class function, they were global. This would not dovetail into the notion of multiple open projects, each having its own set of libraries. So in the course of moving libraries into a project specific container, lots of changes were needed. First among those was to park the libraries container in the PROJECT. It was a necessary but insufficient solution for multiple open projects. One remaining issue is the fact that with multiple open projects you'd still have the same library open twice. Its hard to have the same problem in PCBNEW, (would have to duplicate project specific libraries) and even if you did, most of the plugins react to a change on disk and will re-cache if one of the copies is edited. We now have the libraries container in the PROJECT at least, and it is loaded on demand, by any _eeschema.kiface KIWAY_PLAYER that needs it. For 5 years or more no one questioned the terminology I introduced in the SWEET distributed library design regarding the definition of PART and a COMPONENT. The time to object was 5 years ago. So I went with those original terms per that prior design. LIB_COMPONENT is now LIB_PART. SCH_COMPONENT remains. Works for me. I've always thought that LIB_COMPONENT and SCH_COMPONENT naming was confusing. SCH_COMPONENT uses a link to a LIB_PART. That link was previously done by a library search on every Draw() call. This was easy since the library container was global, and the SCH_COMPONENT had access to the global container. Not so now. I seem to remember some other global variables used by the Draw() functions. The color table and possibly some visibility settings come to mind. I don't know if these have any context per project but it may be one of those things you want to look out for just in case. This also introduced an avoidable performance hit, which is avoided if a link to the LIB_PART is retained across SCH_COMPONENT redraws. You can pretty much now tell where this took me. Squarely into boost::shared_ptr and it companion class boost::weak_ptr. I will get it working in another half day and push it to its own branch, and would like folks to use EESCHEMA for a couple of days in that branch. My son and I are doing a very complex board together. And you can load the part editor and footprint editors directly from kicad.exe, for a single project now. Awesome work Dick! I'll try to do some testing as soon as I see the branch on launchpad. Wayne I pushed an early branch of this work to milestoneB. See the commit log for some of the details. The shared_ptr turned out to be a can of worms. No, several cans of worms, all stacked like a 2 miles of dominos. So I used a single one per LIB_PART according to this link here, and saved us all a lot of gray hairs. This is a very elegant solution which cherry picks not one IOTA more than what we needed: http://www.boost.org/doc/libs/1_55_0/libs/smart_ptr/sp_techniques.html#weak_without_shared I pushed this to branch milestoneB and would appreciate some testing help. There are some TODO items in my section of TODO.txt for this block of work. Most notable is moving the Color loading into the eeschema KIFACE::OnKifaceStart(). Also, the libraries are loaded more often than they should be, I think SCH_EDIT_FRAME needs to quit deliberately loading them and simply use the data on demand technique. You can see schematic editor loading libraries even if you load the
[Kicad-developers] Contributing footprints
Hi, I'm new to KiCad developement and wondering what is the designated way to contribute package footprints. Once I've created a pull request at github for a schematic symbol to github.com/KiCad/kicad-library, which was merged a few hour later. Now I've created a pull request to github.com/KiCad/SMD_Packages.pretty and there are neither comments nor a merge after 9 days. Is this github getting merged onto the bzr repository, or am I supposed to contribute using bzr? Or is there even an other way? Best regards Simon ___ 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] Contributing footprints
On 08/04/2014 11:15 AM, Simon Gansen wrote: Hi, I'm new to KiCad developement and wondering what is the designated way to contribute package footprints. Once I've created a pull request at github for a schematic symbol to github.com/KiCad/kicad-library, which was merged a few hour later. Now I've created a pull request to github.com/KiCad/SMD_Packages.pretty and there are neither comments nor a merge after 9 days. Is this github getting merged onto the bzr repository, or am I supposed to contribute using bzr? Or is there even an other way? I just email the footprints to Carl, and be sure to say thank you. He's made more progress in 5 months than the previous 5 years. ___ 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] compiler warning
Dick, here is my patch to the warnings in vrml_v2_modelparser.cpp From: Kicad-developers [kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of Dick Hollenbeck [d...@softplc.com] Sent: 04 August 2014 17:30 To: KiCad Developers Subject: [Kicad-developers] compiler warning Can someone please fix this: /svn/kicad/product/common/common.cpp:48:13: warning: #warning You must use '--with-gnomeprint' or '--with-gtkprint' in your wx library configuration for full print capabilities. [-Wcpp] # warning You must use '--with-gnomeprint' or '--with-gtkprint' in your wx library configuration for full print capabilities. ^ /svn/kicad/product/3d-viewer/vrml_v2_modelparser.cpp: In member function ‘int VRML2_MODEL_PARSER::read_Transform()’: /svn/kicad/product/3d-viewer/vrml_v2_modelparser.cpp:160:143: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result] fscanf( m_file, %f %f %f %f, m_model-m_rotation[0], m_model-m_rotation[1], m_model-m_rotation[2], m_model-m_rotation[3]); ^ /svn/kicad/product/3d-viewer/vrml_v2_modelparser.cpp:167:175: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result] fscanf( m_file, %f %f %f %f, m_model-m_scaleOrientation[0], m_model-m_scaleOrientation[1], m_model-m_scaleOrientation[2], m_model-m_scaleOrientation[3]); ^ /svn/kicad/product/3d-viewer/vrml_v2_modelparser.cpp:180:43: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result] fscanf( m_file, %d, dummy ); ^ ___ 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 fix_vrml_v2_modelparser_warnings.diff Description: fix_vrml_v2_modelparser_warnings.diff ___ 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] [PATCH] Anti-aliasing for the 3D-Viewer
imp, why the AA is only supported in wx3? #if wxCHECK_VERSION( 3, 0, 0 ) ? MRL ___ 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] [PATCH] Anti-aliasing for the 3D-Viewer
On 04.08.2014 22:45, Mário Luzeiro wrote: imp, why the AA is only supported in wx3? #if wxCHECK_VERSION( 3, 0, 0 ) This part was added by JP, a bit further up in the comments: // Note: We try to use anti aliasing if the graphic card allows that, // but only on wxWidgets = 3.0.0 (this option does not exist on wxWidgets 2.8). Bye, imp ___ 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] [PATCH] Anti-aliasing for the 3D-Viewer
Uhm.. anyway.. I found that my graphic card (and most of decent graphic card drivers I guess) can override the application preferences forcing it to whatever AA. I found also that with my graphic card with the AA in max settings the board textures will be rendered in black.. so we have some issue here.:/ MRL From: Martin Janitschke [i...@hannover.ccc.de] Sent: 04 August 2014 23:04 To: Mário Luzeiro; kicad-developers@lists.launchpad.net Subject: Re: [Kicad-developers] [PATCH] Anti-aliasing for the 3D-Viewer On 04.08.2014 22:45, Mário Luzeiro wrote: imp, why the AA is only supported in wx3? #if wxCHECK_VERSION( 3, 0, 0 ) This part was added by JP, a bit further up in the comments: // Note: We try to use anti aliasing if the graphic card allows that, // but only on wxWidgets = 3.0.0 (this option does not exist on wxWidgets 2.8). Bye, imp ___ 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] compiler warning
Mario, just FYI, you have used tabs in the fscanf alignment indentations. 2014-08-04 22:42 GMT+02:00 Mário Luzeiro mrluze...@ua.pt: Dick, here is my patch to the warnings in vrml_v2_modelparser.cpp From: Kicad-developers [kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of Dick Hollenbeck [d...@softplc.com] Sent: 04 August 2014 17:30 To: KiCad Developers Subject: [Kicad-developers] compiler warning Can someone please fix this: /svn/kicad/product/common/common.cpp:48:13: warning: #warning You must use '--with-gnomeprint' or '--with-gtkprint' in your wx library configuration for full print capabilities. [-Wcpp] # warning You must use '--with-gnomeprint' or '--with-gtkprint' in your wx library configuration for full print capabilities. ^ /svn/kicad/product/3d-viewer/vrml_v2_modelparser.cpp: In member function ‘int VRML2_MODEL_PARSER::read_Transform()’: /svn/kicad/product/3d-viewer/vrml_v2_modelparser.cpp:160:143: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result] fscanf( m_file, %f %f %f %f, m_model-m_rotation[0], m_model-m_rotation[1], m_model-m_rotation[2], m_model-m_rotation[3]); ^ /svn/kicad/product/3d-viewer/vrml_v2_modelparser.cpp:167:175: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result] fscanf( m_file, %f %f %f %f, m_model-m_scaleOrientation[0], m_model-m_scaleOrientation[1], m_model-m_scaleOrientation[2], m_model-m_scaleOrientation[3]); ^ /svn/kicad/product/3d-viewer/vrml_v2_modelparser.cpp:180:43: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result] fscanf( m_file, %d, dummy ); ^ ___ 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 modules path strange behaviour
On 8/4/2014 12:02 PM, Nick Østergaard wrote: 2014-08-04 16:00 GMT+02:00 Wayne Stambaugh stambau...@verizon.net: On 8/4/2014 7:34 AM, yann jautard wrote: Le 04/08/2014 10:57, Nick Østergaard a écrit : 2014-08-04 10:00 GMT+02:00 yann jautard brico...@free.fr: And also what about the path to the 3D models directory that cannot be edited ? Is there a place where we can edit it ? That is a bug I believe, it is supposed to be set with an environment variable, but I guess it is just not catched anywhere. I noticed also we can't edit the KIPRJMOD and KISYSMOD variables related to the library table. I'm not sure that this should me environnement You can edit KIPRJMOD, KISYSMOD, AND KISYS3DMOD. They are environment variables so you have to edit them either system wide or user specific depending on your needs using your preferred method for editing environment variables on your system. You are not obligated to use any of these variables. You can specify the full path and/or file name (depending on the library type) for each library. Well, that is the thing... it does not work for me to define a KISYS3DMOD environment variable. I does not seem to be defined anywere already on my sytem, when I echo $KISYS3DMOD it is empty. But if I try to export it in a new terminal session as export KISYS3DMOD=foo, I do get foo when I echo it -- as expected, but kicad do not catch this. I open pcbnew from the same terminal as I set the env var in, then add a random footprint to the canvas, open the properties for it, then I go to the 3D settings tab, here the path is still listed as /usr/share/kicad/modules/packages3d, which I expected to be foo. I am on Archlinux, with 5041. Environment variable defined in a shell session are only visible to applications launched from within that shell session. It has to be defined before or when you log in as a user to always be visible. Typically you would define it in ~/.profile or for all users in one of the scripts or your own custom script in /etc/profile.d. Although this can vary from distro to distro. Also in that regard I cannot use custom enviroment variables in the 3D Shape Name list IIRC. (at least last time I tested, I did not test this now, I can do that if requested) This may be a limitation of the 3D software design. I didn't write any of this so I cannot say one way or another if 3D model file paths accept the %ENV_VAR%/rest/of/path notation. The footprint library table will accept any environment variable. settings. In my opinion they should be project-specific, and stored in the project file. ( Like it was before the fp-lib table, I think. ) You can use project specific footprint library tables if you prefer rather than using the global footprint table. This is fairly well documented in both the CvPcb and Pcbnew reference manuals. Maybe the KISYS3DMOD variable should also be added to the library table window, and can be edited there ? KISYS3DMOD does not impact the loading of footprint libraries so has no context in the footprint library table. It is only used for loading 3D models. Putting it in the footprint library table editor would be confusing. Also I don't feel right about those variables relative to library tables : why only two variables ? I think there should be the same buttons under the variables list than under the libraries list, so we can add You are not limited to these 3 variables. You are free to define as many environment variables as you like or until you system runs out of memory. I use KILCLMOD to point to all my custom libraries. other research pathes. Like in eeschema. This will not happen. The path look up method is so broken that it's hard to know where to begin to explain it. There have been at least a dozen bug reports due to wrong footprints and components being loaded due to path search order issues. This has been discussed many times and the issue still exists in Eeschema. You can search the bug and mailing lists and find plenty of discussion about this issue. ___ 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 modules path strange behaviour
2014-08-05 1:24 GMT+02:00 Wayne Stambaugh stambau...@verizon.net: On 8/4/2014 12:02 PM, Nick Østergaard wrote: 2014-08-04 16:00 GMT+02:00 Wayne Stambaugh stambau...@verizon.net: On 8/4/2014 7:34 AM, yann jautard wrote: Le 04/08/2014 10:57, Nick Østergaard a écrit : 2014-08-04 10:00 GMT+02:00 yann jautard brico...@free.fr: And also what about the path to the 3D models directory that cannot be edited ? Is there a place where we can edit it ? That is a bug I believe, it is supposed to be set with an environment variable, but I guess it is just not catched anywhere. I noticed also we can't edit the KIPRJMOD and KISYSMOD variables related to the library table. I'm not sure that this should me environnement You can edit KIPRJMOD, KISYSMOD, AND KISYS3DMOD. They are environment variables so you have to edit them either system wide or user specific depending on your needs using your preferred method for editing environment variables on your system. You are not obligated to use any of these variables. You can specify the full path and/or file name (depending on the library type) for each library. Well, that is the thing... it does not work for me to define a KISYS3DMOD environment variable. I does not seem to be defined anywere already on my sytem, when I echo $KISYS3DMOD it is empty. But if I try to export it in a new terminal session as export KISYS3DMOD=foo, I do get foo when I echo it -- as expected, but kicad do not catch this. I open pcbnew from the same terminal as I set the env var in, then add a random footprint to the canvas, open the properties for it, then I go to the 3D settings tab, here the path is still listed as /usr/share/kicad/modules/packages3d, which I expected to be foo. I am on Archlinux, with 5041. Environment variable defined in a shell session are only visible to applications launched from within that shell session. It has to be defined before or when you log in as a user to always be visible. Typically you would define it in ~/.profile or for all users in one of the scripts or your own custom script in /etc/profile.d. Although this can vary from distro to distro. Yeah, I know that, I thought I expressed that in the string: I open pcbnew from the same terminal as I set the env var in I am able to use environment varibles in the fp-lib-table just fine. Also in that regard I cannot use custom enviroment variables in the 3D Shape Name list IIRC. (at least last time I tested, I did not test this now, I can do that if requested) This may be a limitation of the 3D software design. I didn't write any of this so I cannot say one way or another if 3D model file paths accept the %ENV_VAR%/rest/of/path notation. The footprint library table will accept any environment variable. OK. I do not know anything about it either. settings. In my opinion they should be project-specific, and stored in the project file. ( Like it was before the fp-lib table, I think. ) You can use project specific footprint library tables if you prefer rather than using the global footprint table. This is fairly well documented in both the CvPcb and Pcbnew reference manuals. Maybe the KISYS3DMOD variable should also be added to the library table window, and can be edited there ? KISYS3DMOD does not impact the loading of footprint libraries so has no context in the footprint library table. It is only used for loading 3D models. Putting it in the footprint library table editor would be confusing. Also I don't feel right about those variables relative to library tables : why only two variables ? I think there should be the same buttons under the variables list than under the libraries list, so we can add You are not limited to these 3 variables. You are free to define as many environment variables as you like or until you system runs out of memory. I use KILCLMOD to point to all my custom libraries. other research pathes. Like in eeschema. This will not happen. The path look up method is so broken that it's hard to know where to begin to explain it. There have been at least a dozen bug reports due to wrong footprints and components being loaded due to path search order issues. This has been discussed many times and the issue still exists in Eeschema. You can search the bug and mailing lists and find plenty of discussion about this issue. ___ 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:
