Forum Discussion
Drag & Drop issue snap tile (SL 360)
Hello,
I can't have a fine display with the Tile snape dropped option because the size of the dragged item is refering to the Normal State size and not the Drop Correct State. Is it a known issue? Do we have a quick fix to apply?
Please open the review link to understand quickly my problem...
https://360.articulate.com/review/content/fbfea92d-cc4b-4e1c-ba0e-55ffaf10b73b/review
And find the .story attached.
Best regards,
19 Replies
Thanks for making those distinctions, Joyce. I will write a feature request to make drag-and-drop state changes a bit easier to work with. You'll get a confirmation email once I share it with my team!
- JoshuaZettelCommunity Member
I second this. I am creating a large card sort of 45 cards. I am sorting them into 4 piles but the tile spacing is ruining the professionalism of the project. The free form looks very sloppy.
Here is an overview of my goal:
I want them to be large and visible to start. When they are dropped on a pile I wish I could change the image to text and make it's tile stacking size shrink to the size of the text. This will allow students to see the cards in large at first, and then once they place them in a pile, they will all be visible (in text form) and capable of being selected in it's smaller state for further resorting into other piles. This will allow students to see an overview of all the cards they have placed in one box even if there are 30 of them in one pile. User access to the drag and drop items after placing them is crucial for reflection in my case.Troubleshooting efforts:
I tried to make the normal state the smaller text, start the slide in a custom state (large card image), and have the state switch to the smaller, normal text when it is dropped but unfortunately it still maintains the larger card image size when being sorted in tile format. Any solutions? - RenGomezStaff
Hi Joshua,
Thanks for reaching out and sharing the details of what you're trying to accomplish! The best way we can provide help would be to take a look at the interaction in your .story file. I've gone ahead and created a case on your behalf.
Using this personal link to your case, if you can share the file, one of our support engineers will take a look and get back to you!
- JoshuaZettelCommunity Member
Thank you for your response, I have uploaded my storyline to the link. I was able to find a work around by creating individual drop boxes which are large in size, but overlap so that all you can see is the smaller image when it changes state. This was a huge headache and could have been prevented with a tiling function that also changes the size format, when the state changes.
- HantaRamarinjanCommunity Member
Has this issue been resolved? I am now working with drag items that do not pile well on the drop section, too much space in between the items.
- JoyceMaurin-e58Community Member
Hello Hanta,
Not that I'm aware of.
My ordinary workaround is to have a smaller drop area inside the visible drop area.
- ShannonLoweCommunity Member
So I guess, four years later, that this still has not been addressed.
So I have a new complication with this one. Hopefully I can explain it properly. I would like, as would the people above, to be able to drag an item and have it change state, including the size reserved for it in the drop area, but it still saves the space of the normal state. I don't want to use free, my client wants things orderly.
So I took the advice above and made the normal state the size I want and the hover state to show the whole item. But when centered in the box where these items appear, once I create the hover state, even though the normal and hover states are centered in the box where they will appear, when previewed the normal state appears at the top of the box and the hover state is centered on that.
I have only set up the first of the drop objects this way, but it should illustrate the problem.
Can I suggest that you stop adding new features until you have fixed the bugs that have been around for years?
Hello Shannon,
Happy to chime in. I tested your project file using older versions of Storyline 360 and I can confirm that the behavior is similar. In my test, the 'Hover' state of an object, which covers more area than its 'Normal' state, appears to cover other objects that are tiled next to it rather than "pushing them out of the way".
I understand that having the slide recognize the space occupied by the 'Hover' state is better visually so I raised this behavior as a possible bug with our product team. This community post is included in the bug report so we can notify you as soon as any new updates are shared. Thanks again for bringing this to our attention!
Related Content
- 3 months ago
- 8 months ago
- 2 years ago