generate input first#165
Conversation
|
can confirm that it works and that other blocks are unaffected |
|
ok i just removed the warns cause it throws errors anyway so whats really the point |
|
This seems unsafe |
|
how |
|
gng it throws errors anyway how does it provide extra debugging info |
Errors doesn't include the block info. |
then you can view the scope tag when it breakpoints and see the block var
|
No that's stupid |
|
how |
|
Additionally this makes compiling a bit slower. There's a better way to do this if you're trying to make the dual block work |
|
how is it slower???? it did the exact same before but instead of doing reporter first it did stack first |
|
Compiled scripts are made of stacks not reporters You're making it preferable reporters first, which makes compilation slightly slower |
|
But again, there's a better way to do this |
|
its basically the same, plus it only applies when the thing is actually clicked so for actually running projects theres no difference |
|
Okay fine, but still, put the logs back. |
|
k fine but it'll be debug mode only |
Okay |
2 participants
ok sooo i noticed a thing where if it fails to generate a stack it attempts to generate a input
so i've switched it around so it will try to generate input first, and if it fails it will generate stack
why did i do this? ummm so dual block actually shows a bubble
also this does clear a todo to move a piece of code to the generate function
test somewhen