Discuss Scratch
- Discussion Forums
- » Suggestions
- » Color at x: () y: () block.
- Zydrolic
-
1000+ posts
Color at x: () y: () block.
Depends if they even want it. Pretty sure this is already rejected though should I just keep posting about this so that it stays high up on the list so scratch implements it?
Also bumping the topic every 24 hours is better than reposting it, or constantly hindering other people's suggestions by bumping earlier.
incase you dunno what a Bump is just click here
Last edited by Zydrolic (July 2, 2023 17:16:46)
- LilyMakesThings
-
100+ posts
Color at x: () y: () block.
Absolutely not. This thread has been open for years. should I just keep posting about this so that it stays high up on the list so scratch implements it?
- medians
-
1000+ posts
Color at x: () y: () block.
How is it rejected? Shouldn't and wouldn't it be closed if that were the case?Depends if they even want it. Pretty sure this is already rejected though should I just keep posting about this so that it stays high up on the list so scratch implements it?
Anyway, bringing this topic up.
- scienceexplorer1
-
100+ posts
Color at x: () y: () block.
(#6)Cloud variables take up to much storage to be able to store an entire face.
It could be a privacy problem if you show a picture from the camera and there is a quick way to scan that and store in a cloud variable.
Color scanning os already possible with Griffpatch's color screen scanner, https://www.youtube.com/watch?v=3lz1nylUHiY&ab_channel=griffpatch with very efficient methods.
I personally find it kind of weird that you have to workaround for this, and this block itself I tend to use for other bigger workarounds(IMO) such as for erasing pen. I don't want to be necroposting, so yes I do think that getting a color at a specific block should be allowed
- Zydrolic
-
1000+ posts
Color at x: () y: () block.
(#204)It's not, I misread the post and thought it was rejected because of Section 1.7 since it contains a similar block.How is it rejected? Shouldn't and wouldn't it be closed if that were the case?Depends if they even want it. Pretty sure this is already rejected though should I just keep posting about this so that it stays high up on the list so scratch implements it?
Anyway, bringing this topic up.
Last edited by Zydrolic (July 3, 2023 16:13:14)
- TeenySpoon
-
500+ posts
Color at x: () y: () block.
Wow, this would be really useful! I know color scanners exist but it would be more concise to have it in one block.
Also, I think everyone knows this by now, but video sensing is turned off when cloud variables are used, so taking pictures of a person's face is impossible.
Also, I think everyone knows this by now, but video sensing is turned off when cloud variables are used, so taking pictures of a person's face is impossible.
- IndexErrorException
-
500+ posts
Color at x: () y: () block.
This would be awesome for making projects with pixel color rendering. Being able to set and get colors at a pixel on the screen. You can use pen to get a similar effect but this could be a lot more performant.
- ProfessorThickhead
-
100+ posts
Color at x: () y: () block.
It's the other way around. Cloud variables re disabled when Video Sensing is used. Also, I think everyone knows this by now, but video sensing is turned off when cloud variables are used, so taking pictures of a person's face is impossible.
- mumu245
-
1000+ posts
Color at x: () y: () block.
(#1)This is problematic because colours can have multiple shades and saturations.
and would give you the number that you would use in theset pen color to ()to make that color
Better mockup:
set pen color to [#ffaa44]
set pen color to (color code at x: (0) y: (0) ::pen)
set pen (color v) to (24) ::pen
set pen (color v) to ((color v) at x: (0) y: (0) ::pen) ::pen
set pen (saturation v) to (78) ::pen
set pen (saturation v) to ((saturation v) at x: (0) y: (0) ::pen) ::pen
set pen (brightness v) to (99) ::pen
set pen (brightness v) to ((brightness v) at x: (0) y: (0) ::pen) ::pen
- Captain-Doggo
-
100+ posts
Color at x: () y: () block.
Actually, cloud variables + video = cloud disabledYes, that could be a problem with this block. Maybe if there was a project with a video block, this block, and cloud variables, it would have a warning like this: It could be a privacy problem if you show a picture from the camera and there is a quick way to scan that and store in a cloud variable.This project contains the “Color on X, Y,” block, video sensing, and cloud variables. Thus, this project might take a picture of and/or videotape you. If you are concerned about this, please use “See Inside” and look at the scripts and check that this project will not take a picture of and/or videotape you.
- undeterminstic
-
1000+ posts
Color at x: () y: () block.
no it would be slow taking two secondsYou can go fast using run without screen refresh and use it in many clones, thus stealing images quickly and easily.You can't freeze the webcam, so someone would have to stay still for a long time to get a decent picture them. Besides, that script isn't the most efficient way to scan the screen, although it is the simplest.BAD BAD BAD. STAHP GIVING OUT WAYS TO STEAL IMAGES OF PPL. Color at x, y block would be really useful for 100% pen games. But to check a color for a cloud draw program you can use this:set [r v] to (0)
repeat (32)
set [g v] to (0)
repeat (32)
set [b v] to (0)
repeat (16)
if <touching color (((r) * (65536)) + (((g) * (256)) + (b)))> then
add (((r) * (65536)) + (((g) * (256)) + (b))) to [color scan v]
end
change [b v] by (16)
end
change [g v] by (8)
end
change [r v] by (8)
end
In all seriousness, this workaround needs to be silenced as it can steal people's images and stash them in cloud where they cannot be modified by you in any way.
- cookieclickerer33
-
1000+ posts
Color at x: () y: () block.
1: stop arguing, projects cannot use cloud variables and video sensing at the same time, if you try to it disables them
2: what would this return? colors arent a datatype in scratch
2: what would this return? colors arent a datatype in scratch
- undeterminstic
-
1000+ posts
Color at x: () y: () block.
I think it would return hex code 2: what would this return? colors arent a datatype in scratch
- cookieclickerer33
-
1000+ posts
Color at x: () y: () block.
yeah it would have to as thats what used for the inputs of blocks that use colorI think it would return hex code 2: what would this return? colors arent a datatype in scratch
but wouldnt that be really confusing? hex codes are very arbitrary
- undeterminstic
-
1000+ posts
Color at x: () y: () block.
ya but you would just input into set pen color to or something but hex codes are confusingyeah it would have to as thats what used for the inputs of blocks that use colorI think it would return hex code 2: what would this return? colors arent a datatype in scratch
but wouldnt that be really confusing? hex codes are very arbitrary
- cookieclickerer33
-
1000+ posts
Color at x: () y: () block.
maybe you could pick hue saturation brightness and then use set pen hsv because we have that in 3.0ya but you would just input into set pen color to or something but hex codes are confusingyeah it would have to as thats what used for the inputs of blocks that use colorI think it would return hex code 2: what would this return? colors arent a datatype in scratch
but wouldnt that be really confusing? hex codes are very arbitrary
- cookieclickerer33
-
1000+ posts
Color at x: () y: () block.
(get [shade v] at x:() y:()::sensing)then use it with
(get [saturation v] at x:() y:()::sensing)
(get [brightness v] at x:() y:()::sensing)
set pen (shade v) to () ::pen
set pen (saturation v) to () ::pen
set pen (brightness v) to () ::pen
the “color” option would be renamed to “shade” because its confusing to have 2 set color blocks
- Discussion Forums
- » Suggestions
-
» Color at x: () y: () block.