1. 04 May, 2014 1 commit
  2. 30 Apr, 2014 1 commit
  3. 27 Apr, 2014 2 commits
  4. 25 Apr, 2014 1 commit
    • Lorenzo Marcantonio's avatar
      TRACK/SEGVIA cleanup · 3f2c0e1a
      Lorenzo Marcantonio authored
      - SEGVIA becomes VIA
      - Drill size moved from TRACK to VIA
      - Removed shape from TRACK, becomes ViaType in VIA
      - GetTrace becomes GetTrack, for uniformity
      - Some minor constification and typo fixes
      3f2c0e1a
  5. 19 Apr, 2014 1 commit
    • Dick Hollenbeck's avatar
      *) Switch kicad.exe to using KIFACE modules for all major top level windows. · 0d6560a2
      Dick Hollenbeck authored
          Eeschema, Pcbnew, and Cvpcb all run under the same process now,
          FOR THE VERY FIRST TIME!
      
      *)  Added KIWAY::PlayerCreate(), PlayerClose(), and PlayersClose().
      
      *)  Factored FRAME_T into <frame_type.h> from ID_DRAWFRAME_TYPE.
      
      *)  Found that the following command line is helpful for collecting all the *.kiface
          files into the <build>/kicad/ directory so that kicad can find them.
      
            $ cp `find . -name '*.kiface'` kicad/
      
          Maybe somebody will want to rework how the CMake files are organized so all
          the binaries can go into the same place.  See python-a-mingw-us.
      
      *)  This might fix the problem on the Mac where child process windows were not
          coming to the front.  See ->Raise() in kicad/mainframe.cpp.
      
      *)  You can set USE_KIFACE to 0 in kicad/mainframe.cpp to chain load child exes
          instead of using the KIFACE modules directly, i.e. revert.
      0d6560a2
  6. 20 Mar, 2014 1 commit
    • Dick Hollenbeck's avatar
      * KIWAY Milestone A): Make major modules into DLL/DSOs. · 2c67c3ff
      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.
      2c67c3ff
  7. 18 Mar, 2014 1 commit
  8. 09 Mar, 2014 1 commit
  9. 08 Mar, 2014 1 commit
  10. 05 Mar, 2014 1 commit
  11. 28 Feb, 2014 1 commit
  12. 24 Feb, 2014 1 commit
  13. 08 Feb, 2014 1 commit
  14. 03 Feb, 2014 1 commit
  15. 01 Feb, 2014 1 commit
  16. 30 Jan, 2014 1 commit
  17. 29 Jan, 2014 1 commit
  18. 28 Jan, 2014 1 commit
  19. 25 Jan, 2014 1 commit
  20. 08 Jan, 2014 1 commit
  21. 27 Nov, 2013 1 commit
  22. 18 Oct, 2013 1 commit
  23. 14 Oct, 2013 1 commit
    • jean-pierre charras's avatar
      Pcbnew: Fix issue when displaying net names and/or pad numbers including the... · 082b8326
      jean-pierre charras authored
      Pcbnew: Fix issue when displaying net names and/or pad numbers including the "<" char in drc dialog, because drc dialog uses an wxHtmlWindow to display drc messages, and the "<" char has a special meaning and is not allowed in texts (now replaced by the" &lt;" sequence in messages displayed in html)
      Eeschema: replace "<" and ">" by "(" and ")" in autogenerated net names, to avoid other issues in html messages.
      Very minor other fixes.
      082b8326
  24. 13 Oct, 2013 1 commit
    • jean-pierre charras's avatar
      specctra_export.cpp: fix a bug in my export function to 3D viewer which... · 7f648995
      jean-pierre charras authored
      specctra_export.cpp: fix a bug in my export function to 3D viewer which generates bad shapes for holes generated by outlines
      inside the main board outlines.
      specctra_export.cpp: always approximate arcs in outlines by 36 segm for 360 degrees,
      even for arc angle which differs from 90 degrees.
      90 degrees is the default when creating an arc, but the arc value can be edited and have any value between 0 and 360 degrees.
      Previously, 9 segments were used regardless the arc angle.
      7f648995
  25. 07 Oct, 2013 2 commits
  26. 04 Oct, 2013 2 commits
  27. 10 Sep, 2013 1 commit
  28. 28 Aug, 2013 1 commit
  29. 20 Aug, 2013 1 commit
  30. 26 May, 2013 1 commit
  31. 25 May, 2013 1 commit
  32. 16 May, 2013 1 commit
  33. 14 May, 2013 1 commit
  34. 09 May, 2013 1 commit
  35. 08 May, 2013 1 commit
  36. 05 May, 2013 1 commit
    • Lorenzo Marcantonio's avatar
      Migrated the interfaces accepting angles to the double type · d00c83cd
      Lorenzo Marcantonio authored
      The plan goes like this:
      - eeschema still uses int in decidegrees
      - all the other things internally use double in decidegrees (or radians
        in temporaries)
      - in pcbnew UI the unit is *still* int in decidegrees
      
      The idea is to have better precision everywhere while keeping the user with int i
      angles. Hopefully, if a fractional angle doesn't come in from the outside, everything
      should *look* like an integer angle (unless I forgot something and it broke)
      
      When the time comes, simply updating the UI for allowing doubles from the user should
      be enough to get arbitrary angles in pcbnew.
      d00c83cd
  37. 04 May, 2013 1 commit