[Read OP] "set cursor to" block - Featured as "not rejected" on TOLORS

Yoshiii999

bump

edit: <offtopic>king of the hill?? what was it called??</offtopic>

Last edited by Yoshiii999 (Jan. 28, 2024 16:27:59)

Thiago_le_meilleur

This is implemented in TurboWarp so I think they can put it on Scratch.

jellyfishfisher56

Support! The Scratch Team say it's ‘not rejected’, so why don't they just add it then.

Votick

I wish this was an extension category. maybe even changing the look of the mouse pointer.

make [default v] look like [costume 1 v] ::pen

set mouse pointer color to ( ::#FF0000) ::pen

Last edited by Votick (March 17, 2024 23:24:47)

Yoshiii999

Votick wrote:
I wish this was an extension category. maybe even changing the look of the mouse pointer.
make [default v] look like [costume 1 v] ::pen
set mouse pointer color to ( ::#FF0000) ::pen

custom cursors via costumes is rejected, but the default ones provided by your operating system are not. please read the original post (OP) next time

RobotChickens

jellyfishfisher56 wrote:
(#283)
Support! The Scratch Team say it's ‘not rejected’, so why don't they just add it then.

Resources, other priorities, low funding, and many other things.

mumu245

Votick wrote:
(#284)
I wish this was an extension category. maybe even changing the look of the mouse pointer.
make [default v] look like [costume 1 v] ::pen
set mouse pointer color to ( ::#FF0000) ::pen

Doing this would be hard as costumes can make it invisible.

scootyboy-2010

I want them to add this. I would probably make a game with a mouse customising option.

switch cursor to [Target v]

And maybe also Left/Right click.

when mouse is clicked [left v]

play sound [select button v]

<mouse [left v] down?>

<<mouse [left v] down?> and <mouse [right v]down?>>

Last edited by scootyboy-2010 (March 23, 2024 15:31:21)

taqi1109

how about adding your own cursor types?

when green flag clicked
forever
   if <touching [mouse-pointer v] ?> then
    set cursor to [cursor-drawing1 v]::sensing
   end

never mind, that will be to complicated

Last edited by taqi1109 (June 9, 2024 07:31:38)

Yoshiii999

taqi1109 wrote:
how about adding your own cursor types?
when green flag clicked
forever
   if <touching [mouse-pointer v] ?> then
    set cursor to [cursor-drawing1 v]::sensing
   end
never mind, that will be to complicated

I already told you, that idea is rejected.

That's not what I'm suggesting either, I'm just suggesting the default cursors you get with your system.

DangerPuppy10

I support, this would be a great way to tell somebody (you can click me?) without telling them.
Example:

when green flag clicked
forever
if <touching [mouse-pointer v] ?> then 

  set cursor to: [pointer v] :: custom

else
 set cursor to: [default v] :: custom
end
end

taqi1109

Yoshiii999 wrote:
taqi1109 wrote:
how about adding your own cursor types?
when green flag clicked
forever
   if <touching [mouse-pointer v] ?> then
    set cursor to [cursor-drawing1 v]::sensing
   end
never mind, that will be to complicated
I already told you, that idea is rejected.

That's not what I'm suggesting either, I'm just suggesting the default cursors you get with your system.

thanks for reminding!

Yoshiii999

bump

Draked12

cool idea

1080GBA

full support + bump

MillionOfficial

Someone could spam this to confuse users:

when green flag clicked
forever
set mouse pointer to [default v] :: sensing
set mouse pointer to [pointer v] :: sensing
set mouse pointer to [text v] :: sensing
set mouse pointer to [move v] :: sensing
end

Yoshiii999

MillionOfficial wrote:

Someone could spam this to confuse users:

when green flag clicked
forever
set mouse pointer to [default v] :: sensing
set mouse pointer to [pointer v] :: sensing
set mouse pointer to [text v] :: sensing
set mouse pointer to [move v] :: sensing
end

good point but the way that this would be implemented, the cursor will only change while the mouse is inside the project stage

8to16

Yoshiii999 wrote:
(#293)
bump

1080GBA

MillionOfficial wrote:

(#296)
Someone could spam this to confuse users:

when green flag clicked
forever
set mouse pointer to [default v] :: sensing
set mouse pointer to [pointer v] :: sensing
set mouse pointer to [text v] :: sensing
set mouse pointer to [move v] :: sensing
end

its not confusing?

Peneren

MillionOfficial wrote:

Someone could spam this to confuse users:

when green flag clicked
forever
set mouse pointer to [default v] :: sensing
set mouse pointer to [pointer v] :: sensing
set mouse pointer to [text v] :: sensing
set mouse pointer to [move v] :: sensing
end

I don't imagine this being a big deal tbh.

Also, I support this discussion fully. It would allow more customization and would allow for better indicators as to what you can do in the project.

I do have 1 more idea: The ability to “hide” the cursor, but it only works if a setting is enabled, which defaults to being disabled. (I understand you've probably heard the “just add an option” argument many times, for many different rejected suggestions, but it could work.) I do understand the Scratch Team's hesitance to implement something like this as it can be confusing even if you know what's happening. (professional mouse cursor loser here)
I wouldn't be too upset if this is not implemented but it is a cool idea.

Discuss Scratch