An Impress slide may contain a custom-shape (e.g. rectangle, circle, etc.) or a control (e.g. PushButton, Image Control, etc.) Using the Interaction feature of Impress, it is possible to make a mouse click on one of these objects on a slide perform a function, like, run macro. This initially works fine for both the custom-shapes and the controls at the slide design phase. When the Impress slide show is saved the interactions with the custom-shapes are stored in the .odp archive of content.xml as a section called <office:event-listeners>. For example, a rectangle shape that can be clicked on to run a macro would be saved in content.xml as follows: <draw:custom-shape draw:style-name="gr10" draw:text-style-name="P7" draw:layer="layout" svg:width="2cm" svg:height="1cm" svg:x="17.5cm" svg:y="19.5cm"> −<office:event-listeners> <script:event-listener script:language="ooo:script" script:event-name="dom:click" xlink:href="vnd.sun.star.script:Standard.Module1.ClickOnObject?language=Basic&location=document"/> </office:event-listeners> <text:p/> <draw:enhanced-geometry svg:viewBox="0 0 21600 21600" draw:type="rectangle" draw:enhanced-path="M 0 0 L 21600 0 21600 21600 0 21600 0 0 Z N"/> </draw:custom-shape> The problem is that when a control has been assigned to perform an interaction, this <office:event-listeners> information is not being saved in the content.xml file. For example, a PushButton control is currently being saved in content.xml as follows: <draw:control draw:style-name="gr1" draw:text-style-name="P2" draw:layer="controls" svg:width="5.5cm" svg:height="1.5cm" svg:x="1cm" svg:y="1.5cm" draw:control="control1"/> In the above the PushButton control no longer has any event-listeners information, thus when this Impress.odp file is next opened, the PushButton will not have the Interaction functionality it originally had during the slide design phase. To simulate this problem: Create a new Impress presentation with one blank slide. Add a Rectangle shape and a PushButton control. Create a BASIC subroutine in Module1.bas with the instruction: msgbox "Object was clicked". For both the Rectangle and the PushButton click on Interaction icon and select run macro to execute this subroutine. Start the slide show. You will be able to click on either the Rectangle or the PushButton and the message window will open with the message "Object was clicked". Now save the Impress presentation to disk as a .odp file. Close LibreOffice. Find the file you've saved, and double click on it to launch Impress. Start the slide show. You will find that the Rectangle will still run the subroutine and display the message window, but the PushButton control no longer performed this interaction.
Reproduced on LibO 3.3. beta3 SLED 11 sp1 . A sample attached, the push button is not interactive in slide show. Hi irs, Did you notice this ever worked in previous OO.o build? If it is a regression problem, please feel free to promote the priority. Otherwise, I think it is more like an enhancement feature. Thanks!
Created attachment 40733 [details] test data
(In reply to comment #2) > Created an attachment (id=40733) [details] > test data Hi Yifan. The versions of Impress that I have tried are OpenOffice V3.2 and LibreOfficeV3.3-beta and neither of them save the interactions capability when they have been assigned to a form control like a button, but they do save the interactions capability when saved to a drawing object. I don't have enough experience with previous versions to know if this feature used to work or not. The reason I assumed that it should work is based on the openoffice online Impress User Guide. Please see this web-page on Interactions... http://wiki.services.openoffice.org/wiki/Documentation/OOo3_User_Guides/Impress_Guide/Using_interactions It states... Interactions are things that happen when you click on an object in a slide. They are typically used with buttons or images, but text objects can also have interactions. ...this suggests to me that the interactions will work OK with buttons (which they do the first time you set them up to run a macro and then run the slide show). It seem to me that these interaction characteristics should then be preserved during a save of the Impress slide show, such that they then work the next time the slide show file is launched. Perhaps there is someone with older versions of OpenOffice that can confirm if this used to work and if the problems I'm observing is a regression in the functionality in these latest releases. Regards, irs
This is a Impress bug, therefore changed Component accordingly. Added version according to Summary.
Freeing this bug - can't currently commit time to this, unfortunately.
Created attachment 76896 [details] Impress Example with BASIC macro to correct missing parameters With regard to interactions, the two properties for Form Controls that do not get saved to the Impress.odp file are "OnClick" and "Bookmark". As a workaround a subroutine can be launched upon loading the file and it will restore these two parameters. The attached file is a one slide Impress presentation that contains a BASIC macros to restore the onClick and Bookmark parameters for two Form Controls, "push button" and "image control". As the file is loaded it executes a subroutine to correctly set the OnClick and and Bookmark parameters. See Module1 for more information and to read the BASIC code. Additional Note: I also found that for Push Button Form Controls the font size does not seem to get saved. Upon reloading a file it will come up with the default font size label on the push button. The macro in the attached example file also corrects the font size on each file load. This font size issue is a seperate bug. Regards, Ian.
Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
Hi, I have tested for the problem scenario using Libre Office version: 4.2.6.3 Build ID: 420m0(Build:3) The test was on Ubuntu 14.04 Linux Operating System version: 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The problem I intially reported on 2010-10-31 16:34:47 UTC is still present. Regards, Ian.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Hello, I confirm the non-functioning of the interactions (go to the page or the object) put on the cliparts of the gallery. Interactions are lost when the slideshow is saved. These interactions work on shapes and images. Does not work on Libo 5.0.6.3, Libo 5.1.6.2, Libo 5.2.5 Works on AOO 4.1.3 See you soon
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This problem now seems to be resolved as it works for me with the following Libreoffice: Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.2 CPU threads: 2; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-NZ (en_NZ.UTF-8); Calc: group Thanks and regards, irs.