DocumentInQuestion.png This page or section is in question as to whether it is useful or not. You can discuss whether you think it should be deleted or not on its talk page. (November 2019)
Reason: Not that notable enough to be mentioned on its own article, can be merged with other sensing articles
DocumentInQuestion.png It has been suggested that this page's contents be merged with the page Key () Pressed? (block). You can discuss this on the page's talk page. (November 2019)
Document stub.png This article is a stub. It may be incomplete, unfinished, or have missing parts/sections. If the article can be expanded, please do so! There may be suggestions on its talk page. (August 2022)

Additional keys are keys that are not normally accessible through key sensing block drop-down menus, but are detectable using workarounds. Some of the keys involve punctuation and the enter button.

Methods

Here are the following methods to have additional keys:

Method 1

One common way of accessing the keys is by custom inputs, such as utilizing the join block:

<key (join [enter] []) pressed? >

Method 2

Another method is setting a variable to a key, and for the code to check if that key was clicked.

set [key v] to [] // can be any key except Ctrl, Command, Alt, Option, Shift, and Tab
forever
if <key (key) pressed?> then
. . .
end

Method 3

Another method of obtaining additional keys is by editing the project JSON file to point the input to a new value with a text editor, specifying an arbitrary value instead of one of the drop-down options. This can be used to make blocks like this:

<key (+ v) pressed>

To learn more about JSON and editing projects, read this article.

See Also

Cookies help us deliver our services. By using our services, you agree to our use of cookies.