Scratch

lalala3 wrote:

Mokat wrote:

You should be able to turn the hiding off, because how would you see where you were clicking in games where the point of the game is to click objects?

Simple.
1. Don't play the game.
2. I imagine it as a setting within the project editor. That would deal with any issues quite nicely.

Edit: And before anyone tells me I'm necroposting, this is linked to from a stickied thread.

Mokat wrote:

you could press the escape key to show it again

here's what would be dangerous:

when flag clicked
go to mouse
if touching stop button
   say why are you not playing my game?
   forever
      hide mouse
      move [mouse] to x: 0 y: 0

But, just having a Hide Mouse block would be OK. and it would only hide if touching the Flash Player, or ScratchStageMorph, depending on the player.

Support.
And this would NOT be dangerous at all!
Things like cloud variables are WAY more dangerous!

lalala3 wrote:

iTweak0r wrote:

here's what would be dangerous:

when flag clicked
go to mouse
if touching stop button
   say why are you not playing my game?
   forever
      hide mouse
      move [mouse] to x: 0 y: 0

But, just having a Hide Mouse block would be OK. and it would only hide if touching the Flash Player, or ScratchStageMorph, depending on the player.

I was under the impression that it would not be possible to make the mouse hidden if it was not within the constraints of the player in question, and any Scratch Project I happened to be running offline that did such I would close immediately. And the hide mouse block isn't even relevant to that. It's not causing the problem. The move mouse block is the problem in that example.

If scratch was to allow for hiding the mouse that would be it, the mouse would be stuck in the game menu until the user presses the Esc key. The mouse pointer would never be able to therefor reach the stop button as it is not in the game window.
Also scratch would not allow for setting pointer position.

No danger then.

minecraftpe123 wrote:

lalala3 wrote:

iTweak0r wrote:

here's what would be dangerous:

when flag clicked
go to mouse
if touching stop button
   say why are you not playing my game?
   forever
      hide mouse
      move [mouse] to x: 0 y: 0

But, just having a Hide Mouse block would be OK. and it would only hide if touching the Flash Player, or ScratchStageMorph, depending on the player.

I was under the impression that it would not be possible to make the mouse hidden if it was not within the constraints of the player in question, and any Scratch Project I happened to be running offline that did such I would close immediately. And the hide mouse block isn't even relevant to that. It's not causing the problem. The move mouse block is the problem in that example.

If scratch was to allow for hiding the mouse that would be it, the mouse would be stuck in the game menu until the user presses the Esc key. The mouse pointer would never be able to therefor reach the stop button as it is not in the game window.
Also scratch would not allow for setting pointer position.
Exactly my point.
No danger then.

No. I did not mean that the user would be unable to move the mouse from the screen, I meant that I knew of no way to have the mouse pointer hidden if it was outside the player. As in, I was under the impression the way computers/programming languages work means that it's impossible to code in something that would hide the mouse pointer even outside of the player. It just shows automatically when your mouse leaves the window, no matter what the programmer tried to do. I said nothing about forcing the mouse pointer to remain within the Scratch player's window.

Support , also , scratch 2.0 has a ''box'' above the player in fullscreen and non-fullscreen. So , nothing in danger.

Gravitation wrote:

If only when touching project and not the green flag bar, I support. Otherwise this could be abused. 

Yes, if a Scratcher doesn't make their own cursor, there would be no way to tell where the cursor IS. My solution? Make the sprite layer able to go OVER the cursor. But then again, that would spawn new problems, so...

No support.

...And my "solution" won't really work either.

Last edited by Failord (2013-04-23 09:20:26)