EEschema zooming, scrolling bug

Bug #1822442 reported by Anton on 2019-03-30
This bug affects 3 people
Affects Status Importance Assigned to Milestone

Bug Description

See attachment

Anton (antonpupkov) wrote :
Anton (antonpupkov) wrote :

Application: kicad
Version: (5.1.0-rc2-26-g643d884fd), release build
    wxWidgets 3.0.4
    libcurl/7.63.0 OpenSSL/1.1.1a zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.34.0
Platform: Linux 4.19.8-arch1-1-ARCH x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.63.0
    Compiler: GCC 8.2.1 with C++ ABI 1013

Build settings:

Anton (antonpupkov) wrote :

Problem when scaling with centering on the cursor. When I make the maximum reduction, it has a limited zoom and, of course, the canvas has limited dimensions. As you can see in the video, when the cursor goes beyond a certain invisible border when scaled, it automatically returns to the invisible borders of this rectangle. Looks like a bug. If the canvas zoom is limited and the size, respectively, too, why make this invisible border? Pay attention to scrolling. Runners should be the full width of the scroll bar when the zoom is minimal.

drojf (drojfjord) wrote :

I'm not a dev, but just to add some clear repro instructions:

- zoom out as far as possible
- move your cursor to the bottom right corner of the screen
- zoom in

The moment you zoom in, your mouse cursor will jump to within the bounds of some invisible rectangle, where the invisible rectangle is a portion of the sheet.

Note that the invisible rectangle **isn't** the furthest bounds of where you can put components - you actually can put components outside the rectangle. So this could potentially be a problem if you put a very small component outside the bounds of the invisible rectangle, as you can't zoom in to look at it. But it's a bit hard to think of situations where this could cause really big problems, since usually you don't use up that much space making the schematics.

Anton (antonpupkov) wrote :

About the fact that the space outside the frame of the sheet is not used I can argue with you. EESchema, as for me, is used as a standalone schema editor - as a draft. I create one scheme in it, with a cat I make into it any changes to the copy made, so that it can be traced to what was at the beginning and at the end. As you can see in the video, zoom has limitations for zooming in and out - that's good for me. Why bother with something when there is a rather large margin to reduce. As I measured the dimensions of the canvas in real units of about 7,500 mm by 3,500 mm. This is quite a lot. And, as for me, this is quite enough. What happens if this invisible border is extended to the size of the canvas? It is clear that if you fill the entire canvas with elements, here the limit is the size of the RAM.

Seth Hillbrand (sethh) on 2019-03-31
Changed in kicad:
importance: Undecided → Medium
milestone: none → 5.1.1
status: New → Triaged

I am also affected by this bug, is it possible that this is related to this other zooming issue:

Changed in kicad:
milestone: 5.1.1 → 5.1.2
Changed in kicad:
milestone: 5.1.2 → 5.1.3
tags: added: eeschema
Jon Evans (craftyjon) on 2019-05-26
Changed in kicad:
assignee: nobody → Jon Evans (craftyjon)
Jon Evans (craftyjon) on 2019-06-10
Changed in kicad:
assignee: Jon Evans (craftyjon) → nobody
Changed in kicad:
milestone: 5.1.3 → 5.1.4
Changed in kicad:
milestone: 5.1.4 → 5.1.5
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments