Improper Grabbing of placed imaged in eeschema

Bug #1787966 reported by Ron Burkey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Medium
Seth Hillbrand

Bug Description

I am using the nightly build for version 6.0.0-rc1.

This problem relates to the case in which you have placed a large bit-mapped image into eeschema, and have objects atop it ("in front" of it), such as library symbols, wires, text, etc. (Imagine the image being a background for the entire sheet, used as merely a temporary guide for placement of the true spreadsheet objects.)

Under these circumstances, "Grabbing" (G) an item sometimes grabs both the object and the image behind it. For example, Grabbing a symbol does *not* grab the background image (it grabs only the symbol), but Grabbing a wire or endpoint of a wire *does* grab both the wire/endpoint *and* the background image. The effect, of course, is that when you move the object you've grabbed, you inadvertently move the image as well. (But the background image doesn't visually move until after you drop the object you actually though you were moving, so you don't even know you're doing it.)

Unfortunately, you can't just easily work around this by moving the image afterward to where it was supposed to be, because of Bug #1787404.

Tags: eeschema
Revision history for this message
Bob Cousins (bobcousins42) wrote :
Revision history for this message
Ron Burkey (rburkey) wrote : Re: [Bug 1787966] Re: Improper Grabbing of placed imaged in eeschema

On 08/20/2018 03:02 PM, Bob Cousins wrote:
> Is this a duplicate of https://bugs.launchpad.net/kicad/+bug/1785989 ?
>
No. They're both mine, so I know. :-) This one is indisputably a bug
that indicates incorrect handling of Grabs, whereas Bug #1785989 is my
wish that a particular use-case for images was supported better.

But if Bug #1785989 were fixed, I admit that it would be ideal for me
and that I /personally/ would no longer care about Bug #1787966, since
in that case the images I'm concerned about could be locked in place and
never Grabbed at all.

Changed in kicad:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 5.0.1
Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

Fixed in revision 1f60d8fdbf10c388434cd775db1dcb3ae6212a24
https://git.launchpad.net/kicad/patch/?id=1f60d8fdbf10c388434cd775db1dcb3ae6212a24

Changed in kicad:
status: Triaged → Fix Committed
assignee: nobody → Seth Hillbrand (sethh)
Changed in kicad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.