We have ‘Username’ block in Sensing, like that I ask them to add ‘Profile picture’ block

(Username)

(Profile picture)

Thank You
PenquinCode

Hey there! What does this block do? Show the PFP of the specified user (or you?)

Your profile picture, reported as an image (costumes and backdrops are also images)

This block takes someone's profile picture

MDCCCLXVII wrote:

Your profile picture, reported as an image (costumes and backdrops are also images)

This would need a whole new block type though as there's no block that has an output of an image.

fdreerf wrote:

MDCCCLXVII wrote:

Your profile picture, reported as an image (costumes and backdrops are also images)

This would need a whole new block type though as there's no block that has an output of an image.

But they can do it know?

MDCCCLXVII wrote:

Your profile picture, reported as an image (costumes and backdrops are also images)

Oh… then, that would be very hard to implement, especially for GIFs, it will also take up alot of kilobytes for images that have a LOT of kilobytes. It would technically make the Scratch Editor lag trying to process too much bytes of a single PFP.

fdreerf wrote:

MDCCCLXVII wrote:

Your profile picture, reported as an image (costumes and backdrops are also images)

This would need a whole new block type though as there's no block that has an output of an image.

^ This. And then we would need a whole new set of blocks to deal with this new type of variable, all because of one block that very few people would use IMO. No support

the2000 wrote:

fdreerf wrote:

MDCCCLXVII wrote:

Your profile picture, reported as an image (costumes and backdrops are also images)

This would need a whole new block type though as there's no block that has an output of an image.

^ This. And then we would need a whole new set of blocks to deal with this new type of variable, all because of one block that very few people would use IMO. No support

But if it is there it would be nise

PenquinCode wrote:

the2000 wrote:

fdreerf wrote:

MDCCCLXVII wrote:

Your profile picture, reported as an image (costumes and backdrops are also images)

This would need a whole new block type though as there's no block that has an output of an image.

^ This. And then we would need a whole new set of blocks to deal with this new type of variable, all because of one block that very few people would use IMO. No support

But if it is there it would be nise

There are still gonna be very few people who will use this block anyway, this is like an extension from Scratch Lab but worse. No I don't hate the Scratch Lab stuff, I actually like it.

If we get the username's profile picture it would be helpfull for many games

Sorry, if we can't have blocks that return lists or functions (which isn't necessarily a bad thing), I see no reason why we should have a block that returns an image. Plus..

((profile picture :: sensing) + (username)) // what the heck does this do?

Ok. Now I have class meet u later

PenquinCode wrote:

If we get the username's profile picture it would be helpfull for many games

Any proof that it WOULD be good? I don't find any purpose for this.

Maybe this would be a good idea for Snap! actually, since that can store images into variables. The only problem is that Snap! also has no profile pictures (outside of the forums which is a result of them using Discourse) ._.

gosoccerboy5 wrote:

((profile picture :: sensing) + (username)) // what the heck does this do?

I think it'll just show the PFP then the username, however the text should be in the middle of the PFP when it's loaded.

]

CARTOONPFP222111 wrote:

gosoccerboy5 wrote:

((profile picture :: sensing) + (username)) // what the heck does this do?

I think it'll just show the PFP then the username, however the text should be in the middle of the PFP when it's loaded.

That's not what the “()+()” reporter does or would make sense to do. However, the “join()()” reporter may make sense in this scenario.

I do not support this idea because this would take a lot of time to implement and doesn't have much use.

sportfan999 wrote:

]

CARTOONPFP222111 wrote:

gosoccerboy5 wrote:

((profile picture :: sensing) + (username)) // what the heck does this do?

I think it'll just show the PFP then the username, however the text should be in the middle of the PFP when it's loaded.

That's not what the “()+()” reporter does or would make sense to do. However, the “join()()” reporter may make sense in this scenario.

I do not support this idea because this would take a lot of time to implement and doesn't have much use.

Yes, I was referencing that…

CARTOONPFP222111 wrote:

PenquinCode wrote:

If we get the username's profile picture it would be helpfull for many games

Any proof that it WOULD be good? I don't find any purpose for this.

If the block is there I would given proof as a game

gosoccerboy5 wrote:

Sorry, if we can't have blocks that return lists or functions (which isn't necessarily a bad thing), I see no reason why we should have a block that returns an image. Plus..

((profile picture :: sensing) + (username)) // what the heck does this do?

Or we can change the block type like this

set profile picture to [...]