when [space v] key pressed

titanscratch wrote:

There's one gigantic problem:
Everybody knows that mobile phones and tablets don't have keyboards! So for this block…

when [space v] key pressed

…to work, there needs to be a keyboard! But mobile phones and tablets don't have keyboards so the block won't work!

Ed8 wrote:

HTML5 loading sign idea for scratch 3.0: click here to go to image
code:

Big code here that i snipped to save space in an edit that i made just now because i realised that the code was too long and needed a snip to save fourm space so this page doesn't get full with just two posts. I'm sorry, i was talking to someone while typing this and i just kept on typin'

Sigton wrote:

titanscratch wrote:

There's one gigantic problem:
Everybody knows that mobile phones and tablets don't have keyboards! So for this block…

when [space v] key pressed

…to work, there needs to be a keyboard! But mobile phones and tablets don't have keyboards so the block won't work!

Please don't-
- Talk in full caps (especially large, bold etc)
- Symbol spam
- Emoji spam
This is the AT's, not the new scratcher's forum

I'm sure that the ST will have a solution for this, since it would be a bit of an oversight not to account for this

Sigton

titanscratch wrote:

There's one GIGANTIC problem:
Everybody knows that mobile phones and tablets DON'T have keyboards! So for this block…

when [space v] key pressed

…to work, there needs to be a keyboard! But mobile phones and tablets DON'T have keyboards so the block won't work!!!!!!!!!!

thisandagain wrote:

titanscratch wrote:

There's one GIGANTIC problem:
Everybody knows that mobile phones and tablets DON'T have keyboards! So for this block…

when [space v] key pressed

…to work, there needs to be a keyboard! But mobile phones and tablets DON'T have keyboards so the block won't work!!!!!!!!!!

Good catch. That is indeed something we are thinking about / working on!

awesome5185 wrote:

Ed8 wrote:

HTML5 loading sign idea for scratch 3.0: click here to go to image
code:

Big code here that i snipped to save space in an edit that i made just now because i realised that the code was too long and needed a snip to save fourm space so this page doesn't get full with just two posts.

Is this just the styling or is it meant to work? Also with what you have, it would just jump from start to finish.

awesome5185 wrote:

thisandagain wrote:

titanscratch wrote:

mobile phones and tablets DON'T have keyboards

Good catch. That is indeed something we are thinking about / working on!

I think that nothing should happen as workarounds would be too complicated. So maybe a detect if running on mobile block? So that people can code an entirely new UI just for mobile.

awesome5185 wrote:

thisandagain wrote:

titanscratch wrote:

There's one gigantic problem:
Everybody knows that mobile phones and tablets don't have keyboards! So for this block…

when [space v] key pressed

…to work, there needs to be a keyboard! But mobile phones and tablets don't have keyboards so the block won't work!!!!!
~snip~

Good catch. That is indeed something we are thinking about / working on!

I think that nothing should happen as workarounds would be too complicated. So maybe a detect if running on mobile block? So that people can code an entirely new UI just for mobile.

thisandagain wrote:

Good catch. That is indeed something we are thinking about / working on!

“The project you using is not made with mobile devices in mind please use a computer to view this”
Continue?

“The project you are using has not been edited in Scratch 3.0 therefor it may not have mobile support”
Continue?

hiccup01 wrote:

awesome5185 wrote:

thisandagain wrote:

titanscratch wrote:

There's one gigantic problem:
Everybody knows that mobile phones and tablets don't have keyboards! So for this block…

when [space v] key pressed

…to work, there needs to be a keyboard! But mobile phones and tablets don't have keyboards so the block won't work!!!!!
~snip~

Good catch. That is indeed something we are thinking about / working on!

I think that nothing should happen as workarounds would be too complicated. So maybe a detect if running on mobile block? So that people can code an entirely new UI just for mobile.

The issue with a isMobile? block is that mobile compatibility would still be broken on older projects…

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

titanscratch wrote:

And mobile phones and tablets don't have mouses so these blocks won't work as well!

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

P.S. You can plug in a keyboard and a mouse into some tablets, including mine!

dzaima wrote:

titanscratch wrote:

And mobile phones and tablets don't have mouses so these blocks won't work as well!

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

P.S. You can plug in a keyboard and a mouse into some tablets, including mine!

Mouse does work as the touch point. <mouse down?> would equal is screen touched, <touching mouse-pointer?> “is a/the(whether to allow multi-touch or not is a big decision) touch point on me”.
Another thing is multi-touch support - I'd guess that it wouldn't be added (trough it would be cool and advanced scratchers could probably do it if <touching mouse-pointer?> gives true for any point not just one).
About keyboard stuff - there should probably be some option to allow a virtual keyboard (trough an issue would be (as far as I know) that android keyboards don't support “is key pressed”, only “when key pressed”) for compatibility, but that should be an option.

DeleteThisAcount wrote:

“The project you using is not made with mobile devices in mind please use a computer to view this”
Continue?

Add a check mark while sharing project “Works with mobile devices”

“The project you are using has not been edited in Scratch 3.0 therefor it may not have mobile support”
Continue?

Also add a isMobile? block

Greenduck54 wrote:

I'm wondering… will the size of the stage/max size of costumes and backdrops will be increased to 1920 x 1080???

IgDegOo wrote:

Greenduck54 wrote:

I'm wondering… will the size of the stage/max size of costumes and backdrops will be increased to 1920 x 1080???

no

IgDegOo wrote:

Greenduck54 wrote:

I'm wondering… will the size of the stage/max size of costumes and backdrops will be increased to 1920 x 1080???

no

thisandagain wrote:

happyland440 wrote:

I hope Scratch will be in the 16:9 ratio for us with 1080p screens. Finally, some HD projects.

We are considering that, though we are not 100% sure how we will deal with backwards compatibility quite yet. Stay tuned.

thisandagain wrote:

happyland440 wrote:

I hope Scratch will be in the 16:9 ratio for us with 1080p screens. Finally, some HD projects.

We are considering that, though we are not 100% sure how we will deal with backwards compatibility quite yet. Stay tuned.