1. 05 Mar, 2014 1 commit
  2. 03 Mar, 2014 1 commit
  3. 18 Feb, 2014 1 commit
    • Henner Zeller's avatar
      Eeschema component selection dialog improvements. · 392e3a0a
      Henner Zeller authored
      * Allow to select units in components that have more than one right in the
        component chooser dialog.
      * Keep chosen unit in history.
      * Show preview of current component unit as thumbnail image next to the
        description box.
      * Fixes lp:1280567
      392e3a0a
  4. 17 Feb, 2014 1 commit
  5. 11 Feb, 2014 2 commits
  6. 08 Feb, 2014 1 commit
  7. 07 Feb, 2014 3 commits
  8. 06 Feb, 2014 3 commits
  9. 04 Feb, 2014 2 commits
  10. 03 Feb, 2014 4 commits
  11. 02 Feb, 2014 2 commits
  12. 31 Jan, 2014 2 commits
  13. 30 Jan, 2014 1 commit
  14. 29 Jan, 2014 1 commit
  15. 28 Jan, 2014 2 commits
  16. 27 Jan, 2014 2 commits
  17. 26 Jan, 2014 1 commit
  18. 25 Jan, 2014 1 commit
  19. 21 Jan, 2014 1 commit
  20. 20 Jan, 2014 1 commit
  21. 18 Jan, 2014 1 commit
  22. 15 Jan, 2014 1 commit
    • Maciej Suminski's avatar
      BOARD_CONNECTED_ITEMs do not store net code anymore (m_NetCode field), instead... · d62b47a0
      Maciej Suminski authored
      BOARD_CONNECTED_ITEMs do not store net code anymore (m_NetCode field), instead net info is stored using a pointer to NETINFO_ITEM.
      GetNet() refers to the net code stored in the NETINFO_ITEM. SetNet() finds an appropriate NETINFO_ITEM and uses it.
      Removing GetNet() & SetNet() (and the whole net code idea) requires too many changes in the code (~250 references to the mentioned functions).
      BOARD_CONNECTED_ITEMs by default get a pointer to NETINFO_ITEM that stores unconnected items. This requires for all BOARD_CONNECTED_ITEMs to have a parent (so BOARD* is accessible). The only orphaned item is BOARD_DESIGN_SETTINGS::m_Pad_Master, but it does not cause any issues so far.
      Items that do not have access to a BOARD (do not have set parents) and therefore cannot get net assigned, by default get const static NETINFO_LIST::ORPHANED.
      
      Performed tests:
      - loaded .kicad_pcb, KiCad legacy board, Eagle 6.0 board, P-CAD board - all ok
      - load a simple project, reload netlist after changing connections in eeschema - ok
      - save & reload a board - ok, but still contain empty nets
      - remove everything, restore with undo - ok
      - remove everything, reload netlist - ok
      - changing net names (all possibilites: empty->existing, empty->not existing, existing->empty, existing->not existing) - all ok
      - zones: when net is changed to a net that does not have any nodes besides the zone itself, it does not get filled
      d62b47a0
  23. 10 Jan, 2014 2 commits
    • jean-pierre charras's avatar
      f0412874
    • Maciej Suminski's avatar
      Changed the way of looking up NETINFO_ITEM using net names (using... · bf80cc77
      Maciej Suminski authored
      Changed the way of looking up NETINFO_ITEM using net names (using boost::unordered_map). Added a hash function (wxString) for that. Introduced NETINFO_ITEM::GetNetItem( wxString ). BOARD::FindNet() uses the map.
      Net codes are updated upon net list update. (BOARD::ReplaceNetlist())
      Added in some places (mostly class_board.cpp) pad->SetNet() calls to synchronize net codes.
      On creation of NETINFO_LIST, the first NETINFO_ITEM is added (the unconnected items net).
      Removed COMPONENT_NET::m_netNumber, as it was not used anywhere.
      Added an assert to D_PAD::GetNetname(), checking if net code and net name is consistent for unconnected pads. Added an assert for NETINFO_LIST::AppendNet() to assure that appended nets are unique.
      
      It seems that at this point:
      - Updating net lists works fine. The only difference between the file ouput is that after changes it contains empty nets as well.
      - Nets are not saved in the lexical order. Still, net names and net codes are properly assigned to all items in the .kicad_pcb file. It is going to be addressed in the next commit. I believe it should not create any problems, as pads are sorted by their net names anyway (NETINFO_LIST::buildPadsFullList())
      
      Performed tests:
      - Created a blank PCB, saved as pic_programmer.kicad_pcb (from demos folder). Updated net lists. .kicad_pcb file (comparing to the results from master branch) differ with net order (as mentioned before), net codes and timestamps.
      - Removed some of components from the above .kicad_pcb file and updated net lists. Modules reappeared. .kicad_pcb file differs in the same way as described above.
      - Trying to change a pad net name (via properties dialog) results in assert being fired. It is done on purpose (as there is a call to GetNetname() and net name and net code do not match). This will not happen after the next commit.
      - Prepared a simple project (starting with schematics). Imported net list, changed schematic, reimported net list - changes are applied.
      - Eagle & KiCad legacy boards seem to load without any problem.
      
      bf80cc77
  24. 08 Jan, 2014 1 commit
  25. 02 Jan, 2014 2 commits