Discuss Scratch

CodeComet6161
Scratcher
1000+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

Q: Is this a duplicate?
A: No. That topic (which I just bumped) is NOT the same as this topic. That topic is asking for a way to make separate custom reporters and booleans, without the use of creating a block. This suggestion is talking about… Well, read to find out.

Introduction

This suggestion is asking for a way to put reporters INSIDE booleans and other reporters and vice versa. With the current setting, attempting to do this will only create another slot.

Why do I want this?

There are a number of reasons I want this. Here are some, just to name a few.

1: Custom Logic Gates

What we want:
<> xor <>::custom boolean

The result:
<><> xor <>::custom

2: Trans-Programming Language Blocks (OK this is probably just me)

What we want:
input []::custom reporter

The result:
(input::custom) []::stack custom

The possibilities are just endless with this.

“No support, how are you supposed to toggle it?”

Simple. If you're editing text and you hit the reporter/boolean button, it'll be placed where the cursor is. If not, it'll place it normally.

Edit: I had to change the title so it could be distinguished.

Last edited by CodeComet6161 (Oct. 4, 2025 16:21:57)

mtaka4
Scratcher
500+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

I have no idea what you're suggesting
CodeComet6161
Scratcher
1000+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

mtaka4 wrote:

I have no idea what you're suggesting

CodeComet6161 wrote:

This suggestion is asking for a way to put reporters INSIDE booleans and other reporters and vice versa. With the current setting, attempting to do this will only create another slot.
CodeComet6161
Scratcher
1000+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

bump
nembence
Scratcher
500+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

Is it something like this?
define block with strange input <<> xor <>::custom>
...
block with strange input <xor:a> <xor:b> {
} xor: <> :: custom

Last edited by nembence (Oct. 8, 2025 22:16:10)

CodeComet6161
Scratcher
1000+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

nembence wrote:

Is it something like this?
define block with strange input <<> xor <>::custom>
...
block with strange input <xor:a> <xor:b> {
} xor: <> :: custom
Not the second one.
mtaka4
Scratcher
500+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

CodeComet6161 wrote:

mtaka4 wrote:

I have no idea what you're suggesting

CodeComet6161 wrote:

This suggestion is asking for a way to put reporters INSIDE booleans and other reporters and vice versa. With the current setting, attempting to do this will only create another slot.
Oh ok
CodeComet6161
Scratcher
1000+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

CodeComet6161 wrote:

bump
CodeComet6161
Scratcher
1000+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

CodeComet6161 wrote:

CodeComet6161 wrote:

bump
nembence
Scratcher
500+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

CodeComet6161 wrote:

nembence wrote:

Is it something like this?
define block with strange input <<> xor <>::custom>
...
block with strange input <xor:a> <xor:b> {
} xor: <> :: custom
Not the second one.
Then I don't know what you want
Custom block inputs are usually set outside of the custom block, but if the input also has its own inputs then it needs to send them out of the custom block before it can be set from the outside
CodeComet6161
Scratcher
1000+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

nembence wrote:

CodeComet6161 wrote:

nembence wrote:

Is it something like this?
define block with strange input <<> xor <>::custom>
...
block with strange input <xor:a> <xor:b> {
} xor: <> :: custom
Not the second one.
Then I don't know what you want
Custom block inputs are usually set outside of the custom block, but if the input also has its own inputs then it needs to send them out of the custom block before it can be set from the outside
DOES ANYONE ACTUALLY READ THE TITLE????

CodeComet6161 wrote:

mtaka4 wrote:

I have no idea what you're suggesting

CodeComet6161 wrote:

This suggestion is asking for a way to put reporters INSIDE booleans and other reporters and vice versa. With the current setting, attempting to do this will only create another slot.
nembence
Scratcher
500+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

CodeComet6161 wrote:

nembence wrote:

CodeComet6161 wrote:

Then I don't know what you want
Custom block inputs are usually set outside of the custom block, but if the input also has its own inputs then it needs to send them out of the custom block before it can be set from the outside
DOES ANYONE ACTUALLY READ THE TITLE????

CodeComet6161 wrote:

mtaka4 wrote:

I have no idea what you're suggesting

CodeComet6161 wrote:

This suggestion is asking for a way to put reporters INSIDE booleans and other reporters and vice versa. With the current setting, attempting to do this will only create another slot.
Yes but when you have something like this:
define block using the new (input [nested input]) feature
say (input (join [Hello] (answer)::operators))
Where does the result of the join block go then?

Last edited by nembence (Oct. 12, 2025 21:23:42)

CodeComet6161
Scratcher
1000+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

nembence wrote:

CodeComet6161 wrote:

nembence wrote:

CodeComet6161 wrote:

Then I don't know what you want
Custom block inputs are usually set outside of the custom block, but if the input also has its own inputs then it needs to send them out of the custom block before it can be set from the outside
DOES ANYONE ACTUALLY READ THE TITLE????

CodeComet6161 wrote:

mtaka4 wrote:

I have no idea what you're suggesting

CodeComet6161 wrote:

This suggestion is asking for a way to put reporters INSIDE booleans and other reporters and vice versa. With the current setting, attempting to do this will only create another slot.
Yes but when you have something like this:
define block using the new (input [nested input]) feature
say (input (join [Hello] (answer)::operators))
Where does the result of the join block go then?
Hello0
MiaELamanna
Scratcher
35 posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

Bump
CodeComet6161
Scratcher
1000+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

bump
TimothyLawyer
Scratcher
1000+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

I don't understand.

CodeComet6161 wrote:

This suggestion is asking for a way to put reporters INSIDE booleans and other reporters and vice versa.
Can you say this in different words?
d016
Scratcher
99 posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

So do you mean if you have

define cool block (text or number)

you can change it into

define cool block <text or number \(but it's now a boolean!\)>
?

Last edited by d016 (Nov. 5, 2025 19:08:20)

CodeComet6161
Scratcher
1000+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

d016 wrote:

So do you mean if you have

define cool block (text or number)

you can change it into

define cool block <text or number \(but it's now a boolean!\)>
?

d016 wrote:

So do you mean if you have

define cool block (text or number)

you can change it into

define cool block <text or number \(but it's now a boolean!\)>
?
define text ( reporter input(reporter input::custom))::custom
dizzyboy42
Scratcher
500+ posts

Better Custom Blocks THE SECOND SUGGESTION [READ BEFORE REPLYING]

d016 wrote:

So do you mean if you have

define cool block (text or number)

you can change it into

define cool block <text or number \(but it's now a boolean!\)>
?
no they mean
define (input [input2])
run (input [input2]) ::fb681

Powered by DjangoBB