Why doesn't .Draggable work on mobile?

[acreol]

I would assume it has something to do with mobile having multi finger touch capabilities but I’m not really sure how that would limit it

[inHeadspace (vee)]

The app can’t distinguish between the user wanting to drag the gui versus wanting to move the camera.

If it’s a larger transparent gui with draggable on true, that would be an easy way to make mobile players unable to move the camera without hassle.

[EmeraldSlash (Rio)]

I guess, like Starception said, because it can’t distinguish what the user is actually trying to do.

It is possible to make your own custom dragging functionality using UserInputService/ContextActionService (actually, I think you don’t event need to use those – you could just use the InputBegan/Changed/Ended signals on GUI objects).

[ChipioIndustries (chipio)]

The Draggable property has been deprecated, so it’s a good idea to make your own system instead as suggested above. If you’re not interested in remaking it yourself, here’s a script by TiffBlocks that should work on mobile:

Draggable property is hidden on gui objects

It’s never worked very well, and it’s not very flexible. You can’t implement behaviors like snapping or constraints using it, and when you decide you need those, your only option is to rewrite it from scratch. The concept of clicking and dragging is also foreign for gamepad controls, so relying on them in your UX is kind of bad. Here’s a snippet which actually works better than the Draggable property ever did. local UserInputService = game:GetService("UserInputService") local gui = script.Par…

[acreol]

I thought Draggable forced Active so it wouldn’t matter (and if I’m wrong about that, we can just as easily manually enable Active)