-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while splitting #3
Comments
Hi @Taeir and thank you very much for your positive feedback. Concerning the issue you are experiencing, I have made a couple of tests with two PowerPoint installations:
In both cases I am able to successfully split the single slide, as showcased in the following short capture: Please make sure that no applications are interfering with the clipboard while you are splitting. As indicated in the usage instructions as well as in the README, this could easily cause the add-in to fail. Concerning the option to suppress errors, it is something that I have never considered so far (this is also the reason for the discouraged advice in the error dialog box): indeed, errors cause a deviation in normal code execution which could result in further inconsistencies being generated in the following slides even if their contents are perfectly safe. It is like generating errors on top of errors. Therefore, while I am still giving users the option to forcedly continue after an error, I do not think it would be a good idea to do it transparently because it could break the final result. Feel free to reopen the issue in case your questions are still not addressed. |
I can confirm that the same error occurs on my installation using Microsoft 365, with PowerPoint at release 16.0.12827.20328 (64-Bit) with PPspliT 1.21 on Win10 (installed in a VirtualBox). In my case, such error always appears if PPspliT detects an "empty slide", for example because the first element of a slide does not appear automatically but after a click. See this example: PPspliT_Error.pptx |
There is a small difference in the minor number of the PowerPoint release I am using, but I doubt this is really relevant. In addition, I am using the 32-bit version of Microsoft 365 but, again, usage of the add-in should not be impaired on the 64-bit version. Instead, as indicated in the usage instructions, I am more inclined to thinking that VirtualBox is interfering with clipboard usage: this may indeed happen because of the guest additions. In some cases I have been observing unexpected behaviors while VirtualBox was running, even when PowerPoint was executed on the host. My advice:
Finally, I am not seeing any issues while attempting to split your sample presentation. Starting with an empty slide is a very common and covered condition. |
Thanks a lot for your help! You're right. I was a problem with VirtualBox's shared clipboard. After disabling it, PPspliT worked like a charm. Once again, thanks a lot for your great work! |
First of all, thank you for writing this plugin. I think it is very helpful and should be supported by PowerPoint natively.
When using your tool on the slides of a course I am teaching, I constantly keep getting a fatal error:
I have reduced the problem to a single slide, which a simple slide with text boxes, pictures and rectangles. Is any of those not supported by your plugin?
Cannot split.pptx
Note that if I let PPspliT continue, the resulting slides are correct and as I would expect (at least, I don't notice any problems).
In case shapes like rectangles are not (fully) supported, I would like to ask if it would be possible to add some kind of checkbox to "continue despite any errors" (for future errors as well). For my purposes, the split slides are perfectly fine. However, clicking on "continue" after every error is quite time consuming for a slide deck of 70 slides with many animations on each of them. I do see the error handling delays the slide processing a lot, but as long as it can be done automatic, that would be good enough.
Versions
PPspliT 1.21
PowerPoint from office 365 (Powerpoint 16)
The text was updated successfully, but these errors were encountered: