* Use colons for consistency with other dialogs.
* Use default size to allow sizers to determine dialog size.
* Use "segment" rather than abbreviation "segm".
* Use width and height to describe text instead of X and Y.
* Add spacer to improve layout when resizing dialog.
* Use colons consistently in labels.
* Use default dialog size to allow sizers to size dialog.
* Fix control alignment and spacing consistency.
* Add spacer to improve layout when resizing dialog.
* Make control spacing and alignment consistent.
* Use default dialog size and to allow the sizers to do thier job.
* Add colons to per item labels for consistency.
* Fix error message box title capitalization per UI policy.
* Remove hard coded dialog size and let the sizers do their job.
* Minor UI policy text fixes.
* Minor text changes to improve readability.
* Minor tool tip changes to improve readability.
* Split graphic circle objects into two 180 degree arcs to prevent the
VRML_LAYER::AddCircle() function from obscuring objects in the hole
(cut out) area of the circle.
* Enable CvPcb launching in stand alone mode.
* Enable footprint editor launching in stand alone mode.
* Remove some dead code left over from the change in CvPcb behavior.
* These changes were made for users who prefer to work in a less project-
centric work flow. KiCad should not be in the business of dictating
work flow whenever possible.
If the image was being rotated by a valid amount but not 270 degrees due to the if statements it would already report that there was an invalid value.
Also due to the strnicmp only checking the first 2 characters which was valid for 0* but not the rest of the numbers, some values would be able to work that shouldn't
* If a hotkey is set to "unassigned" (typically by causing a conflict), it
is not loaded correctly. The loader interprets "unassigned" as "keep the
default assignment", which leads to a conflict later that causes an
assertion failure.
Replace %zu by %d in wxString::Format (%zu format not always known by wxString::Format on Windows, depending on the way wxWidgets was built ) in a few messages
* Mainly the wxDialog that was opened when the wizard is created is now no more created by the wizard frame CTOR. On some W.M. it created a serious issue related to the way Event Loops are managed. Now the user has to call it by the toolbar tool.
* 2 settings not saved in config are now saved.
* a few other minor enhancements
* better icon in footprint wizard frame
Remove a few #define relative to the wxWidgets 2.8 version, no more supported.
footprint wizard frame: now shows messages from footprints python scripts. Especially usefull when a parameter is incorrect. Fix also an other issue (IO exception error) with some python scripts when they are usin a print command to output messages (now they use the new message window.
footprint wizard frame: now shows messages from footprints python scripts. Especially usefull when a parameter is incorrect. Fix also an other issue (IO error) with some scripts which were usint the print command to output messages (now they use the nes message window.
Simon Wells
Wayne Stambaugh
Simon Wells
jean-pierre charras
Tomasz Wlostowski
Maciej Suminski
Chris Pavlina
Simon Wells
Brian Sidebotham
unknown