0037318 wrote:

FuturePr0 wrote:

When you say that scratch having no debugging tools is bad, it's actually good, scratch hasn't added them because then you don't feel like you are good at coding if you got loads and loads and loads of messages saying the code is wrong, plus it's not their fault, it is more likely going to be yours if the code doesn't work the way you wanted it to.

Debugging tools are meant to help you. Not fix the problem for you. they can help you avoid some really infamous errors, like the undefined block. It is not really anyone's fault that this happens, as programmers always have to debug their code. However, debugging tools make this process a lot faster and help everyone.

Sorry I meant to say that if you added debugging tools I meant they would make you feel like a bad coder and not a good one*

Note that, as far as debugging is concerned, I've always found that just using a list called “Log” is enough.

You could also use the timer for a sort of timestamp if you weren't using it for something else – but honestly, I've never run into a timing-related issue in Scratch (with the possible exception of cloud variable stuff), so I have to wonder what it is you're doing that even needs timestamps.

TheMonsterOfTheDeep wrote:

Note that, as far as debugging is concerned, I've always found that just using a list called “Log” is enough.

You could also use the timer for a sort of timestamp if you weren't using it for something else – but honestly, I've never run into a timing-related issue in Scratch (with the possible exception of cloud variable stuff), so I have to wonder what it is you're doing that even needs timestamps.

A list called log would be enough for small projects. But projects with many sprites and scripts require more. Any project with multiple sprites would benefit from timestamps due to the almost unpredictable order of when things will happen. Since all of the sprites operate asynchronously, knowing exactly when things happen in relation to other things can be very helpful. Knowing how long things take to do can also be helpful. Also, if somebody runs into a bug in your project, you can tell them to export the log and send it to you. You can then examine exactly what happened and when so that you can fix it.

But, I mean, can you give an example? I've very literally, in my 6-ish years of using Scratch, never run into an issue related to timing.

0037318 wrote:

TheMonsterOfTheDeep wrote:

Note that, as far as debugging is concerned, I've always found that just using a list called “Log” is enough.

You could also use the timer for a sort of timestamp if you weren't using it for something else – but honestly, I've never run into a timing-related issue in Scratch (with the possible exception of cloud variable stuff), so I have to wonder what it is you're doing that even needs timestamps.

A list called log would be enough for small projects. But projects with many sprites and scripts require more. Any project with multiple sprites would benefit from timestamps due to the almost unpredictable order of when things will happen. Since all of the sprites operate asynchronously, knowing exactly when things happen in relation to other things can be very helpful. Knowing how long things take to do can also be helpful. Also, if somebody runs into a bug in your project, you can tell them to export the log and send it to you. You can then examine exactly what happened and when so that you can fix it.

What's wrong with using the timer for timestamps?


also…
In your signature, the final block that you say Scratch needs can be done

<<(thing) > (otherthing)> or <(thing) = (otherthing)>>

/offtopic

Wahsp wrote:

also…
In your signature, the final block that you say Scratch needs can be done

<<(thing) > (otherthing)> or <(thing) = (otherthing)>>

/offtopic

Sorry to continue the offtopic, but the better workaround for e.g. A less than or equal to B is

<not <(A) > (B)>>

Wahsp wrote:

0037318 wrote:

TheMonsterOfTheDeep wrote:

Note that, as far as debugging is concerned, I've always found that just using a list called “Log” is enough.

You could also use the timer for a sort of timestamp if you weren't using it for something else – but honestly, I've never run into a timing-related issue in Scratch (with the possible exception of cloud variable stuff), so I have to wonder what it is you're doing that even needs timestamps.

A list called log would be enough for small projects. But projects with many sprites and scripts require more. Any project with multiple sprites would benefit from timestamps due to the almost unpredictable order of when things will happen. Since all of the sprites operate asynchronously, knowing exactly when things happen in relation to other things can be very helpful. Knowing how long things take to do can also be helpful. Also, if somebody runs into a bug in your project, you can tell them to export the log and send it to you. You can then examine exactly what happened and when so that you can fix it.

What's wrong with using the timer for timestamps?


also…
In your signature, the final block that you say Scratch needs can be done

<<(thing) > (otherthing)> or <(thing) = (otherthing)>>

/offtopic

Just because something does exist that would partially satisfy my needs does not mean that my suggestion is completely invalid. That seems to be a common opinion on this forum.

pretty much all the other stuff in the OP would make too small of a suggestion, so I will not make any more.

bumping because this is important

It can be hard when you don't know how to do the coding well…