You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am upgrading my app to tauri v2 and i am using svelte-tauri-filedrop. So i am also upgrading that component which relies on drop events.
The first issue is that it not really documented how the events name changed. Would be nice to have that in the migration page.
Now the biggest issue is that those new events are useless without files path. We now only have the position of the drop (which is nice).
Could we have this fixed ?
It is a show stopper for apps, using drag&drop, to migrate to v2
This was by design to avoid some memory allocations on repeated events like hover, instead you get the file paths first on entry and then again on drop. I don't know the use-case or the need for paths on each hover event but the plugin will need to update its code to save the paths on entry into a variable and use these again in the hover events.
Describe the bug
I am upgrading my app to tauri v2 and i am using svelte-tauri-filedrop. So i am also upgrading that component which relies on drop events.
The first issue is that it not really documented how the events name changed. Would be nice to have that in the migration page.
Now the biggest issue is that those new events are useless without files path. We now only have the position of the drop (which is nice).
Could we have this fixed ?
It is a show stopper for apps, using drag&drop, to migrate to v2
Reproduction
example here https://github.com/probablykasper/svelte-tauri-filedrop
Expected behavior
example working
Full
tauri info
outputStack trace
No response
Additional context
https://discordapp.com/channels/616186924390023171/1239492999382302730
The text was updated successfully, but these errors were encountered: