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

saverofthewo

im getting frustrated nobody is reading OP

windows-11-pro

XxhackerlolxX wrote:
(#153)
I HATE when people reject things due to the VERY MINUSCULE CHANCE it could be miss used. This has ruined cloud variables, and many interesting suggestions. Everything has a weakness that can be exploited to cause chaos.

even this block?

go to x: () y: ()

Last edited by windows-11-pro (July 11, 2022 01:59:54)

-Valtren-

XxhackerlolxX wrote:
(#153)
I HATE when people reject things due to the VERY MINUSCULE CHANCE it could be miss used. This has ruined cloud variables, and many interesting suggestions. Everything has a weakness that can be exploited to cause chaos.

even this block?

go to x: (-69) y: ()

need I say more

also I doubt that anyone on the website is actually going to use the block, and it'll be very surprising to the younger users who randomly had their mouse change shape and can't understand why.

Last edited by -Valtren- (Aug. 15, 2022 01:02:27)

IndexErrorException

windows-11-pro wrote:
XxhackerlolxX wrote:
(#153)
I HATE when people reject things due to the VERY MINUSCULE CHANCE it could be miss used. This has ruined cloud variables, and many interesting suggestions. Everything has a weakness that can be exploited to cause chaos.
even this block?

go to x: () y: ()

Yes. Normally scratch prevents things from going off screen but with this block and a massive costume I can it go off the screen, thus exploiting the block for use not intended by scratch.

Last edited by IndexErrorException (July 11, 2022 09:12:46)

saverofthewo

XxhackerlolxX wrote:
windows-11-pro wrote:
XxhackerlolxX wrote:
(#153)
I HATE when people reject things due to the VERY MINUSCULE CHANCE it could be miss used. This has ruined cloud variables, and many interesting suggestions. Everything has a weakness that can be exploited to cause chaos.
even this block?

go to x: () y: ()

Yes. Normally scratch prevents things from going off screen but with this block and a massive costume I can it go off the screen, thus exploiting the block for use not intended by scratch.

but that IS NOT ABUSE, also, there is a very high chance the ability to HIDE THE MOUSE CURSOR will be abused

IndexErrorException

saverofthewo wrote:
XxhackerlolxX wrote:
windows-11-pro wrote:
XxhackerlolxX wrote:
(#153)
I HATE when people reject things due to the VERY MINUSCULE CHANCE it could be miss used. This has ruined cloud variables, and many interesting suggestions. Everything has a weakness that can be exploited to cause chaos.
even this block?

go to x: () y: ()

Yes. Normally scratch prevents things from going off screen but with this block and a massive costume I can it go off the screen, thus exploiting the block for use not intended by scratch.
but that IS NOT ABUSE, also, there is a very high chance the ability to HIDE THE MOUSE CURSOR will be abused

Abused how? OMG GUYS MY CURSOR IS INVISIBLE WHAT DO I DO? All one would have to do is just move their mouse around until it gets off the stage at which then it would be visible again. The benefits of changing the cursor is much better than the very minor problem caused by potential abuse.

That's like banning all cars because they can be used to run someone over…

saverofthewo

XxhackerlolxX wrote:
saverofthewo wrote:
XxhackerlolxX wrote:
windows-11-pro wrote:
XxhackerlolxX wrote:
(#153)
I HATE when people reject things due to the VERY MINUSCULE CHANCE it could be miss used. This has ruined cloud variables, and many interesting suggestions. Everything has a weakness that can be exploited to cause chaos.
even this block?

go to x: () y: ()

Yes. Normally scratch prevents things from going off screen but with this block and a massive costume I can it go off the screen, thus exploiting the block for use not intended by scratch.
but that IS NOT ABUSE, also, there is a very high chance the ability to HIDE THE MOUSE CURSOR will be abused

Abused how? OMG GUYS MY CURSOR IS INVISIBLE WHAT DO I DO? All one would have to do is just move their mouse around until it gets off the stage at which then it would be visible again. The benefits of changing the cursor is much better than the very minor problem caused by potential abuse.

That's like banning all cars because they can be used to run someone over…

bruh, stop discussing it here its already rejected

also scratch is all ages, a child is gonna be confused if they cant see their mouse cursor, and plus that feature wouldn't be useful as it serves pretty much no purpouse other than something that works in certain circumstances unlike CSS cursors which are meant to tell you "you can click this, you can drag this, ect)

maahay

B)

graham3078

This is already rejected.

lapisi

graham3078 wrote:
(#169)
This is already rejected.

READ THE OP

saverofthewo

bump

MagentaDude1359

I was going to post a topic about this but then I found this and I have 100% support!

Yoshiii999

bump

ChloeKohli

graham3078 wrote:
This is already rejected.

Lol no it isnt

DifferentDance8

saverofthewo wrote:
it serves pretty much no purpouse other than something that works in certain circumstances

In OSes, invisible cursors provide a more authentic experience while the OS is starting up. It could also be used for animation projects, where fine details are important.

Yoshiii999

DifferentDance8 wrote:
saverofthewo wrote:
it serves pretty much no purpouse other than something that works in certain circumstances
In OSes, invisible cursors provide a more authentic experience while the OS is starting up. It could also be used for animation projects, where fine details are important.

1. This suggestion is NOT suggesting invisible cursors.
2. Even if it was, TOLORS rejected invisible cursors.

Little_Mittle12345

When Mouse pointer is [normal v]:: sensing hat
Set cursor to [normal v]:: sensing
Set cursor to [pointing hand v]:: sensing
Set cursor to [grabbing hand v]:: sensing
Set cursor to [grab hand v]:: sensing
Set cursor to [up-down v] arrow:: sensing
Set cursor to [left-right v] arrow:: sensing
Set cursor to [nw resize v] arrow:: sensing
Set cursor to [sw resize v] arrow:: sensing
Set cursor to [move v] arrow:: sensing
Set cursor to [crosshair v] arrow:: sensing
Set cursor to [text v]:: sensing

Add more ideas. And this is not rejected.

Last edited by Little_Mittle12345 (Oct. 6, 2022 19:58:24)

blablablahello

people really do need to read the OP before replying lol

yea this would be cool

there is a chance of there being glitches that could cause things like invisible cursors tho, so if this was to be added, the ST should make sure there isn't any glitches that are relatively common before releasing it

Last edited by blablablahello (Oct. 6, 2022 21:52:15)

mumu245

blablablahello wrote:
people really do need to read the OP before replying lol

yea this would be cool

there is a chance of there being glitches that could cause things like invisible cursors tho, so if this was to be added, the ST should make sure there isn't any glitches that are relatively common before releasing it

how?

saverofthewo

mumu245 wrote:
blablablahello wrote:
people really do need to read the OP before replying lol

yea this would be cool

there is a chance of there being glitches that could cause things like invisible cursors tho, so if this was to be added, the ST should make sure there isn't any glitches that are relatively common before releasing it
how?

cursor not rendering, and scratch users like to try to lag it until it glitches out so yeah, just yknow fix the fact it takes 2 blocks to crash a tab

Discuss Scratch