This is my weekly "I'll keep this thread alive even if I have to do it all by myself"-post.
Post no.: 13.
I skipped a week again - christmas stress caught up with me... But instead of counting the weeks since I started (15), I'll only count the posts I made for this (13). It's my present for Articulate.
The frustration for me is a total lack of communication by developers on this subject. I mean, people have literally been asking for this feature for YEARS. Have we ever heard one peep from anyone saying "hey this just isn't possible and here's why" or "we are working on it" or even "it's never going to happen"?
I'm happy to add another voice to the chorus of people asking for this feature. It's hard to believe it hasn't already been implemented after all this time.
Keep going Ina! This simple functionaiity was first requested back in 2013. (here ... by others, including me). For the past 6 years I have assumed that it must be so complicated for Articulate to implement that it was never a seriously considered addition.
Ken - I agree with you - never once over all these years has the SL staff team attempted to explain WHY it hasn't been implemented, simply offering their empty appreciation for us 'reaching out' (that expression - aaaaargh!)
We don't have the SL3 code so who knows what would be involved in adding this functionality or what monstrous complications allowing seeking to anywhere on the timeline would create.
Maybe the problem is that if the program was to leap from 3 seconds to 48 seconds in, it would have to 'build' all the objects incrementally to get there? So please just tell us Articulate.
But common sense suggests that, since we already have playhead 'CUE POINTS', each must have an identity (ie: a name and a location on the timeline) with that data held in variables in the program. This must be true since we can use a Trigger to perform an action when a specific CUE POINT has been reached.
So why is it so difficult to move the playhead directly to a named CUE POINT?
PS: This request was on my (I thought) quite reasonable list of 'missing feature' presents to Father Christmas here.
87 Replies
I thought it odd I beat you to it last week Ina
Getting a headstart thanks to CET :)
+1! No one find a workaround?
I have video slides with "resume saved state" and i want to restart slide with a button/action/js/anything else, can't get out of this :c
This is my weekly "I'll keep this thread alive even if I have to do it all by myself"-post.
Post no.: 6.
Happy hump day all!!! (Mike Mike Mike!!) :)
This is my weekly "I'll keep this thread alive even if I have to do it all by myself"-post.
Post no.: 7.
Need.... more coffee.....
This is my weekly "I'll keep this thread alive even if I have to do it all by myself"-post.
Post no.: 8.
*yawn* *stretch.....*
Good morning jump to cuepoint thread (:
This is my weekly "I'll keep this thread alive even if I have to do it all by myself"-post.
Post no.: 9.
This is my weekly "I'll keep this thread alive even if I have to do it all by myself"-post.
Post no.: 10.
We've just hit 10 weeks, guys. I just hope Brian has enough memes to last the next ten weeks!
This post was removed by the author
Any Spongebob fans in here? (:
This is my weekly "I'll keep this thread alive even if I have to do it all by myself"-post.
Post no.: 11.
I was on vacation last week, so I missed a week...
lots of yawning and stretching this morning... need coffee (good morning all)
This is my weekly "I'll keep this thread alive even if I have to do it all by myself"-post.
Post no.: 12.
Now I'm off building christmas quizzes. Finally some fun!
Why is this such a difficult ask?
You going to share one of your fun Christmas quizzes here??
This is my weekly "I'll keep this thread alive even if I have to do it all by myself"-post.
Post no.: 13.
I skipped a week again - christmas stress caught up with me...
But instead of counting the weeks since I started (15), I'll only count the posts I made for this (13). It's my present for Articulate.
The frustration for me is a total lack of communication by developers on this subject. I mean, people have literally been asking for this feature for YEARS. Have we ever heard one peep from anyone saying "hey this just isn't possible and here's why" or "we are working on it" or even "it's never going to happen"?
It just feels like disrespect at this point.
I'm happy to add another voice to the chorus of people asking for this feature. It's hard to believe it hasn't already been implemented after all this time.
Edit: Keep it up Ina!
Keep going Ina! This simple functionaiity was first requested back in 2013. (here ... by others, including me). For the past 6 years I have assumed that it must be so complicated for Articulate to implement that it was never a seriously considered addition.
Ken - I agree with you - never once over all these years has the SL staff team attempted to explain WHY it hasn't been implemented, simply offering their empty appreciation for us 'reaching out' (that expression - aaaaargh!)
We don't have the SL3 code so who knows what would be involved in adding this functionality or what monstrous complications allowing seeking to anywhere on the timeline would create.
Maybe the problem is that if the program was to leap from 3 seconds to 48 seconds in, it would have to 'build' all the objects incrementally to get there? So please just tell us Articulate.
But common sense suggests that, since we already have playhead 'CUE POINTS', each must have an identity (ie: a name and a location on the timeline) with that data held in variables in the program. This must be true since we can use a Trigger to perform an action when a specific CUE POINT has been reached.
So why is it so difficult to move the playhead directly to a named CUE POINT?
PS: This request was on my (I thought) quite reasonable list of 'missing feature' presents to Father Christmas here.
Happy Christmas,
Tim
This discussion is closed. You can start a new discussion or contact Articulate Support.