samq64 wrote:

p-p-p-p-p-p-p-p-p-p- wrote:

I support. I can understand that there is an workaround, but new scratchers wouldn't know how to make this. Also, people are talking about how this could be implemented in cloud pictures. I understand the worry, but there is a report button for that. . This would also be useful for camera memory non-cloud.

Support! This would be realy helpful for OS projects to take screenshots, custom wallpapers BMP export and much more!

There is no way you can fit a good photo of someone (probably about 1,000,000 characters) onto a single cloud variable (256 characters) it's impossible. Even using all 10 cloud variables (2,560 characters) is impossible. You could fit a very low resolution photo (16×16) onto a cloud variable, but the person's face wouldn't be recognizable. Plus the person would have to stay still a while. And then you can always report the project. And if you're still worried about it deny camara access! (that's what I would do.)

All I'm saying is “They could save someone's picture in the cloud.” Is not a good reason not to implant this.

mazzadoobry wrote:

samq64 wrote:

p-p-p-p-p-p-p-p-p-p- wrote:

I support. I can understand that there is an workaround, but new scratchers wouldn't know how to make this. Also, people are talking about how this could be implemented in cloud pictures. I understand the worry, but there is a report button for that. . This would also be useful for camera memory non-cloud.

Support! This would be realy helpful for OS projects to take screenshots, custom wallpapers BMP export and much more!

There is no way you can fit a good photo of someone (probably about 1,000,000 characters) onto a single cloud variable (256 characters) it's impossible. Even using all 10 cloud variables (2,560 characters) is impossible. You could fit a very low resolution photo (16×16) onto a cloud variable, but the person's face wouldn't be recognizable. Plus the person would have to stay still a while. And then you can always report the project. And if you're still worried about it deny camara access! (that's what I would do.)

All I'm saying is “They could save someone's picture in the cloud.” Is not a good reason not to implant this.

First of all, there is a way to increase a cloud variable's length to 286 characters. See @KrufferWasTaken's project on how he did that. Also, in Massively Multiplayer Online Games on scratch, they break up values to send to the cloud. They send values of 256 at a time. This way, let's say that there were 512 characters to send. First time the system will send the first 256, then the second 256. Although it is not very efficient, it can still work. There is also another way I haven't tested but probably will work. It has a very easy way of storing stuff into a list and saving it.

<touching darkness [ valuev] ?>
<touching brightness [ valuev] ?>
<touching color [ valuev] ?>

shekspar wrote:

support because it would be useful when I make my own version of Conway's game of life.
but there would have to be a

<touching darkness [ valuev] ?>
<touching brightness [ valuev] ?>
<touching color [ valuev] ?>

Raihan142857 wrote:

shekspar wrote:

support because it would be useful when I make my own version of Conway's game of life.
but there would have to be a

<touching darkness [ valuev] ?>
<touching brightness [ valuev] ?>
<touching color [ valuev] ?>

Maybe it should return a hex code since that's definitely not the way to go.

<touching color [#ffffff] ?>

<touching color [#000000] ?>

(colour v) of colour I'm touching :: reporter sensing
(saturation v) of colour I'm touching :: reporter sensing
(brightness v) of colour I'm touching :: reporter sensing

linearlemur wrote:

How about this:

(colour v) of colour I'm touching :: reporter sensing
(saturation v) of colour I'm touching :: reporter sensing
(brightness v) of colour I'm touching :: reporter sensing

([color v] at x: (0) y: (0) :: sensing)
([saturation v] at x: (0) y: (0) :: sensing)
([brightness v] at x: (0) y: (0) :: sensing)
([color code v] at x: (0) y: (0) :: sensing)

-MyNewAccount- wrote:

would this return RGB or hex values?

go to x: (x position) y: (y position)
forever
if <touching color [color] ?> then
...::grey
end
end

qloakonscratch wrote:

No support, easily workaroundable.

Make a separate sprite and do this

go to x: (x position) y: (y position)
forever
if <touching color [color] ?> then
...::grey
end
end

set pen color to (color at x: (10) y: (20) :: sensing)

qloakonscratch wrote:

No support, easily workaroundable.

Make a separate sprite and do this

go to x: (x position) y: (y position)
forever
if <touching color [color] ?> then
...::grey
end
end

Maximouse wrote:

linearlemur wrote:

How about this:

(colour v) of colour I'm touching :: reporter sensing
(saturation v) of colour I'm touching :: reporter sensing
(brightness v) of colour I'm touching :: reporter sensing

I like the idea of a dropdown, but I think it should also have a hex code option (to be usable as an input to the other set pen color block) and should have x and y inputs instead of only detecting the color under the sprite (which one? – most sprites are larger than 1 pixel). Block examples:

([color v] at x: (0) y: (0) :: sensing)
([saturation v] at x: (0) y: (0) :: sensing)
([brightness v] at x: (0) y: (0) :: sensing)
([color code v] at x: (0) y: (0) :: sensing)

Wheatly_Scratcher wrote:

and would give you the number that you would use in the

set pen color to ()

to make that color.

mumu245 wrote:

Wheatly_Scratcher wrote:

and would give you the number that you would use in the

set pen color to ()

to make that color.

Maybe it could give hex? There is also saturation and lightness.

1132262 wrote:

External server means not cloud variables. You can communicate with the outside internet.
So yes, you could definitely store faces if the camera wasn't blocked.

Wheatly_Scratcher wrote:

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.

([color v] at x: () y: ())

(color at x: () y: ())

([color v] at x: () y: ())

([saturation v] at x: () y: ())

([brightness v] at x: () y: ())

([transparency v] at x: () y: ())