1. 07 Jul, 2014 3 commits
  2. 26 Jun, 2014 1 commit
  3. 24 Jun, 2014 1 commit
    • Dick Hollenbeck's avatar
      1) Add 32 Cu Layers. · 4578ea8b
      Dick Hollenbeck authored
      2) Change from legacy Cu stack to counting down from top=(F_Cu or 0).
         The old Cu stack required knowing the count of Cu layers to make
         sense of the layer number when converting to many exported file types.
         The new Cu stack is more commonly used, although ours still gives
         B_Cu a fixed number.
      3) Introduce class LSET and enum LAYER_ID.
      4) Change *.kicad_pcb file format version to 4 from 3.
      5) Change fixed names Inner1_Cu-Inner14_Cu to In1_Cu-In30_Cu and their
         meanings are typically flipped.
      6) Moved the #define LAYER_N_* stuff into legacy_plugin.cpp where they
         can die a quiet death, and switch to enum LAYER_ID symbols throughout.
      7) Removed the LEGACY_PLUGIN::Save() and FootprintSave() functions.
         You will need to convert to the format immediately, *.kicad_pcb and
         *.kicad_mod (=pretty) since legacy format was never going to know
         about 32 Cu layers and additional technical layers and the reversed Cu
         stack.
      4578ea8b
  4. 20 Jun, 2014 1 commit
    • jean-pierre charras's avatar
      Remove 2 global variables: g_DrawBgColor and g_ShowPageLimits. · 7c99a242
      jean-pierre charras authored
      They are now member of EDA_DRAW_FRAME.
      This change could fix Bug #1330781 (Background color change in Eeschema affects background color in Pcbnew)
      Show page limits has meaning only for the schematic editor,  the board editor and the page layout editor.
      Draw background color selection exists only in eeschema and  page layout editor.
      In pcbnew, only a black background is allowed.
      A side effect is now the user should set the background color in schematic editor, and the library editor (2 different options).
      The default is still the white color.
      7c99a242
  5. 16 Jun, 2014 1 commit
  6. 12 Jun, 2014 1 commit
    • Lorenzo Marcantonio's avatar
      Fixes #1186269 · bee6b9f9
      Lorenzo Marcantonio authored
      - Refactored the common part of cursor key movement and crosshair update
        in the various GeneralControl
      - Add x10 movement with the keyboard (CTRL modifier)
      - Avoid fixup of the cursor position by dummy mouse movements generated
        by cursor warping (original analysis and idea Chris Gibson)
      - Do key handling in a way to permit sub-pixel cursor movement 
      bee6b9f9
  7. 10 Jun, 2014 1 commit
  8. 05 Jun, 2014 1 commit
  9. 04 Jun, 2014 1 commit
  10. 03 Jun, 2014 2 commits
  11. 25 May, 2014 1 commit
  12. 16 May, 2014 2 commits
  13. 15 May, 2014 1 commit
    • jean-pierre charras's avatar
      DXF export: fix incorrect export of polygons having thick outline (like... · bb0804ec
      jean-pierre charras authored
      DXF export: fix incorrect export of polygons having thick outline (like zones): Thick segments of outline were drawn like lines with no thickness.
      Fix ( workaround only) crash (Windows only) when a quasi modal frame (like footprint viewer) was called from a dialog (like the component properties dialog in schematic editor).
      Very minor other fixes.
      bb0804ec
  14. 13 May, 2014 1 commit
  15. 12 May, 2014 1 commit
  16. 09 May, 2014 4 commits
  17. 05 May, 2014 4 commits
  18. 04 May, 2014 6 commits
    • Dick Hollenbeck's avatar
      Modular-Kicad milestone B), minor portions: · a2227a75
      Dick Hollenbeck authored
      *) KIWAY_PLAYER::IsModal() is now a retained state, controlled by SetModal()
      
      *) Fully re-work the KIWAY_PLAYER::ShowModal() to use a nested event loop.
      
      *) Add support to DIALOG_SHIM for a "quasi-modal" dialog presentation and mode.
         See top of dialog_shim.cpp about that for benefits and need.
      
      *) You can now pick footprint from the schematic component field dialog, although
         if you do this before you open the BOARD, you will only get the global footprint
         libraries, not also the project specific ones.  Opening the BOARD first avoids this
         problem.
      
      This is the first example of cross KIFACE invocation, it is also the first
      instance of using a TOP_FRAME other than FRAME_PCB as the first thing. It works,
      but it's missing support for opening the project specific table because
      historically the FRAME_PCB did that. This is now starting to expose all the near
      term needs for KIWAY_PLAYER <-> PROJECT interaction, independence and out of
      sequence usage.
      
      A fix for this will be coming in a few days.
      
      However it mostly starts to show why the KIWAY is terribly useful and important.
      a2227a75
    • Dick Hollenbeck's avatar
      Modular-Kicad milestone B), minor portions: · fef168aa
      Dick Hollenbeck authored
      *) KIWAY_PLAYER::IsModal() is now a retained state, controlled by SetModal()
      
      *) Fully re-work the KIWAY_PLAYER::ShowModal() to use a nested event loop.
      
      *) Add support to DIALOG_SHIM for a "quasi-modal" dialog presentation and mode.
         See top of dialog_shim.cpp about that for benefits and need.
      
      *) You can now pick footprint from the schematic component field dialog, although
         if you do this before you open the BOARD, you will only get the global footprint
         libraries, not also the project specific ones.  Opening the BOARD first avoids this
         problem.
      
      This is the first example of cross KIFACE invocation, it is also the first
      instance of using a TOP_FRAME other than FRAME_PCB as the first thing. It works,
      but it's missing support for opening the project specific table because
      historically the FRAME_PCB did that. This is now starting to expose all the near
      term needs for KIWAY_PLAYER <-> PROJECT interaction, independence and out of
      sequence usage.
      
      A fix for this will be coming in a few days.
      
      However it mostly starts to show why the KIWAY is terribly useful and important.
      fef168aa
    • Lorenzo Marcantonio's avatar
      Constification of HitTest and GetParent · 342016b6
      Lorenzo Marcantonio authored
      In particular HitTest for zones *do not* select the nearest vertex/edge as a side effect
      342016b6
    • Lorenzo Marcantonio's avatar
      Constification of HitTest and GetParent · 85c5aa22
      Lorenzo Marcantonio authored
      In particular HitTest for zones *do not* select the nearest vertex/edge as a side effect
      85c5aa22
    • Dick Hollenbeck's avatar
    • Dick Hollenbeck's avatar
  19. 03 May, 2014 2 commits
    • Dick Hollenbeck's avatar
      Modular-Kicad milestone B), major portions: · 991926d3
      Dick Hollenbeck authored
      *) Rework the set language support, simplify it by using KIWAY.  Now any major
         frame with a "change language" menu can change the language for all KIWAY_PLAYERs
         in the whole KIWAY.  Multiple KIWAYs are not supported yet.
      
      *) Simplify "modal wxFrame" support, and add that support exclusively to
         KIWAY_PLAYER where it is inherited by all derivatives.  The function
         KIWAY_PLAYER::ShowModal() is in the vtable and so is cross module capable.
      
      *) Remove the requirements and assumptions that the wxFrame hierarchy always
         had PCB_EDIT_FRAME and SCH_EDIT_FRAME as immediate parents of their viewers
         and editors. This is no longer the case, nor required.
      
      *) Use KIWAY::Player() everywhere to make KIWAY_PLAYERs, this registers the
         KIWAY_PLAYER within the KIWAY and makes it very easy to find an open frame
         quickly.  It also gives control to the KIWAY as to frame hierarchical
         relationships.
      
      *) Change single_top to use the KIWAY for loading a KIFACE and instantiating
         the single KIWAY_PLAYER, see bullet immediately above.
      
      *) Add KIWAY::OnKiwayEnd() and call it from PGM_BASE at program termination, this
         gives the KIFACEs a chance to save their final configuration dope to disk.
      
      *) Add dedicated FRAME_T's for the modal frames, so m_Ident can be tested and
         these modal frames are distinctly different than their non-modal equivalents.
         KIWAY_PLAYER::IsModal() is !not! a valid test during the wxFrame's constructor,
         so this is another important reason for having a dedicated FRAME_T for each
         modal wxFrame.
      
      On balance, more lines were deleted than were added to achieve all this.
      991926d3
    • Dick Hollenbeck's avatar
      Modular-Kicad milestone B), major portions: · 25d1ab40
      Dick Hollenbeck authored
      *) Rework the set language support, simplify it by using KIWAY.  Now any major
         frame with a "change language" menu can change the language for all KIWAY_PLAYERs
         in the whole KIWAY.  Multiple KIWAYs are not supported yet.
      
      *) Simplify "modal wxFrame" support, and add that support exclusively to
         KIWAY_PLAYER where it is inherited by all derivatives.  The function
         KIWAY_PLAYER::ShowModal() is in the vtable and so is cross module capable.
      
      *) Remove the requirements and assumptions that the wxFrame hierarchy always
         had PCB_EDIT_FRAME and SCH_EDIT_FRAME as immediate parents of their viewers
         and editors. This is no longer the case, nor required.
      
      *) Use KIWAY::Player() everywhere to make KIWAY_PLAYERs, this registers the
         KIWAY_PLAYER within the KIWAY and makes it very easy to find an open frame
         quickly.  It also gives control to the KIWAY as to frame hierarchical
         relationships.
      
      *) Change single_top to use the KIWAY for loading a KIFACE and instantiating
         the single KIWAY_PLAYER, see bullet immediately above.
      
      *) Add KIWAY::OnKiwayEnd() and call it from PGM_BASE at program termination, this
         gives the KIFACEs a chance to save their final configuration dope to disk.
      
      *) Add dedicated FRAME_T's for the modal frames, so m_Ident can be tested and
         these modal frames are distinctly different than their non-modal equivalents.
         KIWAY_PLAYER::IsModal() is !not! a valid test during the wxFrame's constructor,
         so this is another important reason for having a dedicated FRAME_T for each
         modal wxFrame.
      
      On balance, more lines were deleted than were added to achieve all this.
      25d1ab40
  20. 02 May, 2014 2 commits
  21. 30 Apr, 2014 1 commit
  22. 28 Apr, 2014 1 commit
  23. 25 Apr, 2014 1 commit