When I open the footprint selector it looks like this:
The list on the left is too narrow, and I usually end up expanding it so I can read the category names properly.
Is there a way to make it permanently wider?
When I open the footprint selector it looks like this:
The list on the left is too narrow, and I usually end up expanding it so I can read the category names properly.
Is there a way to make it permanently wider?
There are many informations missing in your question.
FWIW the column-width is saved (and restored) on my system (v7.0.7 and 7.99 on Win10), with some limitations regarding the minimum column width. So in principle the requested function is implemented, it could be a bug in your special case.
Application: KiCad x64 on x64
Version: 7.0.7, release build
Libraries:
wxWidgets 3.2.2
FreeType 2.12.1
HarfBuzz 6.0.0
FontConfig 2.14.1
libcurl/7.88.1-DEV Schannel zlib/1.2.13
Platform: Windows 10 (build 19045), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
Date: Aug 14 2023 02:42:39
wxWidgets: 3.2.2 (wchar_t,wx containers)
Boost: 1.81.0
OCC: 7.7.1
Curl: 7.88.1-DEV
ngspice: 40
Compiler: Visual C++ 1936 without C++ ABI
Build settings:
KICAD_SPICE=ON
Windows 10. 4k screen with 175% scaling. Single monitor.
I open the Footprint Library Browser by opening a symbol’s properties window and clicking on the library icon next to the footprint text field.
The column width is saved in the Footprint Assignment Tool, just not when I access it as described.
Maybe it’s some combination of the scaling and resolution causing it to reset because Kicad thinks it is too large/small?
Maybe it’s some combination of the scaling and resolution causing it to reset because Kicad thinks it is too large/small?
Could be. I’m sure I have read similar issues provoked by high-resolution monitors (4k) already on the gitlab bugtracker, but I couldn’t find any this time.
I would recommend to search for yourself on gitlab, and if you find nothing open a new issue. Mention the resolution + windows-scaling. In principle it’s known that wxwidgets (the used GUI-framework) has some problems with 4k-scaling.
good bugreport, but next time please use the standard KiCad / KiCad Source Code / kicad · GitLab section, not the wx-subsection (my mention of “wxwidgets” was only guesswork).
And I would recommend the builtin “Kicad–>Help–>Report bug”-command. This opens the correct gitlab location, prefills the issue with the most needed version information and makes bugreporting easier.
It’s been moved to:
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.