Currently, the only control enabled is the 'add' button. If I want to have a different effect, I currently need to:
* assign whatever was last selected
* edit the effect afterwards
* if I want to add effects to multiple shapes, or add text effects (which implicitely break up my shape into sub-animations), I need to dummy-assign that to another shape to change the default, then delete that animation, then assign to the real target shape
This is all pretty bad UX.
User Profile Reset: No
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
If you want to _change_ an effect it wouldn't be only the add button that is available. Changing the effect is just a click away.
> If you want to _change_ an effect it wouldn't be only the add button that is
> available. Changing the effect is just a click away.
This comment makes absolutely no sense
(In reply to Katarina Behrens (CIB) from comment #2)
> > If you want to _change_ an effect it wouldn't be only the add button that is
> > available. Changing the effect is just a click away.
> This comment makes absolutely no sense
Or the original request :-).
What I mean is that you cannot "have a different effect" when none is added before. If an effect has been added all controls are accessible, if the list is empty the user have to add one.
(In reply to Heiko Tietze from comment #3)
> What I mean is that you cannot "have a different effect" when none is added
> before. If an effect has been added all controls are accessible, if the list
> is empty the user have to add one.
Clarification & example - I want to assign 'motion path, five-point star'. There's two ways currently to do that:
* add 'entrance, appear', then change the already-assigned effect to the one I really wanted
* do the dance from above to an unrelated shape, then delete that effect, then use the new default to assign 'motion path, five-point star' to my _actual_ shape
Before, with enabled extra controls, I could do all those tweaks _before_ assigning an effect. Note that assigning effects can _already_ trigger actions, like splitting an outline text into sub-effects. So changing effect type before or after is _not_ identical in all cases.
Got it. Use case is to a) avoid preview animation while multi-step configuration (but have it when finished) and b) to get exactly the same animation without digging into the plethora of options.
But I still hesitate with 'configure object properties without an actual object'. Two ideas come in mind: store settings made, meaning you don't start with entrance > appear but motion > stars. And the other is to copy the animation with all its properties and allow to paste it to an object. Could be a context menu on the animations list.
The idea in comment 5 got support, removing UX.
Dear Thorsten Behrens (CIB),
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!
Still present in master (to-be 6.4)