A better short term solution would be to push the modified status down
to at least PCB_BASE_FRAME::SetDesignSettings() by first comparing the
new BOARD_DESIGN_SETTINGs against the existing ones in the board and
setting the modified flag accordingly to prevent false positives. Like
this:
The ideal long term solution would be to keep track of the board
modification state within the BOARD object as it's modified but that is
a much more involved task.
On 9/22/2015 1:08 PM, Stefan wrote:
> oups
>
> It should be
> A)
> All the values in Grid/Pads/Pad Mask Clearance/Differental Paris
> are saved in the .pro file and does not affect the .kicad_pcb
>
> B)
> All the values in "Texts And Drawings" is on the other hand
> saved in the .kicad_pcb file.
>
A better short term solution would be to push the modified status down FRAME:: SetDesignSettin gs() by first comparing the SETTINGs against the existing ones in the board and
to at least PCB_BASE_
new BOARD_DESIGN_
setting the modified flag accordingly to prevent false positives. Like
this:
void PCB_BASE_ FRAME:: SetDesignSettin gs( const BOARD_DESIGN_ SETTINGS&
aSettings )
{
wxASSERT( m_Pcb );
if( m_Pcb-> GetDesignSettin gs() != aSettings )
m_Pcb- >SetDesignSetti ngs( aSettings );
{
OnModify();
}
}
The ideal long term solution would be to keep track of the board
modification state within the BOARD object as it's modified but that is
a much more involved task.
On 9/22/2015 1:08 PM, Stefan wrote: Differental Paris
> oups
>
> It should be
> A)
> All the values in Grid/Pads/Pad Mask Clearance/
> are saved in the .pro file and does not affect the .kicad_pcb
>
> B)
> All the values in "Texts And Drawings" is on the other hand
> saved in the .kicad_pcb file.
>