Bug 60010

Summary: SLIDESHOW: Some objects are deformed in slidshow
Product: LibreOffice Reporter: sylvain_msl
Component: ImpressAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: ign_christian
Priority: medium    
Version: 3.6.2.2 release   
Hardware: Other   
OS: Linux (All)   
Whiteboard: BSA
Crash report or crash signature: Regression By:
Attachments: Both views (edit mode and slideshow) of the same slide

Description sylvain_msl 2013-01-29 11:12:16 UTC
Created attachment 73823 [details]
Both views (edit mode and slideshow) of the same slide

Problem description:

(Excuse my poor English, it is not my mother tongue)
Some objects are vertically dilated in slideshow mode comparing to the editing mode.
Tested on various versions and OS (XP, Ubuntu, Xubuntu, Mac OSX)

Steps to reproduce:
1. Create a large rectangle with horizontal hatchings
2. Create a widely vertical rectangle with no border, horizontal hatchings (space between each hatching twice as wide as the first rectangle) 
3. Align these two rectangles in a way the hatchings are perfectly aligned
4 Change to slideshow mode (F5) 

Current behavior:

The two rectangles are no longer aligned.
One of them is dilated so the hatchings are no longer aligned and the spacing between them varies vertically.


Expected behavior:

The hatchings stay aligned in slideshow mode

              
Operating System: Ubuntu
Version: 3.6.2.2 release
Comment 1 richard_g 2013-01-29 11:41:51 UTC
Dilatation problem confirmed with other OOo/AOO/LibO versions on any OS.

Can also be seen on slides having charts with a title on its vertical axis.
Steps to reproduce:

-Calc:
 1. build an XY chart with titles for horizontal axis and vertical axis
 2. copy the chart

-Impress :
 1. paste the copied chart into a slide.
 3. try switching between edit mode et slideshow mode.

 When in slideshow mode, the tile of the vertical axis is stretched along the height of the screen.

Tested with LibO 346 on Windows Vista 32 bit SP2

richard_g
Comment 2 A (Andy) 2013-03-23 23:06:39 UTC
not reproducible with LO 4.0.1.2 (Win7 Home, 64bit)

Does this issue still persist for you with the latest release of LO?
Comment 3 ign_christian 2013-06-03 07:14:32 UTC
Hi Sylvain

Please attach sample presentation so anyone here could test using same source.
Comment 4 QA Administrators 2014-02-02 02:06:31 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 5 QA Administrators 2014-02-26 19:31:02 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO