Opened 14 years ago

Closed 14 years ago

#2711 closed patch (fixed)

Strange legend behaviour

Reported by: brushtyler Owned by: brushtyler
Priority: critical: causes crash or data corruption Milestone: Version 1.5.0
Component: GUI Version: Trunk
Keywords: Cc:
Must Fix for Release: No Platform: All
Platform Version: Awaiting user input: no

Description

See the screenshot attached. The layer symbol is in a strange position. Here how reproduce it.

Load more than 1 layer (2 layers) Move the upper layer bottom Double click on the new upper layer simbol

Sometimes QGis crashes when you do doubleclick on the simbol

Attachments (3)

img0.png (12.2 KB ) - added by brushtyler 14 years ago.
legend image
patch.diff (1.1 KB ) - added by brushtyler 14 years ago.
patch
fix2711.diff (593 bytes ) - added by brushtyler 14 years ago.
new patch (use this, contains only the patch for this ticket)

Download all attachments as: .zip

Change History (10)

by brushtyler, 14 years ago

Attachment: img0.png added

legend image

comment:1 by lutra, 14 years ago

Platform: DebianAll

Great Giuseppe,

you find a way to reproduce this problem! :)

Hopefully fixing this will fix also the "crazy jumping legend item" problem...

cheers

comment:2 by jef, 14 years ago

see also #2528

comment:3 by lutra, 14 years ago

see also #2018

by brushtyler, 14 years ago

Attachment: patch.diff added

patch

comment:4 by brushtyler, 14 years ago

Owner: changed from nobody to brushtyler

I hope my patch resolves these 3 tickets once and for all.

There is also another fix, to avoid crashes if you drag a layer and drop it in an invalid place.

Did I earn an svn account?? :P

comment:5 by lutra, 14 years ago

Type: bugpatch

Great Giuseppe! :)

by brushtyler, 14 years ago

Attachment: fix2711.diff added

new patch (use this, contains only the patch for this ticket)

in reply to:  4 comment:6 by brushtyler, 14 years ago

Replying to brushtyler:

There is also another fix, to avoid crashes if you drag a layer and drop it in an invalid place.

I see that the other fix is related with ticket #699.

So I splitted the first attached patch in 2 parts. Use fix2711.diff as patch for this ticket.

comment:7 by brushtyler, 14 years ago

Resolution: fixed
Status: newclosed

Fixed by applying patch (from r13640)

Note: See TracTickets for help on using tickets.