I think that you should be able to insert scratchblock code in 2.0, like a text-based code...
Offline
Offline
I support.
Offline
Agentpieface wrote:
would this even be possible? I highly doubt it
Maybe in 2.1?
Offline
I support, but it probably won't happen until 2.1. However, the plugin isn't exactly sound. For example:
when [Sprite1] clicked set [ans v] to ([slider v] sensor value) stop all pinks"when ____ clicked" doesn't render properly, "([slider v] sensor value)" isn't supported, and "stop all pinks" doesn't exist. Just to name a few bugs.
Offline
coolhogs wrote:
Agentpieface wrote:
would this even be possible? I highly doubt it
Everything is possible, it's just a little more complex, sometimes.
no
i dont think this is possible anyway
Offline
Agentpieface wrote:
coolhogs wrote:
Agentpieface wrote:
would this even be possible? I highly doubt it
Everything is possible, it's just a little more complex, sometimes.
no
i dont think this is possible anyway
It's possible, everything is if you're a good enough programmer. This would just be a lot of hard work, which isn't really necessary in my opinion.
Offline
RedRocker227 wrote:
Agentpieface wrote:
coolhogs wrote:
Everything is possible, it's just a little more complex, sometimes.
no
i dont think this is possible anywayIt's possible, everything is if you're a good enough programmer. This would just be a lot of hard work, which isn't really necessary in my opinion.
I wouldnt use it anyway but I can think of some people who this would come in handy for.
Last edited by Mokat (2012-07-18 09:24:38)
Offline
360-International wrote:
I support, but it probably won't happen until 2.1. However, the plugin isn't exactly sound. For example:
when [Sprite1 v] clicked set [ans v] to ([slider v] sensor value) stop all pinks"when ____ clicked" doesn't render properly, "([slider v] sensor value)" isn't supported, and "stop all pinks" doesn't exist. Just to name a few bugs.
I hope this does get implemented when the plugin bugs are fixed.![]()
Fixed
Offline
joletole wrote:
360-International wrote:
I support, but it probably won't happen until 2.1. However, the plugin isn't exactly sound. For example:
when [Sprite1 v] clicked set [ans v] to ([slider v] sensor value) stop all pinks"when ____ clicked" doesn't render properly, "([slider v] sensor value)" isn't supported, and "stop all pinks" doesn't exist. Just to name a few bugs.
I hope this does get implemented when the plugin bugs are fixed.![]()
Fixed
Not really, if you look in Scratch the "when ___ clicked" block doesn't look like that.
Offline