when green flag clicked
ask [Is a debugger coming out soon?] and wait
if <(answer) = [ no]> then
   say [nooooooooooooo]
   stop [the universe]
else:
   say [yyyaaayyy!]
   celebrate
end

IronBit_Studios wrote:

No support; while this is great, the ST will take forever to do this.
While you're at it, this place is great for issues like this.

capybara wrote:

IronBit_Studios wrote:

No support; while this is great, the ST will take forever to do this.
While you're at it, this place is great for issues like this.

Is that an excuse for making one?

Also: finally, someone who has played the Portal games!
Best. Games. Ever.

capybara wrote:

IronBit_Studios wrote:

No support; while this is great, the ST will take forever to do this.
While you're at it, this place is great for issues like this.

Is that an excuse for making one?

capybara wrote:

Also: finally, someone who has played the Portal games!
Best. Games. Ever.

mrbobbygreathead wrote:

Yes that is an excuse.
To make your siggy, click here

mrbobbygreathead wrote:

Another way is to scroll to the bottom of the discussion home page and click “change your signature”.

DaSpudLord wrote:

There used to be a single-stepping mode in 1.4, I think. We really need to bring it back- I also have projects that I have either quit or are currently sitting in my unshared projects folder simply because I can't diagnose a bug with them.

DaSpudLord wrote:

There used to be a single-stepping mode in 1.4, I think. We really need to bring it back- I also have projects that I have either quit or are currently sitting in my unshared projects folder simply because I can't diagnose a bug with them.

helloandgoodbye9 wrote:

DaSpudLord wrote:

There used to be a single-stepping mode in 1.4, I think. We really need to bring it back- I also have projects that I have either quit or are currently sitting in my unshared projects folder simply because I can't diagnose a bug with them.

I heard about that, and that would be very useful, but a little slow for big projects. If you really need a debugger, program one.
Semi-support.

capybara wrote:

helloandgoodbye9 wrote:

DaSpudLord wrote:

There used to be a single-stepping mode in 1.4, I think. We really need to bring it back- I also have projects that I have either quit or are currently sitting in my unshared projects folder simply because I can't diagnose a bug with them.

I heard about that, and that would be very useful, but a little slow for big projects. If you really need a debugger, program one.
Semi-support.

WHAT? That doesn't even make sense! I can't program this on scratch, it has to be a part of scratch! I would have to put a wait until space pressed block in between EVERY other block, and then take them out a again for testing!

helloandgoodbye9 wrote:

Congrats! You just programed one . I would do it a different way by logging each command, though . Its hard, but gives you more control and can be better for bigger projects. Like I said, I would give Semi-Support. Its could be helpful, but a haven't encountered anything that I need this for.

capybara wrote:

helloandgoodbye9 wrote:

Congrats! You just programed one . I would do it a different way by logging each command, though . Its hard, but gives you more control and can be better for bigger projects. Like I said, I would give Semi-Support. Its could be helpful, but a haven't encountered anything that I need this for.

Well that's me outsmarted, that is.

helloandgoodbye9 wrote:

capybara wrote:

helloandgoodbye9 wrote:

Congrats! You just programed one . I would do it a different way by logging each command, though . Its hard, but gives you more control and can be better for bigger projects. Like I said, I would give Semi-Support. Its could be helpful, but a haven't encountered anything that I need this for.

Well that's me outsmarted, that is.

Like I said, it is hard to make but gives you more control. I have never needed this, but since this is a cool idea, I'm giving Semi-Support.

capybara wrote:

helloandgoodbye9 wrote:

capybara wrote:

helloandgoodbye9 wrote:

Congrats! You just programed one . I would do it a different way by logging each command, though . Its hard, but gives you more control and can be better for bigger projects. Like I said, I would give Semi-Support. Its could be helpful, but a haven't encountered anything that I need this for.

Well that's me outsmarted, that is.

Like I said, it is hard to make but gives you more control. I have never needed this, but since this is a cool idea, I'm giving Semi-Support.

Thanks! Maybe I'll try it. What do you mean by “logging”?

define log [stuff]
add (stuff) to [log v]
wait (0.1) secs

when gf clicked
log [start]
move (10) steps
log [move 10]
...

the_extreme_coder wrote:

i support this and so dos this person


https://www.google.com.au/imgres?imgurl=http://science-all.com/images/mother-teresa/mother-teresa-02.jpg&imgrefurl=http://science-all.com/files/mother-teresa.html&h=1033&w=1213&tbnid=P1nP8gPJ1fsnmM:&docid=jbY0Z8T692aLTM&ei=AnH4Vq22JMui0gTOu7y4Ag&tbm=isch&client=safari&ved=0ahUKEwitv5fThuLLAhVLkZQKHc4dDycQMwgyKAEwAQ

helloandgoodbye9 wrote:

capybara wrote:

helloandgoodbye9 wrote:

capybara wrote:

helloandgoodbye9 wrote:

Congrats! You just programed one . I would do it a different way by logging each command, though . Its hard, but gives you more control and can be better for bigger projects. Like I said, I would give Semi-Support. Its could be helpful, but a haven't encountered anything that I need this for.

Well that's me outsmarted, that is.

Like I said, it is hard to make but gives you more control. I have never needed this, but since this is a cool idea, I'm giving Semi-Support.

Thanks! Maybe I'll try it. What do you mean by “logging”?

Something like this.

define log [stuff]
add (stuff) to [log v]
wait (0.1) secs

when gf clicked
log [start]
move (10) steps
log [move 10]
...

That way, when it breaks, you stop it and check the log. Whatever was last is most likely the thing that broke it.