After the Cancel operation the schematic shrinks. I tried to not move the cross-hair cursor when I took the screeshots. Notice that clicking OK instead of Cancel doesn’t trigger the problem.
I just tested in my system and it is still the same but once you click OK, it doesn’t happen anymore, however if you close the schematic and open it again, it goes back to the same behavior.
Application: KiCad Schematic Editor x64 on x64
Version: 7.0.5-36-g7d9222926a, 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: Jun 3 2023 05:14:43
wxWidgets: 3.2.2 (wchar_t,wx containers)
Boost: 1.81.0
OCC: 7.6.3
Curl: 7.88.1-DEV
ngspice: 40
Compiler: Visual C++ 1936 without C++ ABI
Build settings:
KICAD_SPICE=ON
thank you for your replies. I have something new to add. The example that I have reported concerned projects using an A4 page size. I have opened few minutes ago a project using an A3 page size and the problem is opposite. After ESC or Cancel the schematic becomes larger instead of shrinking.
Mmmmh, interesting…
Ok, I’ve never used the bugtracker so I will look how it works before reporting.
Unfortunately the gitlab bot will close issues that reference anything other than the most recent stable version of KiCad as potentially already fixed. Since @der.ule has replicated the behavior on 7.0.5, they could provide the version info for the description and you can re-open the issue. Alternatively you can upgrade yourself (perhaps a good idea if you have the option) and use the new version info to re-open the issue.
and this is the result of the update to version 7.0.5! That’s why I am still with 7.0.1. This project is already terminated and without errors. I’m reverting now to 7.0.1.
yes, I know, but I can’t see any reason to ignore simulation errors and I still consider that a bug. But strangely, the issue in the bugtracker regarding this problem has been closed.
I have just added a couple of comments hoping that the issue will be reopened.
It is close because it is fixed in the coming v8, apparently it is not possible to fix it in the current v7 because there are some issues with “the strings”
