7.99 - Footprint editor wont save (all) modified text sizes?

I am trying to change the text size of the Reference or Value of a(ny) footprint, but the text size is not commited in the save. Changing the text size of the text “${REFERENCE}” does change.

(Right click > Open image in new tab to expand to a readable size)

FootprintTextSizeWontSave

Changing the text sizes for the Value and Reference from the Footprint Properties window also won’t save my changes. Oddly enough, the “${REFERENCE}” text isn’t even visible in the Footprint Properties window.

FootprintTextSizeWontSave2

I have a feeling I am missing something obvious, but I am noticing this behaviour with footprints created with a 6.99 nightly and editing these on a recent 7.99 build, but also on footprints created in 7.99.

I can find no mention of this on the bug tracker or the forum, so I am guessing it’s only me?

Application: KiCad Footprint Editor x64 on x64

Version: 7.99.0-1755-gbb27f09108, 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: Jul  6 2023 08:33:26
	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:

I can find no mention of this on the bug tracker or the forum, so I am guessing it’s only me?

False guess, you need to clean your crystal ball.
I can reproduce the same (Version: 7.99.0-1650-gf3122184df, from 27.06.), so go ahead and open a gitlab bug issue.
One wish: don’t work with the animated gif pictures - it’s hard to interprete what the user is really doing. Use a good, detailed step-by-step description (open FP xyz → doubcleclick REF**-string → opens reference properties dialog → change width+height==3mm → close reference properties dialog → save FP (no need for SaveAs) → reload FP → change is reverted).
And than additional pictures/videos are good, but don’t rely alone on the gif-pictures.

Thanks for confirming, I will open an issue as soon as Gitlab is up and running again (I’m getting 503/500 errors atm) and link it back here for reference.

Do you suggest making separate issues for the text size not saving and for the text field not being visible in the footprint properties?

As for the animated gif, it indeed didn’t have the desired effect but I thought i’d try something different after a separate discussion yesterday where I thought text alone didn’t convey the message properly. I’ll stick to plain text

Cheers for the feedback and verification.

Videos can be extremely good but animated gifs aren’t. Almost any screencast application can save mp4 or something like that.

3 Likes

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.