Skip to content

eeschema: position of find-result unfavorable after moving of find-dialog

Description

Normally eeschema positions search-results on the left of the find-dialog. This works relatively well (well enough for me. Minor complaint: the position of the navigator panel is not considered).

After moving the find-dialog, closing the find dialog and on the next search-action the auto-positioning of the search result is bad and the search-result is displayed approximately under the find-dialog. This is possibly related to my last report #8969 (closed).

Steps to reproduce

  1. open a project with a schematic with some components with the same text (example is the 3.3V power port)
  2. Hit Ctrl+F for search-dialog, type "+3.3V", ENTER, get the first 3.3V-symbol. This is displayed at the left of the find-dialog, good predictable and good visible. Picture 1.
  3. move the search-dialog to the top right of the work space. Picture 2. search again, than close search dialog.
  4. invoke again the search dialog. observe the reposition of the dialog at screen-center (see #8969 (closed)). The search-text-field is still written with the last search-value (in this case: +3.3V). Click "Find"-button to find next 3,3V-power-port
  5. Kicad finds the next occurance (power port), but it displays it also centered, directly under the find-dialog. picture3.
  6. move the find-dialog slightly left and only now you can see the found search result. Picture4.
  7. If you again click the find-button on the find-dialog, the next results are also displayed on the same screen position in the middle.
  8. I would want a position of the search-result as in point2 - always predictable and good visible.

pics_complete

KiCad Version

Application: KiCad Schematic Editor (64-bit)

Version: (5.99.0-11663-g8172737d6f), release build

Libraries:
	wxWidgets 3.1.5

Platform: Windows 10 (build 19041), 64-bit edition, 64 bit, Little endian, wxMSW

	wxWidgets: 3.1.5 (wchar_t,STL containers)
	Boost: 1.75.0
	OCC: 7.5.0
	Curl: 7.74.0-DEV
	ngspice: 34
	Compiler: Visual C++ 1928 without C++ ABI

Build settings:
	KICAD_USE_OCC=ON
	KICAD_SPICE=ON
Edited by Maik Freitag