We had been maintaining the tree collapse state for "clear" actions
where the user went back to no object search. This was helpful in the
case where we had previous items (e.g. last placed element)
But this causes isses when a sub element was previously select on GTK.
Now we choose safety for GTK over the pretty display
Fixes https://gitlab.com/kicad/code/kicad/issues/8198
Returning a reference to a temporary value crashes when the value is
deallocated before use. Passing a full string fixes the crash and
allows NVRO on the temporary value.
Attempt to parse BOM output file extension from BOM plugin header, and
append it to the "%O" argument in the BOM plugin command line.
Fixes#6943
(cherry picked from commit f54ab830f6)
This updates multi unit symbols uniquely even when the schematic is
unannotated (and therefore there are multiple symbols with the same
reference). We attempt to enfore a single unit update per symbol and
test for both value and reference commonality before assuming that the
unit is part of the larger multi-unit symbol
Fixes https://gitlab.com/kicad/code/kicad/issues/7117
It was previously fixed to 1500x900 pixels, that can be too large.
The window size and position is also now retained during a session.
From master branch, commit 60152bc
So many things can go wrong with this control in GTK. We have to
collapse the tree when updating the search string to avoid a crash when
referencing a child object but collapsing the tree will iterate over
elements and crash when we have deleted a symbol.
The temporary fix for this nonsense is to carefully order the calls.
We only need to collapse the search tree if we are not keeping our state
(in other words if we are fully re-building the tree)
Fixes https://gitlab.com/kicad/code/kicad/issues/6910
(cherry picked from commit 8af4cf88a0)
- The default value is 0.01 mm (according to comments and similar to the 3D viewer
settings that uses 0.02 mm)
- The export dialog has now 3 values 1 micron, 0.01mm (default) and 0.1 mm
From Master branch, commits a9feb1c and 5db7580
From Master, commit 686254.
In some cases a created pad stack name had the same name as an other pad stack
having a slightly different shape, thus creating pads with a incorrect shape on board.
Fixes#6495 for the 5.1.10 branch.
We are using the unix separator in filenames in all platforms.
However on Windows some filenames can contain native separators.
We now ensure all filenames use the unix separator before comparison.
Fix#6742
Fix#5740Fix#4126
This is a stupid solution because SAMBA sends invalid events and wxWidgets decides to assert rather than ignore them.
Why can't people just use Windows Server shares :(
Apparently wxFileName stats the file on Windows when using the == operator
which causes slow response when adding sheets in designs saved on remote
shares.
Fixes https://gitlab.com/kicad/code/kicad/-/issues/5596
wxTextFile uses wxFile which uses write syscalls which means its unbuffered.
This makes file IO more expensive against network shares where it will flush far too aggressively.
wxTextFile is fine for reads however.
wxFloatingPointValidator has some limitations, but mainly the change is a try
to fix an annoying issue (#6670) we cannot reproduce but is probably related
to a locale issue.
Wayne Stambaugh
Seth Hillbrand
Marek Roszko
jean-pierre charras
Jon Evans
Graham Keeth
Johannes Maibaum
Jeff Young
Mikołaj Wielgus
Jan Mrázek
qu1ck
Ian McInerney