View Issue Details

IDProjectCategoryView StatusLast Update
0010071ScribusGeneralpublic2011-06-24 17:10
Reporterchappa-ai Assigned Tojghali  
PriorityhighSeveritymajorReproducibilityalways
Status closedResolutionduplicate 
PlatformOS XOSSnow LeopardOS Version10.6.7
Product Version1.4.0svn 
Summary0010071: Frames Don't Move to Correct Pages
DescriptionWith facing pages (what Scribus calls "Double Sided"), moving a frame from an even-numbered page to an odd-numbered page (excluding the first page) with a left x-coordinate of 0.00 causes the frame to be part of the previous even-numbered page in the Outline window instead of part of the destination page.
Steps To ReproduceCreate a 3-page Double Sided document with Points as the measurement unit. Place an image frame on page 2 with an X-Pos value of 0.00. Copy the frame and drag the copy to Page 3 with an X-Pos value of 0.00 (note that the red page highlighting indicating the active page switches from Page 2 to Page 3). Open the Outline window and notice that the copied frame is still under Page 2 instead of Page 3. Increase the copied frame's X-Pos value from 0.00 to 1.00 and notice in Outline that it moves from Page 2 to Page 3. Change the value back to 0.00 and it moves back to Page 2 in Outline (but still appears to be on Page 3 in the main window). With Page 3 still active, cut the copied frame (Command-X), click on Page 3 to ensure it really is the active page, and paste the frame (Command-V). Now Outline shows the frame properly on Page 3 with the 0.00 X-Pos value.
Additional InformationIt would also be helpful having a Send to Page option for frames, similar to Send to Level and Send to Layer.
TagsNo tags attached.
Patch

Relationships

duplicate of 0007389 new Choice of page an object belongs to 

Activities

jghali

2011-06-24 17:05

administrator   ~0026469

Duplicate of 0007389

jghali

2011-06-24 17:10

administrator   ~0026470

Please check if a bug exists on the bug tracker before submitting a new one. A simple search with the "wrong page" in the search field would have allowed you to find the duplicate in this case. More than half of the bugs you already submitted have been closed as duplicate or 'no change required'.

Issue History

Date Modified Username Field Change
2011-06-24 13:08 chappa-ai New Issue
2011-06-24 17:05 jghali Note Added: 0026469
2011-06-24 17:05 jghali Relationship added duplicate of 0007389
2011-06-24 17:05 jghali Status new => resolved
2011-06-24 17:05 jghali Resolution open => duplicate
2011-06-24 17:05 jghali Assigned To => jghali
2011-06-24 17:05 jghali Status resolved => closed
2011-06-24 17:10 jghali Note Added: 0026470