# Audio stopped event in the drag-and-drop interface?

**URL:** https://community.thunkable.com/t/audio-stopped-event-in-the-drag-and-drop-interface/1941279
**Category:** Questions about Thunkable X
**Tags:** sound, audio, draganddrop, drag-and-drop
**Created:** [June 27, 2022, 1:56am UTC](https://community.thunkable.com/t/audio-stopped-event-in-the-drag-and-drop-interface/1941279 "2022-06-27T01:56:15Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![storycatcherzz78](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@storycatcherzz78](https://community.thunkable.com/u/storycatcherzz78)
#### Post date: [June 27, 2022, 1:56am UTC](https://community.thunkable.com/t/audio-stopped-event-in-the-drag-and-drop-interface/1941279/1 "2022-06-27T01:56:15Z")

</div>

I’ve been testing and trying to figure out how to take an action after my audio has finished playing (in the Drag and Drop interface). There seems to be one in Snap-To-Place, but I’ve come up empty so far with DnD.

Does this feature exist, and if not, has anyone seen a workaround?

---

<div class="post-metadata">

### Author: ![muneer](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/muneer/32/75210_2.png) [@muneer](https://community.thunkable.com/u/muneer)
#### Post date: [June 27, 2022, 8:09pm UTC](https://community.thunkable.com/t/audio-stopped-event-in-the-drag-and-drop-interface/1941279/2 "2022-06-27T20:09:58Z")

</div>

Can you show the code you tried?

---

<div class="post-metadata">

### Author: ![storycatcherzz78](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@storycatcherzz78](https://community.thunkable.com/u/storycatcherzz78)
#### Post date: [June 28, 2022, 9:04pm UTC](https://community.thunkable.com/t/audio-stopped-event-in-the-drag-and-drop-interface/1941279/3 "2022-06-28T21:04:08Z")

</div>

For sure - they’ve all been variations on something like this:

![image](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/b/e/beea602e4229f60689ef74d9dc376944b849ad36.png)

---

<div class="post-metadata">

### Author: ![muneer](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/muneer/32/75210_2.png) [@muneer](https://community.thunkable.com/u/muneer)
#### Post date: [June 29, 2022, 11:10am UTC](https://community.thunkable.com/t/audio-stopped-event-in-the-drag-and-drop-interface/1941279/4 "2022-06-29T11:10:25Z")

</div>

Check this demo project

[https://x.thunkable.com/projectPage/601cf5c2988b8128b77e801e](https://x.thunkable.com/projectPage/601cf5c2988b8128b77e801e)

---

<div class="post-metadata">

### Author: ![storycatcherzz78](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@storycatcherzz78](https://community.thunkable.com/u/storycatcherzz78)
#### Post date: [June 29, 2022, 10:03pm UTC](https://community.thunkable.com/t/audio-stopped-event-in-the-drag-and-drop-interface/1941279/5 "2022-06-29T22:03:44Z")

</div>

Thanks so much - I appreciate you putting the time in.

Unfortunately I couldn’t actually see a difference - the tracks start to overlap with one another.

If you could, maybe look at this demo project and see how it might get adjusted: [Thunkable](https://x.thunkable.com/copy/157b844d7c054b81d742006717e2cee8)

Here’s what I observe:

1. The label text ends up at “1342”
2. The full label text reaches that end point before the audio file has stopped playing.

Here’s what I would expect to happen:

1. The label text would start in the state “1”
2. The track would play, and once it is finished playing either “2” or “3” would be the next number ie. so the label text is now either “123” or “132”
3. “4” would be appended at the end of the label text.

---

<div class="post-metadata">

### Author: ![storycatcherzz78](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@storycatcherzz78](https://community.thunkable.com/u/storycatcherzz78)
#### Post date: [June 29, 2022, 10:10pm UTC](https://community.thunkable.com/t/audio-stopped-event-in-the-drag-and-drop-interface/1941279/6 "2022-06-29T22:10:47Z")

</div>

Huh, interesting note: the above occurs when live previewing in the browser.

If I live test on the device, I get the behavior outlined in the expected section.

Do you think this would be worth opening a ticket for? (asking in your capacity as someone who is potentially experienced with the bug reporting process)

---

<div class="post-metadata">

### Author: ![muneer](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/muneer/32/75210_2.png) [@muneer](https://community.thunkable.com/u/muneer)
#### Post date: [June 30, 2022, 9:42am UTC](https://community.thunkable.com/t/audio-stopped-event-in-the-drag-and-drop-interface/1941279/7 "2022-06-30T09:42:01Z")

</div>

It only works correctly from the phone.

The `Web Test` is a quick way to see if your app is doing what is expected of it but your typical platform to execute the app would be a mobile device.

I would say that this behavior needs to be tested on a `web app` and then a ticket should be raised if the `web app` version didn’t run as expected.

---

<div class="post-metadata">

### Author: ![storycatcherzz78](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@storycatcherzz78](https://community.thunkable.com/u/storycatcherzz78)
#### Post date: [July 4, 2022, 3:21am UTC](https://community.thunkable.com/t/audio-stopped-event-in-the-drag-and-drop-interface/1941279/8 "2022-07-04T03:21:51Z")

</div>

Yeh, I guess that’s fair. I would strong prefer that any form of testing mirrors production as closely as possible - diverging behavior just adds a lot of cognitive load for users.

But we can’t have everything I guess. Thanks for walking through this with me!

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/0/f/0f59f292712368bce16ff80133ae10de8a6f27e8.png) [@system](https://community.thunkable.com/u/system)
#### Post date: [October 2, 2022, 3:22am UTC](https://community.thunkable.com/t/audio-stopped-event-in-the-drag-and-drop-interface/1941279/9 "2022-10-02T03:22:29Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
