there should be events that support multi-touch

when this sprite touched::events hat

so what it would do is it would run the event if the sprite is being touched. by “touched” i mean touch as in for a mobile device. so you can have multiple sprites being touched at once. this is different from clicking where you can only have one sprite being clicked at once.

and also i propose a sensing block for this

<this sprite touched?::sensing>

this would make making mobile controls way easier since you would now be able to make a joystick and a jump button that can be pressed at the same time

EDIT: also if you use mouse input then those blocks would behave exactly the same as their counterparts:

when this sprite clicked

<<touching [mouse pointer v]> and <mouse down>>

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

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

This already exists, as the:

when this sprite clicked

block, so there isn't any reason to add it.

-FasterThanLight- wrote:

This already exists, as the:

when this sprite clicked

block, so there isn't any reason to add it.

You probably don't know what game_pr0grammer is suggesting. He or she wants two things to be touched at once.

*laughs* This block already exists:

when this sprite clicked

By the way, here's a workaround for the other block:

<<touching [mouse pointer v]> and <mouse down?>>

Seth_Zaw wrote:

*laughs* This block already exists:

when this sprite clicked

By the way, here's a workaround for the other block:

<<touching [mouse pointer v]> and <mouse down?>>

You probably don't know what game_pr0grammer is suggesting. He or she wants two things to be able to be touched at once.

No support. This can be used to make mobile-only projects…

Scratch doesn't support multi-touch anyway, as far as I can tell. If it did, “when this sprite clicked” blocks can be used just fine.

nyankatpro wrote:

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

whats wrong with mobile-only projects? doesnt most people have a mobile device anyway?

xXRedTheCoderXx wrote:

-FasterThanLight- wrote:

This already exists, as the:

when this sprite clicked

block, so there isn't any reason to add it.

You probably don't know what game_pr0grammer is suggesting. He or she wants two things to be touched at once.

xXRedTheCoderXx wrote:

Seth_Zaw wrote:

*laughs* This block already exists:

when this sprite clicked

By the way, here's a workaround for the other block:

<<touching [mouse pointer v]> and <mouse down?>>

You probably don't know what game_pr0grammer is suggesting. He or she wants two things to be able to be touched at once.

I do not believe Scratch 3.0 has multi-touch compatibility, so this suggestion is a very particular one.

I wonder how much work would have to be done to gain such, or even if such is possible.

And as a side note, I'd recommend refraining from using “he or she” and using the all-encompassing gender neutral “they” if you don't know someone's gender. Some folx do not use “he” or “she” as pronouns, and use only “they”.

nyankatpro wrote:

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

Mobile projects are a key part of Scratch 3s viewpoints, and why you take issue with mobile-only when the majority of projects are PC-only, I don't know.

game_pr0grammer wrote:

nyankatpro wrote:

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

whats wrong with mobile-only projects? doesnt most people have a mobile device anyway?

No one would be able to use one on their computers. Some people don't even have phones! Only my mom knows where my phone is… and I haven't used it in weeks… Scratch doesn't like to cater (provide stuff) to some, it likes to cater to all people.

OurPrincess wrote:

game_pr0grammer wrote:

nyankatpro wrote:

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

whats wrong with mobile-only projects? doesnt most people have a mobile device anyway?

No one would be able to use one on their computers. Some people don't even have phones! Only my mom knows where my phone is… and I haven't used it in weeks… Scratch doesn't like to cater (provide stuff) to some, it likes to cater to all people.

But… most projects are PC-only and don't work on Mobile…

It is very hypocritical to banish this block for it allowing Phone-Only projects (when in reality, it'd be mostly used to add phone support to already PC-capable projects).

Basing the verdict of this suggestion off a hypothetical situation that may or may not occur on a per-project basis does not seem to be a great idea.

OurPrincess wrote:

Scratch doesn't like to cater (provide stuff) to some, it likes to cater to all people.

Scratch should fix that its projects are majority PC only then.

ElsieBreeze wrote:

OurPrincess wrote:

game_pr0grammer wrote:

nyankatpro wrote:

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

whats wrong with mobile-only projects? doesnt most people have a mobile device anyway?

No one would be able to use one on their computers. Some people don't even have phones! Only my mom knows where my phone is… and I haven't used it in weeks… Scratch doesn't like to cater (provide stuff) to some, it likes to cater to all people.

But… most projects are PC-only and don't work on Mobile…

It is very hypocritical to banish this block for it allowing Phone-Only projects (when in reality, it'd be mostly used to add phone support to already PC-capable projects).

Basing the verdict of this suggestion off a hypothetical situation that may or may not occur on a per-project basis does not seem to be a great idea.

This suggestion has really good potential, though… and I'm on semi-support at the moment. You can already jump and move left/right at the same time on mobile… with one finger.

OurPrincess wrote:

ElsieBreeze wrote:

OurPrincess wrote:

game_pr0grammer wrote:

nyankatpro wrote:

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

whats wrong with mobile-only projects? doesnt most people have a mobile device anyway?

No one would be able to use one on their computers. Some people don't even have phones! Only my mom knows where my phone is… and I haven't used it in weeks… Scratch doesn't like to cater (provide stuff) to some, it likes to cater to all people.

But… most projects are PC-only and don't work on Mobile…

It is very hypocritical to banish this block for it allowing Phone-Only projects (when in reality, it'd be mostly used to add phone support to already PC-capable projects).

Basing the verdict of this suggestion off a hypothetical situation that may or may not occur on a per-project basis does not seem to be a great idea.

This suggestion has really good potential, though… and I'm on semi-support at the moment. You can already jump and move left/right at the same time on mobile… with one finger.

Multi-touch would be a lovely addition, I just don't know whether it'd be possible from a technical perspective.

Regarding touch-only projects, I think the mouse can simulate a finger (but this won't work for projects requiring multiple touch inputs). Many projects already require keyboards, so this could be used as a compromise for keyboardless devices. I recall a suggestion asking for a message like “this project requires a keyboard” (which can be shown in the extensions list) for keyboard-using projects; something similar can be done for touch projects. In addition, some projects on Scratch rely on other physical things like those fancy lego and makey makey devices, so not all projects need to be 100% universal

ElsieBreeze wrote:

I do not believe Scratch 3.0 has multi-touch compatibility, so this suggestion is a very particular one.

I wonder how much work would have to be done to gain such, or even if such is possible.

I think Scratch's targeted browsers all support at least touch events, which support multiple touch inputs. Currently, Scratch VM only accepts one pointer position at a time, but I think that could be changed with not a ton of revolutionary rewriting. However, I think the main issue is how to make this available in the form of Scratch blocks

Scratch doesn't support first class lists for storing a list of pointers, but perhaps they could add these blocks:

when pointer is down::events hat
when pointer moves::events hat
when pointer is up::events hat
(pointer ID::sensing) // *
// modification of existing blocks
(pointer x of (0)::sensing) // accepts a pointer ID
(pointer y of (0)::sensing)
<pointer (0) is down?::sensing> // these two are not absolutely necessary since they can be workarounded with existing blocks
<touching pointer (0)?::sensing>

Where the pointer ID only reports a value while running one of the three new hat blocks. This ID can be stored in a variable to access pointer information at a later time

This is mostly based on how JavaScript deals with multiple pointers (event-based) and also how the ask/wait and answer blocks behave, but I'm not sure if this is the best way. Does anyone have a different idea for blocks?

Also, how can you click two sprites at once?

no support. you can do this just as easily with

when this sprite clicked

or

forever
if <touching [mouse pointer v] ?> then

end
end

or

forever
if <<touching [mouse pointer v] ?>and<mouse down?>> then

end
end

Plus it could make some projects non-computer friendly, and that's just weird.

StevenTheSquare wrote:

no support. you can do this just as easily with

when this sprite clicked

or

forever
if <touching [mouse pointer v] ?> then

end
end

or

forever
if <<touching [mouse pointer v] ?>and<mouse down?>> then

end
end

Plus it could make some projects non-computer friendly, and that's just weird.

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

Maybe change title of topic to “multi touch events.” Touch event sounds like what Scratch already does.