Calc database have macro CreateSheet. Have macro - CloseSheet. CreateSheet: createNewSheet fill with data user: press button Print Calc: calculation of needed for characters (width,height) user: run macro CloseSheet. CloseSheet: close this sheet Calc: trying to printing garbage with lethal ending. This occurs when I switch on AutoCalulation. Printing of the sheet received a slow speed.
to close sheet used brutal form: Sheet.close(true) May be this was guilty.
^^ - wrong - ^^ to close sheet used brutal form: Document.close(true) May be this was guilty.
Could you give a try to a newer version like 3.5.5 ? Then could you precise which macro you're talking about ? (I haven't found "CreateSheet", perhaps just missed it). Is it a macro included in LO out of the box ?
Macro: selectSheetByName(thisComponent, "Price blank") dispatchURL(thisComponent,".uno:SelectAll") dispatchURL(thisComponent,".uno:Copy") secondDoc = StarDesktop.loadComponentFromUrl("private:factory/scalc","_blank",0,dimArray()) secondDoc.getSheets().insertNewByName("Price",0) selectSheetByName(secondDoc, "Price") dispatchURL(secondDoc,".uno:Paste") thisComponent.getSheets.removeByName("Price") ' save secondDoc.storeAsUrl("file:///.../price" & Str(secondDoc.getSheets.getByName("Price").getCellByPosition(5,3).Value) & ".ods",Array()) secondDoc.close(true)
^^^ first line was wrong: selectSheetByName(thisComponent, "Price")
Do you mean it's ok now ? Is it a macro you created or out of box ? Did you give a try to 3.5.5 ?
(In reply to comment #6) > Do you mean it's ok now ? > Is it a macro you created or out of box ? > Did you give a try to 3.5.5 ? I'm a programmer. It's very hard to trying version 3.5.5. I have an OS Linux OpenSUSE. Which currently have a version 3.4.5.
(In reply to comment #7) > (In reply to comment #6) > > Do you mean it's ok now ? > > Is it a macro you created or out of box ? > > Did you give a try to 3.5.5 ? > > I'm a programmer. Do you mean you created this macro ? > It's very hard to trying version 3.5.5. You can download the rpm from here: http://www.libreoffice.org/download/?nodetect > I have an OS Linux OpenSUSE. Which currently have a version 3.4.5. See my previous comment. If it's a bug with 3.4.5, 3.4.6 exists but there won't be any new 3.4.X version. That's why I ask you to give a try to 3.5.5 If you're a programmer, you may be interested in building from sources, see http://wiki.documentfoundation.org/Development/Native_Build
While trying to use new version 3.5.5 I get more complex trouble. Impossible to use. https://www.libreoffice.org/bugzilla/show_bug.cgi?id=52338
Dear Bug Submitter, 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
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