When hitting the play game button, everything is fine but the UIDragDetectors doesn’t work. I’ve also set each property correctly.
The fix that worked for me was to manually set the BoundingUI property to the correct one again using the studio tools. Scripting it to set it to nil and back to the correct one doesn’t fix it. Manually or scripting to disable and enable it again also doesn’t work.
Hopefully this will be a useful information. Or maybe I’ve been doing it wrong? Idk. I’ve just started tinkering with this new feature.
Is there an estimated release date for this feature and, as per my PM, do you know who I should contact with regards to the deprecated private modules?
Quick little discovery that I’ve just found, enabling and disabling the “Select” tool also fixes it for some reason. The default state that I had is none of the tools being activated.
Also I found a bug where when dragging on mobile (surfacegui) the thumbstick will still function, so you can’t really drag an ui that is close to the thumbstick
Ah yes, having a tool selected disables the usage of UIDragDetectors. Same goes for plugins, although that will change to being disabled only when UIEditor specifically is on, soon.
It moving 5000 pixels and disappearing is concerning and I’ve had reports of it-- I haven’t been able to reproduce it but it is something I’m continuously checking for.
As for usage during plugins: At the moment, it’s disabled for use when a tool or any plugin is active.
Next week’s release will come with a patch that disables it only when tools or the UIEditor plugin is active, so that should resolve the issue.
It might have something to do with the UI editor conflicting with UIDragDetector.
This only happens when I use them somewhere where I can also edit the UI (StarterGui).
It doesnt happen in play mode, in plugin widgets, in ScreenGuis inside CoreGui, it only happens in StarterGui in Edit Mode, which is also the only place where I can edit and resize the frame