Proper animation effects often need a non-zero duration: Swivel, wipe, fade etc. But emphasis animation types are, as often as not, chose for instantaneous application, e.g. font weight, family or color change. This is currently almost-achievable, by setting the duration to 0.01 seconds. But it should be possible to just make them instantaneous, period. A checkbox or a button would do nicely - possibly to the right of the duration box with a tooltip explaining it's for isntantaneity (sp?)
What is a zero duration animation? Would be a none-animation to my understanding.
(In reply to Heiko Tietze from comment #1) I mean, like "Appear" has no duration. These are effects in which the final state is meaningful, even without the transition. This is relevant for effects such as font color/family/weight change, for example. It's meaningful to watch the color change, but it's also meaningful to just have it different then before, for the rest of the slide display time.
[Automated Action] NeedInfo-To-Unconfirmed
Using 0.01s for Color Blend, for example, appears to be quite immediately to me. My take => WF (not needed and dangerous since zero might have side-effects)
(In reply to Heiko Tietze from comment #4) > Using 0.01s for Color Blend, for example, appears to be quite immediately to > me. > > My take => WF (not needed and dangerous since zero might have side-effects) Come on, Heiko, you know that's not fair. Your position is not much different then rejecting an "Appear" effect, by telling people to use 0.01s Fade-In instead, since it "seems quite immediate" (which it does), and a duration-0 Fade-In is dangerous.
Zero is very much different than numbers in IT. Think about multiplication/division.
(In reply to Heiko Tietze from comment #6) > Zero is very much different than numbers in IT. Think about > multiplication/division. Heiko, of course when you allow something to be zero, you have to make sure you're not dividing by it (multiplication is generally ok). But we have a zero value for delay. And we have other zero-duration effects. So what you've described is a chore for the person introducing the change. That is at most a reason to reduce implementation priority, not a counter-argument against feature usefulness. Plus, again - there could be a toggle for have/don't have duration.
Okay, let's leave this implementation detail to the developers. Whether the minimum is 0.01 or 0 shouldn't affect UX - and seems to be desirable.