Solved

Interactive Hotspots - dragging into a Drop Spot

Hi there,

I am building an interactive scene where I'm using the interactive drop spot functionality.


For Context:

I have set up a list of Hotspot buttons, arranged in a random order and all are interactive drag items.

User has to drag the Hotspot buttons to a correct sequence (1 to 6) on the right hand side, where I've placed 6 x Single Drop Spots, such that only 1 of the buttons from the left hand side correctly drops into the Drop spot. (For example, button 3 drops correctly into the 3rd Drop Spot. But if button 3 drops into any other Drop Spot, it's incorrect, and resets).

I've published the scene and it works well on web (ie. browser).

However, when I use the same HTML export for Pico app, the Dragged Items (buttons) do not get dropped into the Drop Spots correctly, and are dropped significantly away from the Drop Spot position (up the Y axis). The logic still works fine (ie. button 3 drops correctly into the 3rd Drop Spot).

Finally, the reset function(where the Drag item is incorrectly placed, and resets to original position) does not work on the Pico either, but works fine on the browser.


Therefore, can someone please help me with whether there's existing bugs in the Pico app such that it does not recognise the Drag Spot (or it moves around), and how the logic gets treated, vs the browser? I need it to work for the Pico, as that's the preferred deployment method.


I can also share the URL of the scenario for testing.


Thanks in advance.


Solution

First of all, thanks for the great description of the issue. Made it easy to see what you were working towards, and to create a way to reproduce the issue. For the reset function, I was able to reproduce the problem in the Pico App when I used the "Contains" condition on the drop spot to check if the wrong drag item was being dropped. However, I was able to get it working by using the "Is Drop Target" condition on the drag item like this:



I'm not able to reproduce the issue where the drag item is shifted up when dropped, for me it seems to work fine. Is there any additional information you can provide for that?


We will definitely get the contains fixed, but for now, there is a workaround.



Discussion (2)

First of all, thanks for the great description of the issue. Made it easy to see what you were working towards, and to create a way to reproduce the issue. For the reset function, I was able to reproduce the problem in the Pico App when I used the "Contains" condition on the drop spot to check if the wrong drag item was being dropped. However, I was able to get it working by using the "Is Drop Target" condition on the drag item like this:



I'm not able to reproduce the issue where the drag item is shifted up when dropped, for me it seems to work fine. Is there any additional information you can provide for that?


We will definitely get the contains fixed, but for now, there is a workaround.



Thanks @johnb, this solution worked for the reset issue. For the issue where the drag item is shifted up when dropped, I went for a work-around where rather than show the dropped item (which shifted up), I hid the dropped item and showed another item instead - thereby forcing it to display correctly. Thanks for your prompt reply!