Scene producing unexpected behaviour

(Hrishikesh Kokate) #1

The scene is producing really unexpected behaviours and I can’t figure it out, why.

I’m creating this scene for a project. I have created a scene with an image on which there’s a button (Click here) that starts the app. The app basically has a text input field that is supposed to read what kind of symptoms the user is facing and then give a reply. It is doing so using JavaScript. I have added certain keywords (the keywords are: headache, stomach, joint, tooth, insomnia) which are checked for and then the user is taken to a specific time in timeline which shows that reply.

Now, the problem is, I can’t seem to be able to get rid of the ‘Help me’ button and the form when it’s not needed (it’s not needed when users are getting the reply). The Hype timeline shows no error, but, it’s not working fine in preview.

Can someone please help?

Oral-B (397.3 KB)

(Kalle) #2

It seems as if it needs a ‘display’-keyframe at exact that time where you send the ‘Options’ Timeline to (1s for ‘headache’, 2s for ‘stomache’ etc.). Each for the form an for the button. But I would prefer to set the display/visibility via JS - you will have more control… (442.1 KB)

(Kalle) #3

Here is a JavaScript version. Gave your button and the form IDs (‘helpBut’ and ‘form’):

var myBut = hypeDocument.getElementById('helpBut'); = 'none';
var myForm = hypeDocument.getElementById('form'); = 'none';

sets your button and the form invisible in the ‘check1200’ function. There´s a new function 'changeView" which sets both to visible again by clicking the ‘Help me!’ Button or the ‘Got another sympton’ button:

var myBut = hypeDocument.getElementById('helpBut'); = 'block';
var myForm = hypeDocument.getElementById('form'); = 'block';
hypeDocument.goToTimeInTimelineNamed(0, 'Image'); (421.8 KB)

(Hrishikesh Kokate) #4

Thanks a lot, sir! This works great. But, why does it need another keyframe to stay hidden? Like, I don’t understand that, especially because Hype’s timeline shows the correct preview but it produces unexpected results only in browser (in my file). Why should this happen?

(Hans-Gerd Claßen) #5

no answer to your question here, but a scene- or symbolbased-approach should be easier to handle …

(Kalle) #6

No idea… Timelines are great, but they contain certain pitfalls - especially if you use them in context with display/not display - in my experience. Timelines may affect other timelines… in this case I suspect the keyframe in the ‘image’-timeline interfering with the ‘options’-timeline. Therefore I would always prefer the JS approach - or - to make things much easier, as Hans-Gerd points out - in this case it’s likely better to use scenes.

(Jonathan Deutsch) #7

The most basic reason is that the runtime plays timelines as streams of animations, where an animation is defined as the change between a start and end keyframe. If there is only one keyframe it isn’t really an animation and won’t get played.

That said I do consider this to not be desired behavior – the display property is pretty special relative to other properties, so we’d like to improve this so it works as you expected!

(Hrishikesh Kokate) #8

That’s some new information. Thanks a lot!