Thank you, Jeff, for another wonderfully helpful video! I’m currently on a deep-dive into building my animation skills, using gsap. You’re really helping me with that. Massively appreciated! All the best (from Manchester UK) 🙂
Great video! I also noticed this problem a while back when trying to use GSAP from my own code and found this same solution a few days ago. I have a slightly different implementation that you might find helpful. Check out the gist linked below. The central part of it is a function that calculates and returns the scale factor. You can then say, xValue * scaleFactor, store it in a variable and pass it to GSAP instead of first subtracting the object dimensions from the slide dimensions. Ok, so TH-cam didn't like that I had a link in the comment. Hopefully, the above explains it well enough
This is fantastic! And I learned sooo much! Unfortunately, this doesn't work if you are trying to move an object from a scrollable area to outside of the scrolling area. For example, I have a drag and drop interaction where the targets are inside the scrollable area (because I need more vertical space). When I use your code it moves it somewhere inside the scrolling area. You don't by any chance know how to resolve this do you?
Yeah have not tried it in a scrollable area. It does add another level of complexity to it. I can add it to my backlog and try to explore when I get a chance.
Thank you, Jeff! Is there anything we should consider when it comes to targeting an object with the data-model-id? Is there anything that would make it change and make our JS useless?
One example just came into my mind. You can target multiple objects throughout the course if the code is used on the slide master and you give the same accessibility text to all the targeted objects. You cannot really do that with a unique data model id.
When you publish the file that is that, nothing will break with the code so you should be fine but when you republish with a new version there may be a chance it breaks if Articulate updates or changes there code so that may happen with republished files but I have not come across that yet myself.
Accessibility text yeah could happen but the data-model-id is generated unique for every object so you should not run into duplication like you can with the accessibility text so I think it is a safer way to go for now.
HI @Learning Dojo, thanks for the video. I remember asking you if it's possible to have a global function so you don't have to keep copy/pasting code. I have figured out a way to do it! So now each button calls the same funciton and only needs to pass the (xCoord, yCoord). This will make it easier to maintain the code and hopefully opens up new possibilities for you. Also, because I am new to StoryLine I don't know if my solution is breaking the "rules", but it works. Because of this I don't want to paste it on here in case people start using my solution which StoryLine might not allow in a future update. I can't see why this would happen but I don't know how strict StoryLine is with manipulating javascript in their trigger console. is there a better place to contact you and show you how I did it?
Thank you, Jeff, for another wonderfully helpful video! I’m currently on a deep-dive into building my animation skills, using gsap. You’re really helping me with that. Massively appreciated! All the best (from Manchester UK) 🙂
Oh awesome! Glad to hear that. Curious to see what you build with GSAP.
Great video! I also noticed this problem a while back when trying to use GSAP from my own code and found this same solution a few days ago. I have a slightly different implementation that you might find helpful. Check out the gist linked below. The central part of it is a function that calculates and returns the scale factor. You can then say, xValue * scaleFactor, store it in a variable and pass it to GSAP instead of first subtracting the object dimensions from the slide dimensions.
Ok, so TH-cam didn't like that I had a link in the comment. Hopefully, the above explains it well enough
Hmm interesting. Email me the link jeff@learningdojo.ninja. Curious to see that.
@@LearningDojo Mail sent.
This is fantastic! And I learned sooo much! Unfortunately, this doesn't work if you are trying to move an object from a scrollable area to outside of the scrolling area. For example, I have a drag and drop interaction where the targets are inside the scrollable area (because I need more vertical space). When I use your code it moves it somewhere inside the scrolling area. You don't by any chance know how to resolve this do you?
Yeah have not tried it in a scrollable area. It does add another level of complexity to it. I can add it to my backlog and try to explore when I get a chance.
Thank you, Jeff! Is there anything we should consider when it comes to targeting an object with the data-model-id? Is there anything that would make it change and make our JS useless?
One example just came into my mind. You can target multiple objects throughout the course if the code is used on the slide master and you give the same accessibility text to all the targeted objects. You cannot really do that with a unique data model id.
When you publish the file that is that, nothing will break with the code so you should be fine but when you republish with a new version there may be a chance it breaks if Articulate updates or changes there code so that may happen with republished files but I have not come across that yet myself.
Accessibility text yeah could happen but the data-model-id is generated unique for every object so you should not run into duplication like you can with the accessibility text so I think it is a safer way to go for now.
HI @Learning Dojo, thanks for the video.
I remember asking you if it's possible to have a global function so you don't have to keep copy/pasting code.
I have figured out a way to do it!
So now each button calls the same funciton and only needs to pass the (xCoord, yCoord).
This will make it easier to maintain the code and hopefully opens up new possibilities for you.
Also, because I am new to StoryLine I don't know if my solution is breaking the "rules", but it works.
Because of this I don't want to paste it on here in case people start using my solution which StoryLine might not allow in a future update.
I can't see why this would happen but I don't know how strict StoryLine is with manipulating javascript in their trigger console.
is there a better place to contact you and show you how I did it?
Yeah very curious how you did it. Email me jeff@learningdojo.ninja.
@LearningDojo hey Jeff, I sent you an email with my solution. Hopefully, you received it.
@LearningDojo hey I sent you an email with my solution. Have you received it?
@@LearningDojo Hey I sent you an email with my solution. Did you receive it?
@@LearningDojo why are my replies getting deleted lol?