CraftedCart wrote:

danielhal wrote:

What's the point in this?

An example could be:
A project creates a string of text as a save/load code
The project writes to the clipboard, much nicer and sleeker than displaying a list and asking the user to RClick and Export

K

Good idea.
Also, you need to do

(clipboard :: sensing) // (clipboard :: sensing)

Edit 2021: No. Just… ignore this post.

mybearworld wrote:

Good idea.
Also, you need to do

(clipboard :: sensing) // (clipboard :: sensing)

No this isn't a necropost because you made a duplicate.

I think it would work so long as there were these implementations:

1: The clipboard can only copy from a list
2: There should be a clipboard chart (similar to the cloud variable history)
3: On project load, there should be a message that says “this project can access the clipboard”
4: If a user decides to use the project, if clipboard wants to be used, there should be a message "do you want to copy to your clipboard“
5: It can only copy 100 chars max.
6: The project should not depend on it. IE, if a project can't ”write“ to the clipboard. ”write" refers to, being able to change parts of a computer system software.

No support for the (personal stuff)

clipboard

reporter, but support for the copier with restrictions:

[removed]

bump

Support, this would make save codes much easier for mobile users.

Support. As said there should be a warning before or simply ask when games try to do something with clipboard

Suport , this would make it easyer to do it on molile as iv tryed to do it while my computer was broken and iit was a pain

The “copy val to clipboard” should have a filter run on it.

I support this, but in a different way. I support copying scripts, costumes, and sprites in the editor to the clipboard instead of having to use the backpack for *easier* use. I also support the “copy to clipboard” block but

han614698 wrote:

^^ with restrictions, such as a bad word filter otherwise this block could be used to display inappropriate text on someone's screen even though they can report it.

EDIT: Didn't see this. Sorry!

han614698 wrote:

The “copy val to clipboard” should have a filter run on it.

Here are blocks that would be nice:

add [] to clipboard :: sensing

clear clipboard :: sensing // Not sure about this one...

paste clipboard :: sensing

(clipboard :: sensing)

(Oops necropost, sorry.) Actually nevermind, necroposting doesn't really exist on the suggestion forums.

This seems a great idea! It would make many projects that rely on lists for exporting so much cleaner.

I do think that restrictions are necessary, but not to the extent of creating a popup on your screen (Maybe have that as an option in settings? Maybe ask when the project starts instead of whenever it asks to copy? IDK what the ideal solution would be but a popup like the one above seems over the top)

Andygun11 wrote:

Here are blocks that would be nice:

add [] to clipboard :: sensing

clear clipboard :: sensing // Not sure about this one...

paste clipboard :: sensing

(clipboard :: sensing)

1. Should probably be set clipboard, not add.
2. To stop people maliciously clearing the clipboard maybe this should only work if the content on the clipboard was copied by the project that is trying to clear it.
3. What input would it paste to? I don't think this is necessary as it would have no use

AHypnoman wrote:

2. To stop people maliciously clearing the clipboard maybe this should only work if the content on the clipboard was copied by the project that is trying to clear it.

how do you maliciously clear the clipboard lmao?
do you put all your personal info there or smthn?

HeliosTheSuperior wrote:

AHypnoman wrote:

2. To stop people maliciously clearing the clipboard maybe this should only work if the content on the clipboard was copied by the project that is trying to clear it.

how do you maliciously clear the clipboard lmao?
do you put all your personal info there or smthn?

No but people can put a repeating script in their projects that clears the clipboard - also, it was not an idea of mine that it could be done maliciously.

when clipboard pasted :: events :: hat

Maybe this, too?

SciPiDilts wrote:

when clipboard pasted :: events :: hat

Maybe this, too?

What would this actually detect?

AHypnoman wrote:

SciPiDilts wrote:

when clipboard pasted :: events :: hat

Maybe this, too?

What would this actually detect?

It would detect when you press ctrl+v.

SciPiDilts wrote:

AHypnoman wrote:

SciPiDilts wrote:

when clipboard pasted :: events :: hat

Maybe this, too?

What would this actually detect?

It would detect when you press ctrl+v.

Or whenever you use the

paste clipboard :: sensing

block too?