Bug 65549 - Export as PDF - Range property is ignored in recorded macro
Summary: Export as PDF - Range property is ignored in recorded macro
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
3.5.7.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-08 20:29 UTC by maskamar
Modified: 2014-02-26 19:31 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description maskamar 2013-06-08 20:29:33 UTC
Problem description: 

I want export as PDF part of the Calc document through the recorded macro. I recorded a macro. It is OK. But if I run it, the macro ignore property Range ("Selection") from PDF Options window.

This property is saved in the macro code:
...
Array("Selection",0,,com.sun.star.beans.PropertyState.DIRECT_VALUE)
...

Steps to reproduce:
1. Fill some cells with any data.
2. Start record macro.
3. Select some cells (not all).
4. File/Export as PDF.
5. Select "Selection" in Range setting on General tab.
6. "Export" and choose the destination.
7. Stop record macro and save it.
8. Check created document - it should be OK - only selected cells has been exported.
9. Run the macro.
10. Check created document - whole document has been exported.

I tested it in Ubuntu LibreOffice version 3.5.7.2 (Calc and Writer), Windows Xp LibreOffice 4.0.1.2 (Calc), 4.1.0.0beta1 (Calc) and in some version of OpenOffice (Calc).

All tested versions contain this bug. 


              
Operating System: All
Version: (See in Summary)
Comment 1 tommy27 2013-07-20 14:39:13 UTC
please post the whole code here and let's if it's really a bug.

however you should keep in mind that the macro recorder is a rough tool far from being perfect and sometimes it doesn't exactly record all the manual steps you do.

if you need help with macro you can subscribe to this forum ( 
http://forum.openoffice.org/en/forum/viewforum.php?f=20 ) and ask assistance to some of the "macro gurus" over there to edit the macro code to make it fit your needs.

P.S. changing version to first one reported by user (3.5.7)
Comment 2 QA Administrators 2014-02-02 02:06:57 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 3 QA Administrators 2014-02-26 19:31:27 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