Forum Discussion
Drag and Drop: Move drop object behind another item.
I'm creating a drag and drop interaction where the user drops an item into a trash can. The item is dropped onto a hotspot and then using motion path drops down behind the trash can image.
Currently I have the drop object and hotspot set up behind (further down the timeline) the trash can.
I've got the motion path working but the drop item keeps moving in front of the trash can instead of behind it. Any suggestions why this might be?
26 Replies
Hi Anna,
This is still an open issue as we prioritize other issues and features. I'm going to add your voice to the report. If there's any news regarding this bug, this conversation will be updated.
Thanks for letting us know about this!
I do have a sample on the forum somewhere that shows a card flip. If im not mistaken that one also has zIndex change in it.
Although this is a simple sample where a click brings an element to a higher z-index and thus shows upfront... this concept can be used in Drag and Drop scenarios too.
https://360.articulate.com/review/content/1a7a1a7e-3562-431a-9d0f-f08d477f0674/review
These lines of Javascript code do the trick...let card = document.querySelector("[data-acc-text='c_sp10@3x.png']");gsap.set(card, {css:{zIndex:100}})
Where you ofcourse need to take care that the zIndex given to a higher element...indeed is higher then the highest one on your stage. In this case there were 55 layers...so i could suffice with 56.Thank you! I will try it :)
Any news on this problem since 2020? It's 2024 now but I am facing the same issue.
Hi Anastasia!
I'm sorry to hear you've also been affected by this issue!
I don't have any updates to share at this time as our development team prioritizes other fixes. Not to worry! I've included you in the bug report and will update this discussion as soon as we have news to share.
In the meantime, for your reference, here's a deeper look at how we tackle bugs.
It's been 7 years. Is there any update to fixing this issue?
I have an open ticket that's over 5 years old on another issue, and it's status has changed a dozen times now, but it's never been resolved or addressed.
Not to dog on Articulate, I have respect for you all, and I can only imagine the workload and complexity, but having an open and unresolved bug for almost a decade doesn't convey a focus on the user or customer. Especially when Storyline keeps pumping in pay-to-play features like AI, advanced text-to-speech, and a contextual menu. A bug fix should've taken a fraction of the time it would to develop any of those into the program, and should take priority. Why paint a house if you're not going to address the caving structure?
All of these new features Articulate keeps adding, while nice, are in less demand than the fixes their users have been asking to be addressed for years.
I would like to add my voice to the request for an option to have drag objects drop BEHIND the target object. Thanks.
I am also adding my voice to this issue.
Isn't it a pretty poor response to customer requests that this issue hasn't been resolved since being raised in 2017!!
Yet, I seem to remember being able to achieve this with layers on a previous project...
Actually layers have the same issues with depth. Offcourse you can 'trick' the viewer in thinking something is behind or on top of something by showing a layer with content. But thats just make believe.
