View Issue Details

IDProjectCategoryView StatusLast Update
0002164ScribusUser Interfacepublic2009-05-04 03:08
ReporterringercAssigned Tojghali  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Platformx86 LinuxOSFedora CoreOS Version3
Product Version1.3.3.1 
Fixed in Version1.3.5svn 
Summary0002164: Guides won't let go of snapped items
DescriptionIf snap to guides is on, the guides won't release an item that's snapped to the guide if it is dragged slowly. The item must be "yanked" from the grasp of the guide.

This is a bug in the mouse drag handling of scribusview.cpp. It updates the item's actual position, but doesn't keep a separate record of where the current drag position is. Thus, if the user drags slowly the small drags don't accumulate into one big enough to budge the item from the grip of the guide.

This also causes the mouse drag position to be *way* out of sync with the actual location of the item.

I'll see if I can fix this, time permitting, but I'm leaving it unassigned in case some other kind person decides to beat me to it. To fix it, you'll need to give scribusview the ability to track the drag location of a pageitem separately to its actual location, then update it so that snap to effects apply to the real location but not drag location.
Additional InformationSee also the test file uploaded to the dupe 0003722
TagsNo tags attached.
Patch

Relationships

has duplicate 0003722 closed difficult to drag objects with snapping on 
has duplicate 0005129 closedjghali Horizontal guides are much "stickier" than vertical ones 
related to 0002584 closedfschmid 'Nudge' tool doesn't work correctly with guides 
related to 0003718 closedfschmid can't snap on "non-preferred" side 
related to 0003721 closedchristoph_s one guide always treated as if in a different place for snapping 

Activities

drekka

2005-07-29 04:22

reporter   ~0005777

Hi, I've just recently downloaded Scribus and hit this issue. I use guides a lot for laying up text and graphics so this is important to me. I would like to offer a suggested change to the above fix. Rather than having the snap code operate all the time, make it so that the snap code does not fire until the user drops the obejct. THis way you can drag without snap firing and it only come into play when you drop it near a guide.

TigerDE2

2006-08-26 18:24

reporter   ~0012320

This seems to be an issue in 1.3.3.3 for Win aswell...

jghali

2009-05-03 22:06

administrator   ~0021673

Fixed in 1.3.5svn

Issue History

Date Modified Username Field Change
2005-06-30 07:40 ringerc New Issue
2005-06-30 07:40 ringerc Status new => confirmed
2005-07-29 04:22 drekka Note Added: 0005777
2005-09-23 04:14 ringerc Relationship added related to 0002584
2006-05-08 06:33 mhanski Relationship added has duplicate 0003722
2006-05-08 06:35 mhanski Product Version 1.3.0cvs => 1.3.3.1
2006-05-08 06:35 mhanski Additional Information Updated
2006-05-08 09:38 mhanski Relationship added related to 0003718
2006-05-08 09:39 mhanski Relationship added related to 0003721
2006-08-26 18:24 TigerDE2 Note Added: 0012320
2008-04-29 22:47 jghali Relationship added has duplicate 0005129
2009-05-03 22:06 jghali Note Added: 0021673
2009-05-03 22:06 jghali Status confirmed => resolved
2009-05-03 22:06 jghali Fixed in Version => 1.3.5svn
2009-05-03 22:06 jghali Resolution open => fixed
2009-05-03 22:06 jghali Assigned To => jghali
2009-05-04 03:08 jghali Status resolved => closed