1. 16 May, 2013 1 commit
  2. 10 May, 2013 2 commits
  3. 09 May, 2013 1 commit
  4. 08 May, 2013 2 commits
    • Wayne Stambaugh's avatar
      Footprint library table work, minor fixes, and code cleaning. · cf86e18f
      Wayne Stambaugh authored
      * Fix a bug when full file name and path are passed to FOOTPRINT_INFO::
        ReadFootprintFiles() which I created in bug fix lp:593989.
      * Fix a wxString debug assertion in EDA_APP::InitEDA_Appl() when the KICAD
        environment variable is defined as an empty string.
      * Add error dialog when libraries cannot be found in system search path
        when loading footprint using the select footprint dialog.
      * Add footprint library name column to the EDA_LIST_DIALOG when selecting
        footprints from the list.
      * Allow reading all columns from the selected row in EDA_LIST_DIALOG.
      * Remove redundant sort from EDA_LIST_DIALOG constructor
      * Add library name member variable and accessors to FOOTPRINT_INFO.
      * Make headers translatable for Eeschema select component from list dialog.
      * Add some helper methods to FPID for identifying the FPID type and validity.
      * Remove a bunch of trailing whitespace and add missing license comments.
      cf86e18f
    • jean-pierre charras's avatar
      More work on CPOLYGONS_LIST class. · 2e6969fe
      jean-pierre charras authored
      2e6969fe
  5. 07 May, 2013 2 commits
  6. 06 May, 2013 3 commits
  7. 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
  8. 04 May, 2013 1 commit
  9. 03 May, 2013 1 commit
  10. 02 May, 2013 1 commit
  11. 01 May, 2013 4 commits
  12. 28 Apr, 2013 1 commit
    • Lorenzo Marcantonio's avatar
      Removed the SAFE_DELETE macro. · 3b1ddd95
      Lorenzo Marcantonio authored
      In most case the assignment to null was not necessary since it was easily provable that the (local) variable wouldn't have referenced after that anyway.
      3b1ddd95
  13. 27 Apr, 2013 1 commit
  14. 26 Apr, 2013 1 commit
    • Wayne Stambaugh's avatar
      Post Pcbnew NETLIST_READER change clean up. · 81271ad4
      Wayne Stambaugh authored
      * Tweak the NETLIST_READER code to allow for component footprint names that
        are not found in any library to generate a warning instead of an error and
        update the board accordingly.
      * Don't display undo warning in netlist dialog when dry run option selected.
      * Rename netlist_reader_common.cpp to netlist_reader.cpp
      * Rename netlist_reader_firstformat.cpp to legacy_netlist_reader.cpp
      * Rename netlist_reader_kicad.cpp to kicad_netlist_reader.cpp
      * Remove cvpcb/read_write_cmpfile.cpp and move the single function it
        contained into cvframe.cpp
      * Remove cvpcb/loadcmp.cpp and move the single function it contained into
        class_DisplayFootprintsFrame.cpp.
      * Remove cvpcb/readschematicnetlist.cpp and move the single function it
        contained into cvframe.cpp.
      * Remove cvpcb/setvisu.cpp and move the few functions it contained into
        the appropriate source file.
      81271ad4
  15. 25 Apr, 2013 1 commit
    • Wayne Stambaugh's avatar
      Pcbnew NETLIST_READER improvements. · 61b4f8a9
      Wayne Stambaugh authored
      * Create separate NETLIST object to hold contents of netlist files.
      * Read entire netlist and footprint link files before making applying
        changes to board.
      * Add BOARD::ReplaceNetlist() function to eliminate the calls between the
        NETLIST_READER, PCB_EDIT_FRAME, and BOARD objects.
      * Change placement of new components below the center of the current board
        or in the center of the page if the BOARD is empty.
      * Add dry run option to netlist dialog to print changes to message control
        without making changes.
      * Add button to netlist dialog to allow saving contents of message control
        to a file.
      * Eliminate the need to compile netlist_reader_*.cpp in both CvPcb and Pcbnew.
      * Add netlist_reader_*.cpp to the pcbcommon library.
      * Remove redundant load component link file code from CvPcb.
      * Modify CvPcb new to work with the new NETLIST_READER object.
      * Add compare() function and < and == operators to FPID object.
      * Add REPORTER class to hide an underlying string writing implementation for
        use in low level objects.  Thank you Dick for the idea.
      * Lots of minor coding policy, Doxygen comment, and missing license fixes.
      61b4f8a9
  16. 18 Apr, 2013 2 commits
  17. 14 Apr, 2013 1 commit
  18. 11 Apr, 2013 2 commits
  19. 10 Apr, 2013 2 commits
  20. 09 Apr, 2013 4 commits
  21. 08 Apr, 2013 1 commit
    • Dick Hollenbeck's avatar
      Implement "KiCad s-epression" support for boost::property_tree's ptree, the 8 · 6bf3d7cd
      Dick Hollenbeck authored
      bit string version of property_tree. The ram resident structure of the ptree is
      mostly compatible with one created using the xml_parser from
      boost::property_tree, with slight differences in the way atoms are stored. The
      result is you can use Format() to convert from xml to s-expression, but not the
      other way around. You can write a simple s-expression beautifier in just a few
      lines of code.
      
      The main value however is the s-expression parser, i.e. Scan(), which is an
      alternative to crafting a custom recursive descent parser for a particular
      grammar. The tipping point depends on whether you want to read only a small
      portion of a much larger document. If so, then using the ptree will likely be a
      "faster to code" route. Documentation on how to navigate a ptree can be found on
      the boost website and there are a number of examples in the
      pcbnew/eagle_plugin.cpp file in this project. Powerful path navigation support
      makes it easy to extract a subset of a ptree.
      6bf3d7cd
  22. 07 Apr, 2013 2 commits
  23. 06 Apr, 2013 3 commits