Increase time delay trigger maximum to 60s
Instead of having a fixed set of delayed times for a time trigger allow a designer to enter any time value in seconds.
The maximum trigger time of 1 second is not sufficient and as the feature currently exists it is unnecessarily limited.
If a maximum time must me added (I'm not sure that it does) it could be 60 seconds for more flexibility.
Christopher
shared this idea
I’ve updated the title to reflect your request. Please note that the current maximum is actually 5s, and you can type the number directly into the interaction popup.
20 comments
-
Ian
commented
It's September 26th, 2021 and this SIMPLE feature still hasn't been implemented yet. This is why everyone is ditching Adobe products.
-
Joshua
commented
Still this is an arbitrary number. A simple progress bar shouldn't be this hard to handle. Or better yet, allow timing animation on a component.
-
Ant
commented
Made an account just to vote on this
-
Anonymous
commented
I agree! Especially when prototyping with a loading bar that is going to take, say, 20s, it's super frustrating to have to use multiple artboards or have an absurdly short progress animation.
-
Whit Gurley
commented
Bump. This is beyond ridiculous, you're arbitrarily deciding on an absurdly short limit when you can't know what your customers are trying to do. As with a number of XD requests, you have dozens or hundreds of people complaining about something that's incredibly easy to fix (could this possibly be more than just an integer in the software?), yet it lingers for years. 🤦🏻♂️
-
Anonymous
commented
Absolutely agree. I don't even get why this has been limited. So annoying...
-
Anonymous
commented
This would be really useful! Please allow this in the next update.
-
Matt Braun
commented
agree. The max time of only 5sec is not enough for so many things
-
KT
commented
the purpose of Auto-animation and delay time is because we would like the user to read all the critical information on the screen before going to the next screen. Please make the delay time more flexible for your user.
-
Anonymous
commented
seems like an easy enough fix to me. I would prefer nog time cap. If minutes could be added that would be great
-
Anonymous
commented
Seconding this. The 5 seconds limit is very restrictive and somewhat arbitrary.
-
Simon Dybeck
commented
This is a simple, simple change for Adobe. Why shoudnt' we be able to have more seconds, minutes, hours..?
For example we want to make a presentation that uses auto-animations and therefore we would like some pages to show up for a few minutes -
Edu Couchez
commented
Yeah! 5 seconds... but my customer needs exactly 10 seconds (even another simple micro-interactions that XD is incapable to replicate) Time to look for a new app to achieve it :-(
-
Amanda Kozak
commented
Agreed. This is a big blocker for me right now.
-
Luka Rukonić
commented
I really see no reason to limit the transition time to 5s (what data or reasoning supports this decision?). In my case, I would need to have a 10s delay, please make sure you increase this in the next release or allow us to enter any arbitrary value.
-
Simon
commented
We currently have only the option to go up to a maximum of 1s regardless of how much we free type in. We really need to see prototypes with more time delays before transitions.
-
Theo Nordahl
commented
I agree.
-
Dan
commented
I'd like to have 10 s time delay
-
Paul Seymour
commented
OMG please please please, I can't stand arbitrary limitations. I've created a self running demo of timed sequences, and this 5s limit drove me nuts, but just lived with it. But, now that I'm timing stuff out in After Effects, it's even worse - I have to now time-remap all kids of stuff and it's now a mess..
Make it longer, PLEASE! I see no reason to just limit it to 5s. Sure, the pop-up values make sense, but limiting the manual entry, and forcing it to 5s, no.
-
Christopher
commented
Ah, okay. I was trying to type in 6s and it kept changing it back to whatever I had selected from the predefined options. * After just trying it out, I think my issue was I was typing in "6s" rather than just "6". In either case I think a longer more flexible time would be beneficial.