Oops. I posted on the dupe..

Anyways, support. Mobile games like Minecraft suppport multiple touch spots.

One question.. what does mouse x and mouse y report?

Full support.

Support! It would be much easier to make mobile games if they add that.

Here's my block suggestions:

<sprite pressed?::sensing>

This block is basically a boolean version of “when sprite clicked” and it supports multiple touches

(mouse x offset from click::sensing)
(mouse y offset from click::sensing)

These two give the X or Y offset from a click (example: if your sprite is at (0, -5) and you click at (0, 5) the output from (mouse x offset from click) would be 10)

Here's a possible use:

when green flag clicked
hide
go to x:(-200) y:(-50)
switch costume to [joystick v]
create clone of [myself v]
go to x:(175) y:(25)
switch costume to [button x v]
create clone of [myself v]
go to x:(225) y:(75)
switch costume to [button o v]
create clone of [myself v]

when i start as a clone
forever
if <(costume name) = [joystick]> then
if <sprite pressed?::sensing> then
change [playerX v] by (mouse x offset from click::sensing)
change [playerY v] by (mouse y offset from click::sensing)
end
end
if <(costume name) = [joystick]> then
replace item (1) of [button presses v] with <sprite pressed?::sensing>
end
if <(costume name) = [joystick]> then
replace item (2) of [button presses v] with <sprite pressed?::sensing>
end
end

MAZ3MAK3R wrote:

Here's my block suggestions:

<sprite pressed?::sensing>

This block is basically a boolean version of “when sprite clicked” and it supports multiple touches

(mouse x offset from click::sensing)
(mouse y offset from click::sensing)

These two give the X or Y offset from a click (example: if your sprite is at (0, -5) and you click at (0, 5) the output from (mouse x offset from click) would be 10)

SNIP SNIP GOTTA CLIP

this thread is not about that, you should instead go make your own thread. this thread is about multi-touch events.

And besides mouse offset from click has a very trivial workaround

((mouse x) - (x position))
((mouse y) - (y position))

gosoccerboy5 wrote:

One question.. what does mouse x and mouse y report?

Well, mouse x and mouse y would stay unchanged I guess.

EDIT: They are called mouse x and y after all. Not touch x and y.

No support, most people don't play Scratch projects on phones and unlike the physical extensions I don't see very much educational potential in adding this. Maybe a “phone features” extension would be alright, along with other things like motion sensing? (Saw a suggestion for that once)

"fdreerf" wrote:

I'm not sure what you're saying you can make mobile-only games because on mobile taps “jump” from point to point. How would a project detect that without getting needlessly complicated? Frankly, I don't support this. There really isn't a need for this; how exactly this would be useful? Scratch was meant for computer and built for computer. Do people actually use Scratch on mobile devices, if so I must give them a round of applause for navigating a website meant to be displayed on a computer on a smaller screen. As well as that, there would be mobile-only projects. PC-only projects do exist in the form of anything that uses the keyboard.

This is smooth-brain thinking.

It wouldn't hurt to add some mobile accessibility to the site. A lot of genius things can be made if you have multiple fingers in the picture instead of just one cursor.

fdreerf wrote:

A lot of genius things can be made if you have multiple fingers in the picture instead of just one cursor.

I don't like the idea of having too many projects which are inaccessible to PC users, but I agree with this, and that's why I support it as an extension. Perhaps this kind of thing will be a self-regulating issue anyway; the less people who are able to play your project, the less people who will give love-its.

Mr_PenguinAlex wrote:

nyankatpro wrote:

This could easily be used to make mobile-only projects… no support.

Is… that a bad thing?

I don't know. We have plenty of computer-only projects right now anyway.

Support to a very large degree.
Possibly a mobile-features extension.

nyankatpro wrote:

This could easily be used to make mobile-only projects… no support.

mobile-only projects exist already tho most big projects I'm working on dont work on PC and I can't add pc support if I don't have a keyboard

Support. would be easier for mobile-only projects and they could just make a pc version of the project

they should at someting like this:

(touchX :: touchX)
(touchY :: touchY)

both are lists containing the touch positions. they are ordered by time:
first on the top
last at the bottom

nyankatpro wrote:

This could easily be used to make mobile-only projects… no support.

True.

Alex-2739 wrote:

they should at someting like this:

(touchX :: touchX)
(touchY :: touchY)

both are lists containing the touch positions. they are ordered by time:
first on the top
last at the bottom

Cool necropost my guy

game_pr0grammer wrote:

StevenTheSquare wrote:

~snip~

do you not know what i am talking about you only have one mouse coordinate only so you can only press on one sprite and humans do not have only one finger they have ten so they can press the screen at ten different areas of the screen and i am suggesting a way to detect whether one of those touches are touching a sprite so you can have ten sprites being touched at once but you can only have one sprite being clicked at once people do you not read the entire thing

and you can probably make non-computer friendly projects anyway using current methods since when they track your mouse x and mouse y in mobile there is no light gun or something tracking your finger when its off the screen so it only tracks where you touched meaning that movements go from one point to another in an instant while on a computer you can't do this so when you want your mouse to go from point a to b your mouse goes through many points between a and b until you finally reach the goal

That is exactly what the

when this sprite clicked

block does. It should be called

when this sprite pressed::events hat

maybe this can be added on turbowarp or by using inspect element (note: this is kinda like adding controller support without the google extenison.) then pasting in a block of code and them bam but on mobile idk i just hope it comes in some way

nyankatpro wrote:

This could easily be used to make mobile-only projects… no support.

i mean aren't the majority of scratch games PC only games? That's like saying we should ban the makey maker controller because a majority of people don't have it. support, only opens up new possibilities

xXRedTheCoderXx wrote:

Support. Mobile projects would be much easier, with 2 things being able to be touched at once

This is a must