Custom C blocks
(because custom hat blocks would probably be useless)
So C blocks are really useful, but a lot of people hate having to just re-create their conditional (c-block) functions as it makes code messier.
I've decided to create a post for this feature.
I hope ST reads this.
So I've been working out a way that it works.

define cblock etc
code here

Pretty simple? But how exactly do you create them?
Alright, so you create your new custom block, it has a define. and you put code inside the define, But how does it map out how the c-block will work?
Here's an example.

define repeat*2 (int32)
repeat (int32)
    // in here it'd assume ok this is a c block so we'll use this as part of the c block
end
repeat (int32)
   // same for here
end

So if you've seen what I'm going for (It uses c-blocks and other blocks that'd work with conditionals as the conditional) then you might want to go ahead and support!
Now, about my other thing (custom hats) This feature isn't as great, but it is basically just a custom event being pulled, So for example if I have a 3 click event on an object, I can create a custom hat for that.
It'd use event combining and I don't know how exactly it would look in scratchblocks, that's beyond the BB plugin's feature.
Thanks for supporting in advance!

dhdguysg wrote:

Hello again!
As you saw my last post about pen blocks maybe, I was getting good support, I hope those blocks will come to life, Anyways, Lets get to the subject
I have been looking threw obsolete blocks, Some dont have workarounds and they are c blocks or something,
Heres an example of a custom c block define and everything

Scratch C block definers+c block examples

define c block while <stuff :: custom-arg> :: custom hat
Scratch Code [repeat until <not <stuff :: custom-arg>>] //Experimental block for custom code. there's an easier way to make c blocks in the next explanation
//So it asks you to insert scratchblocks code that you'd do in a post inside the experimental block saying: scratch code

when gf clicked
while <mouse down?> :: cstart custom
say [HoodelHoe!]
end :: cend custom

That was pretty easy right??
Here's the easier way to set behavior the same way i did up there..

define c block while <stuff :: custom-arg> :: custom hat
repeat until <not <stuff :: custom-arg>> :: cstart control
end :: cend control
when gf clicked
while <mouse down?> :: cstart custom
say [Easier way!]
end :: cend custom

Well that was easy, Now to show you hat blocks, This is also easy
The red flag is a sprite ingame

define hat block When red flag clicked :: custom hat //This code is inside the red flag
if <<mouse down?> and <touching [mouse pointer v]?>>
Code below hat :: grey //This is not in the actual code, it will just run anything below if this statement is true..
end

When red flag clicked :: custom hat
say [I'm clicked!] for (2) secs

I hope you will support this! Ask me anything but before you ask look if i answered the question already!

...

HOWING wrote:

dhdguysg wrote:

Hello again!
As you saw my last post about pen blocks maybe, I was getting good support, I hope those blocks will come to life, Anyways, Lets get to the subject
I have been looking threw obsolete blocks, Some dont have workarounds and they are c blocks or something,
Heres an example of a custom c block define and everything

Scratch C block definers+c block examples

define c block while <stuff :: custom-arg> :: custom hat
Scratch Code [repeat until <not <stuff :: custom-arg>>] //Experimental block for custom code. there's an easier way to make c blocks in the next explanation
//So it asks you to insert scratchblocks code that you'd do in a post inside the experimental block saying: scratch code

when gf clicked
while <mouse down?> :: cstart custom
say [HoodelHoe!]
end :: cend custom

That was pretty easy right??
Here's the easier way to set behavior the same way i did up there..

define c block while <stuff :: custom-arg> :: custom hat
repeat until <not <stuff :: custom-arg>> :: cstart control
end :: cend control
when gf clicked
while <mouse down?> :: cstart custom
say [Easier way!]
end :: cend custom

Well that was easy, Now to show you hat blocks, This is also easy
The red flag is a sprite ingame

define hat block When red flag clicked :: custom hat //This code is inside the red flag
if <<mouse down?> and <touching [mouse pointer v]?>>
Code below hat :: grey //This is not in the actual code, it will just run anything below if this statement is true..
end

When red flag clicked :: custom hat
say [I'm clicked!] for (2) secs

I hope you will support this! Ask me anything but before you ask look if i answered the question already!

Support? I'm not 100% sure.
Also, you could use this:

...

Instead of the grey block “Code below hat”.

HOWING wrote:

What block will we use to run the c-block when the condition is true?

define c block Ex (stuff)
repeat until <not <stuff :: custom-arg>>
    ... :: grey
end

//And your stuff
when green flag clicked
Ex (mouse down?) :: cstart custom
  ... :: grey //So you'd use the block you created to run if the condition is true, If it wouldnt be true it'd skip the block
end :: cend custom

while ([condition] :: custom-arg) {[stack1] :: custom-arg} :: custom-arg
//would become
while () :: custom-arg cstart
end
//the definition:
repeat until <not<condition :: custom-arg>>
stack1 :: custom-arg
end

Cyoce wrote:

Support. Here's how the custom c-blocks could be created:
Just like the “add ___ input” under options, you could have an “add stack” option.
For example, for making a “while” block:

while ([condition] :: custom-arg) {[stack1] :: custom-arg} :: custom-arg
//would become
while () :: custom-arg cstart
end
//the definition:
repeat until <not<condition :: custom-arg>>
stack1 :: custom-arg
end

Similarly, you could have “add else”. This would add an else loop.
Couldn’t represent that properly because the “define” formatting is finicky.

TehCow wrote:

Umm… Code Blocks? What kind of code would we be dealing with? I hope the ST doesn't have to Invent a whole new language for this

TehCow wrote:

Umm… Code Blocks? What kind of code would we be dealing with? I hope the ST doesn't have to Invent a whole new language for this

when gf clicked
forever
wait until <>
...
end

cwrivera99 wrote:

I support the c-loops thing, but there is a workaround for the hat blocks-

when gf clicked
forever
wait until <>
...
end

Cyoce wrote:

Support. Here's how the custom c-blocks could be created:
Just like the “add ___ input” under options, you could have an “add stack” option.
For example, for making a “while” block:

while ([condition] :: custom-arg) {[stack1] :: custom-arg} :: custom-arg
//would become
while () :: custom-arg cstart
end
//the definition:
repeat until <not<condition :: custom-arg>>
stack1 :: custom-arg
end

Similarly, you could have “add else”. This would add an else loop.
Couldn’t represent that properly because the “define” formatting is finicky.

while (mouse down?) :: custom cstart
...
else :: custom
...
end :: custom cned