I had 100th reply in my hands and man just snatched it :(
joke btw
OK.. OK
You understand what I meant to say...
v1.0.0 Released
Changes:
- Bugs have been corrected and patched.
- Some code has been cleaned and simplified.
- Implemented and blocks data successfully.
Thanks to:
- @ScratchModification for noticing and making these changes!
(C) 2022 ScratchModification
can v1.0.1
have my block in it? I'm implementing the code right now.
I'm not sure. Since my block can detect errors I don't think that will be necessary
?
I mean, if you want to convert a string that cannot be converted:
no like, how does "is (block) a block" block have to do with errors?
If that block errors, then that means the string isn't a valid block!
but how would we use this if it doesn't report true or false?
Well, since sometimes takes time to convert to a block, I recommend you to safely try converting the string, but if it errors then that mean it isn't a valid block.
Do you understand what I mean?
Yeah, but it would just be easier for people to use [scratchblocks] is {} a block?[/scratchblocks]
*in my opinion
My priority now is performance...
Checking a block if it's valid implies converting a string and checking. If it's valid then you have to convert the same string again.
But if you only convert the string directly using safely try, then you don't have to convert it twice!
all it literally does is check to see if (text) exists in (bh data).
No conversions.
Yes, I know.
But check the example again, as can you see the block checks if the text I entered is in BC data
Unable to convert ... to block
means that this block have not been mapped.
And I noticed in your project that you are checking a whole command (not only a text):
You can simply do this:
Fine...
Hope I helped you
You did, and I appreciate that.
I just wanted to have one of my blocks in something people will actually use.
v1.0.1 Released
Changes:
- List reported by is now not linked to the original one.
- Conversions now supports variadic inputs in , , and blocks.
- Bug with solved.
- This version now supports Snap! version
7.3.0
Thanks to:
- @ScratchModification for noticing and making these changes!
(C) 2022 ScratchModification