Discuss Scratch

badatprogrammingibe
Scratcher
500+ posts

Colour of pixel at location.

Could look something like this, and either could return a hex value of the colour or another form.
(color of pixel at x: () y: () :: sensing)
Anyways this is needed as the workarounds are very cumbersome and slow.

Last edited by badatprogrammingibe (April 9, 2019 01:47:28)

Za-Chary
Scratch Team
1000+ posts

Colour of pixel at location.

Could you give a specific example of how this might be useful? (Something other than “it can be used to detect color at a certain location”.)

In addition, what could it return, hexadecimal values for color?

It looks like I'm a Scratch Team member now!

Za-Chary's Game Museum
The Complete List of Rejected Suggestions
badatprogrammingibe
Scratcher
500+ posts

Colour of pixel at location.

Za-Chary wrote:

Could you give a specific example of how this might be useful? (Something other than “it can be used to detect color at a certain location”.)

In addition, what could it return, hexadecimal values for color?
If you look at projects that scan pictures to lists, they are very slow as they cannot directly detect the colour of a pixel at a specific location, rather they must go through every colour for every pixel.
This would allow for fast scanning.

I suppose it would return hexadecimal values for colour, however scratch could choose to implement it differently than I have in mind (for example using scratch's in built colour mechanism.)
Tallented-Code-bot
Scratcher
100+ posts

Colour of pixel at location.

No support, this could allow people to scan from the camera and put it on a cloud variable, than look at it and possibly record them.
Za-Chary
Scratch Team
1000+ posts

Colour of pixel at location.

badatprogrammingibe wrote:

Za-Chary wrote:

Could you give a specific example of how this might be useful? (Something other than “it can be used to detect color at a certain location”.)

In addition, what could it return, hexadecimal values for color?
If you look at projects that scan pictures to lists, they are very slow as they cannot directly detect the colour of a pixel at a specific location, rather they must go through every colour for every pixel.
This would allow for fast scanning.

I suppose it would return hexadecimal values for colour, however scratch could choose to implement it differently than I have in mind (for example using scratch's in built colour mechanism.)
Hmm…that does sound cool.

Overall, I'd say semi-support because you'd be able to make some really cool stuff with this. However, one would have to consider very heavily how this boolean returns stuff. Would it return a hexadecimal value? If so, that may be confusing for younger users. Would it return a list of numbers representing the colors in the editor? If so, that may be tough since no other Scratch boolean returns lists (to my knowledge).

I do think it could work, though. It would just require some thought, as always.

It looks like I'm a Scratch Team member now!

Za-Chary's Game Museum
The Complete List of Rejected Suggestions
DaEpikDude
Scratcher
1000+ posts

Colour of pixel at location.

Za-Chary wrote:

badatprogrammingibe wrote:

Za-Chary wrote:

Could you give a specific example of how this might be useful? (Something other than “it can be used to detect color at a certain location”.)

In addition, what could it return, hexadecimal values for color?
If you look at projects that scan pictures to lists, they are very slow as they cannot directly detect the colour of a pixel at a specific location, rather they must go through every colour for every pixel.
This would allow for fast scanning.

I suppose it would return hexadecimal values for colour, however scratch could choose to implement it differently than I have in mind (for example using scratch's in built colour mechanism.)
Hmm…that does sound cool.

Overall, I'd say semi-support because you'd be able to make some really cool stuff with this. However, one would have to consider very heavily how this boolean returns stuff. Would it return a hexadecimal value? If so, that may be confusing for younger users. Would it return a list of numbers representing the colors in the editor? If so, that may be tough since no other Scratch boolean returns lists (to my knowledge).

I do think it could work, though. It would just require some thought, as always.
I'd imagine it's probably supposed to be a reporter:
(color at x: () y: ()::sensing)

Pirate: The cannons be ready, Cap'n!
Captain: *are
Za-Chary
Scratch Team
1000+ posts

Colour of pixel at location.

DaEpikDude wrote:

I'd imagine it's probably supposed to be a reporter:
(color at x: () y: ()::sensing)
Ah, good point. That must be what @badatprogrammingibe was referring to. It still may be a little tough to determine what it returns, though.

It looks like I'm a Scratch Team member now!

Za-Chary's Game Museum
The Complete List of Rejected Suggestions
badatprogrammingibe
Scratcher
500+ posts

Colour of pixel at location.

DaEpikDude wrote:

Za-Chary wrote:

badatprogrammingibe wrote:

Za-Chary wrote:

Could you give a specific example of how this might be useful? (Something other than “it can be used to detect color at a certain location”.)

In addition, what could it return, hexadecimal values for color?
If you look at projects that scan pictures to lists, they are very slow as they cannot directly detect the colour of a pixel at a specific location, rather they must go through every colour for every pixel.
This would allow for fast scanning.

I suppose it would return hexadecimal values for colour, however scratch could choose to implement it differently than I have in mind (for example using scratch's in built colour mechanism.)
Hmm…that does sound cool.

Overall, I'd say semi-support because you'd be able to make some really cool stuff with this. However, one would have to consider very heavily how this boolean returns stuff. Would it return a hexadecimal value? If so, that may be confusing for younger users. Would it return a list of numbers representing the colors in the editor? If so, that may be tough since no other Scratch boolean returns lists (to my knowledge).

I do think it could work, though. It would just require some thought, as always.
I'd imagine it's probably supposed to be a reporter:
(color at x: () y: ()::sensing)
Yeah, that's what it was supposed to be.
Sheep_maker
Scratcher
1000+ posts

Colour of pixel at location.

Duplicate

- Sheep_maker This is a kumquat-free signature. :P
This is my signature; it appears below all my posts. Make your own at https://scratch.mit.edu/discuss/settings/YOUR USERNAME/.
Screen recording has been added to Scratch 2.0!
.postsignature { overflow: auto; } .scratchblocks { overflow-x: auto; overflow-y: hidden; }

Powered by DjangoBB

Standard | Mobile