(Some of these items don't currently get printed, but
there's no sense in leaving a latent bug around in case
we ever change our minds.)
(cherry picked from commit 877c6bce89)
We use IN for INCH as units, but IN is defined in a Windows header
(cherry picked from commit b0fe4df3c5)
(cherry picked from commit 0acdabd1eb)
(cherry picked from commit eaa1e6d594)
Move most of the update firing to the file system watcher (except for
windows network shares that still need timed updated). Gate the repo
status for sync
Fixes https://gitlab.com/kicad/code/kicad/-/issues/20133
(cherry picked from commit 5027a562e4)
Push the git checks from the main thread into child threads to prevent
resource contention in some cases where Windows machines might have many
files in git that are _also_ being managed by Google Drive
Fixes https://gitlab.com/kicad/code/kicad/-/issues/20078
(cherry picked from commit 2c54ab277b)
The big grey X and dimming the component made it look like the component
was no longer a part of the circuit, rather than just being excluded for
a single purpose.
The changes the display to make a more subtle grey outline with an icon
in the corner to indicate that this refers to simulation.
(cherry picked from commit 878cf768d6)
wx infobar generic will wrap text, changing the stored label data on
instantiation. Since we might expand the infobar later, this presents
an issue as the newlines are then baked into the string.
We do two things here: keep a copy of the original string to make sure
that we can reset it on update and do a hard calculation of the minimum
height for the infobar to ensure we are displaying the full text string
Fixes https://gitlab.com/kicad/code/kicad/issues/19799
wxBitmapBundle assumes the smallest bitmap added is the intended "original" size for a particular use case.
And generally that is probably true. However, we re-use icons in some places where we intend for them to start at 16
or start at 24. This is problematic when GetPreferredBitmapSizeFor is called for calculations because it'll return the
16*scale number instead of 24*scale number. So let's just allow passing in a min height restriction to KiBitmapBundle
for when we reuse bitmaps.
The m_imageData buffer in the BITMAP_BASE is an
internal implementation - the public API to persist the
data to a stream appears to be SaveImageData - so use that,
which hides the implementation (and generates the image data
"live" when needed).
Remove the public access to the m_imageData buffer as it isn't
needed for public use, and also is misleading.
Also break out the formatting of the data into KICAD_FORMAT,
as it's currently replicated in eeschema/pcb/pagelayout
formatting code.
Fixes: https://gitlab.com/kicad/code/kicad/-/issues/19772
Seth Hillbrand