- 27 Mar, 2014 1 commit
-
-
jean-pierre charras authored
Dialog Freeroute: if freeroute.jar is find in kicad binaries, it is run as a standard java application, not as web applcation Very minor other fixes FPC_(SMD_type)_footprintwizard.py wizard finished.
-
- 23 Mar, 2014 2 commits
-
-
jean-pierre charras authored
Eeschema: does not close when the schematic file given in command line to run Eeschema is not found (i.e. when starting a new project). Otherwise one cannot start a new schematic project.
-
Marco Serantoni authored
-
- 22 Mar, 2014 2 commits
-
-
Marco Serantoni authored
-
jean-pierre charras authored
Minor fixes for Windows: move resources from dso to .exe, to have the application icon in executable, and therefore shown in shortcuts. pcb_calculator: minor coding style fix.
-
- 21 Mar, 2014 4 commits
-
-
Dick Hollenbeck authored
-
Dick Hollenbeck authored
-
jean-pierre charras authored
CvPcb: Fix crashes when starting cvPcb (could be Windows Specific) and after closing the footprint viewer.
-
Dick Hollenbeck authored
-
- 20 Mar, 2014 6 commits
-
-
Wayne Stambaugh authored
* Use wxFileName::GetPathSeparator() instead of redefining them.
-
Dick Hollenbeck authored
-
Dick Hollenbeck authored
-
Dick Hollenbeck authored
! The initial testing of this commit should be done using a Debug build so that all the wxASSERT()s are enabled. Also, be sure and keep enabled the USE_KIWAY_DLLs option. The tree won't likely build without it. Turning it off is senseless anyways. If you want stable code, go back to a prior version, the one tagged with "stable". * Relocate all functionality out of the wxApp derivative into more finely targeted purposes: a) DLL/DSO specific b) PROJECT specific c) EXE or process specific d) configuration file specific data e) configuration file manipulations functions. All of this functionality was blended into an extremely large wxApp derivative and that was incompatible with the desire to support multiple concurrently loaded DLL/DSO's ("KIFACE")s and multiple concurrently open projects. An amazing amount of organization come from simply sorting each bit of functionality into the proper box. * Switch to wxConfigBase from wxConfig everywhere except instantiation. * Add classes KIWAY, KIFACE, KIFACE_I, SEARCH_STACK, PGM_BASE, PGM_KICAD, PGM_SINGLE_TOP, * Remove "Return" prefix on many function names. * Remove obvious comments from CMakeLists.txt files, and from else() and endif()s. * Fix building boost for use in a DSO on linux. * Remove some of the assumptions in the CMakeLists.txt files that windows had to be the host platform when building windows binaries. * Reduce the number of wxStrings being constructed at program load time via static construction. * Pass wxConfigBase* to all SaveSettings() and LoadSettings() functions so that these functions are useful even when the wxConfigBase comes from another source, as is the case in the KICAD_MANAGER_FRAME. * Move the setting of the KIPRJMOD environment variable into class PROJECT, so that it can be moved into a project variable soon, and out of FP_LIB_TABLE. * Add the KIWAY_PLAYER which is associated with a particular PROJECT, and all its child wxFrames and wxDialogs now have a Kiway() member function which returns a KIWAY& that that window tree branch is in support of. This is like wxWindows DNA in that child windows get this member with proper value at time of construction. * Anticipate some of the needs for milestones B) and C) and make code adjustments now in an effort to reduce work in those milestones. * No testing has been done for python scripting, since milestone C) has that being largely reworked and re-thought-out.
-
Dick Hollenbeck authored
-
Dick Hollenbeck authored
! The initial testing of this commit should be done using a Debug build so that all the wxASSERT()s are enabled. Also, be sure and keep enabled the USE_KIWAY_DLLs option. The tree won't likely build without it. Turning it off is senseless anyways. If you want stable code, go back to a prior version, the one tagged with "stable". * Relocate all functionality out of the wxApp derivative into more finely targeted purposes: a) DLL/DSO specific b) PROJECT specific c) EXE or process specific d) configuration file specific data e) configuration file manipulations functions. All of this functionality was blended into an extremely large wxApp derivative and that was incompatible with the desire to support multiple concurrently loaded DLL/DSO's ("KIFACE")s and multiple concurrently open projects. An amazing amount of organization come from simply sorting each bit of functionality into the proper box. * Switch to wxConfigBase from wxConfig everywhere except instantiation. * Add classes KIWAY, KIFACE, KIFACE_I, SEARCH_STACK, PGM_BASE, PGM_KICAD, PGM_SINGLE_TOP, * Remove "Return" prefix on many function names. * Remove obvious comments from CMakeLists.txt files, and from else() and endif()s. * Fix building boost for use in a DSO on linux. * Remove some of the assumptions in the CMakeLists.txt files that windows had to be the host platform when building windows binaries. * Reduce the number of wxStrings being constructed at program load time via static construction. * Pass wxConfigBase* to all SaveSettings() and LoadSettings() functions so that these functions are useful even when the wxConfigBase comes from another source, as is the case in the KICAD_MANAGER_FRAME. * Move the setting of the KIPRJMOD environment variable into class PROJECT, so that it can be moved into a project variable soon, and out of FP_LIB_TABLE. * Add the KIWAY_PLAYER which is associated with a particular PROJECT, and all its child wxFrames and wxDialogs now have a Kiway() member function which returns a KIWAY& that that window tree branch is in support of. This is like wxWindows DNA in that child windows get this member with proper value at time of construction. * Anticipate some of the needs for milestones B) and C) and make code adjustments now in an effort to reduce work in those milestones. * No testing has been done for python scripting, since milestone C) has that being largely reworked and re-thought-out.
-
- 19 Mar, 2014 2 commits
-
-
maciej. authored
-
jean-pierre charras authored
Pad editor dialog: Better tests and error messages about issues in pad settings. Fis also an other hard to translate error messge.
-
- 18 Mar, 2014 2 commits
-
-
jean-pierre charras authored
kicad-install.sh: fix bad url for legacy libraries. Add the same script hich does not need a bazaar account to download Kicad (using https instead of ssh to create branches)
-
jean-pierre charras authored
-
- 16 Mar, 2014 2 commits
-
-
unknown authored
-
jean-pierre charras authored
bitmap2component: add management of image resolution: Is read from file, when exists, and can be modified in bitmap2component. It also fix issue #747631
-
- 14 Mar, 2014 4 commits
-
-
Orson authored
Corrected the error message about required OpenGL version for GAL. Fixed pcb_calculator .desktop file.
-
jean-pierre charras authored
-
Marco Serantoni authored
-
Marco Serantoni authored
-
- 13 Mar, 2014 4 commits
-
-
Marco Serantoni authored
-
Maciej Suminski authored
-
jean-pierre charras authored
Footprint Editor: fix a crash when the dialog to set pad properties is called from the main toolbar (i.e. to define the default setting for new pads, and not to edit an existing pad)
-
Maciej Suminski authored
* Fix Python scripting error causing pcbnew_wrap.cxx to fail to build. * Fix OpenGL canvas ratsnest missing connections in copper zones.
-
- 12 Mar, 2014 4 commits
-
-
Maciej Suminski authored
-
Maciej Suminski authored
-
Maciej Suminski authored
Workarounded SWIG problems (does not support nested C++ classes, more on the subject: http://www.swig.org/Doc1.3/SWIGPlus.html#SWIGPlus_nested_classes).
-
Maciej Suminski authored
-
- 10 Mar, 2014 1 commit
-
-
Marco Serantoni authored
-
- 09 Mar, 2014 1 commit
-
-
jean-pierre charras authored
-
- 08 Mar, 2014 2 commits
-
-
jean-pierre charras authored
-
jean-pierre charras authored
Rework on 3D viewer (work in progress): Disable or enable layers, grid or 3D footprint shapes should be now faster.
-
- 07 Mar, 2014 1 commit
-
-
Wayne Stambaugh authored
* Make block rotate command honor the rotation angle setting. Thank you Umesh Mohan <mohan.umesh@gmail.com> for the patch. * Change block rotate undo command from UR_ROTATE to UR_CHANGED so consecutive rotations do not lead to round errors and for proper undo in case the user changes the rotation angle setting between block rotations.
-
- 06 Mar, 2014 2 commits
-
-
Cirilo Bernardo authored
-
Wayne Stambaugh authored
-