Steve0Greatness wrote:

snip]

Thanks

This would probably be really easy to implement too, they could do what the Khan Academy devs did

How would this work consider that there are not syntax errors on scratch? You can easily find bugs in your projects.

dertermenter wrote:

How would this work consider that there are not syntax errors on scratch? You can easily find bugs in your projects.

That's narrow minded thinking.
No syntax errors maybe, but Scratch doesn't give you a magical pathway to making a great game. This would help you know how to fix a bug, especially in bigger projects. Bugs do exist when making a game, regardless of the language or interface.

dertermenter wrote:

How would this work consider that there are not syntax errors on scratch? You can easily find bugs in your projects.

Read the OP.

ninjaMAR wrote:

The editor would have a new block which would take its input and log it to the console.

the2000 wrote:

dertermenter wrote:

How would this work consider that there are not syntax errors on scratch? You can easily find bugs in your projects.

Read the OP.

ninjaMAR wrote:

The editor would have a new block which would take its input and log it to the console.

Sorry, I don't really get this suggestion to much.

Does it send a message in text based scratch to the console and that checks for syntax errors?

Also, relax G, I don't need an angry emoji and big bold letters enforced into my face

dertermenter wrote:

the2000 wrote:

Read the OP.

ninjaMAR wrote:

The editor would have a new block which would take its input and log it to the console.

Sorry, I don't really get this suggestion to much.

Does it send a message in text based scratch to the console and that checks for syntax errors?

Sorry, I don't usually have patience with people who ask questions that they would know the answer to if they just read the OP, especially if the OP is very concise.

I don't want to play 20 questions with Scratch suggestions, just read the OP. It doesn't have anything to do with syntax errors, it's just asking for a Scratch console window that you can print text to for your own debugging purposes.

the2000 wrote:

dertermenter wrote:

the2000 wrote:

Read the OP.

ninjaMAR wrote:

The editor would have a new block which would take its input and log it to the console.

Sorry, I don't really get this suggestion to much.

Does it send a message in text based scratch to the console and that checks for syntax errors?

Sorry, I don't usually have patience with people who ask questions that they would know the answer to if they just read the OP, especially if the OP is very concise.

I don't want to play 20 questions with Scratch suggestions, just read the OP. It doesn't have anything to do with syntax errors, it's just asking for a Scratch console window that you can print text to for your own debugging purposes.

IDK if that is snarky but if so, please stop, we all make mistakes
I read the OP, can I have a gold star

So would you have to do your own debugging? What is the point of that!

dertermenter wrote:

So would you have to do your own debugging? What is the point of that!

Because there are no syntax errors in Scratch? Most of programming is “doing your own debugging”, as you put it. I am currently developing a real game and building an engine from the ground up for it, and I have had to use “console.log” (print function in JavaScript) for debugging purposes many, many times. To answer your question, the point of doing your own debugging is that doing your own debugging is the point of programming.

the2000 wrote:

dertermenter wrote:

So would you have to do your own debugging? What is the point of that!

Because there are no syntax errors in Scratch? Most of programming is “doing your own debugging”, as you put it. I am currently developing a real game and building an engine from the ground up for it, and I have had to use “console.log” (print function in JavaScript) for debugging purposes many, many times. To answer your question, the point of doing your own debugging is that doing your own debugging is the point of programming.

You can do ur own debugging on scratch anyway


Gold star plez

dertermenter wrote:

the2000 wrote:

dertermenter wrote:

So would you have to do your own debugging? What is the point of that!

Because there are no syntax errors in Scratch? Most of programming is “doing your own debugging”, as you put it. I am currently developing a real game and building an engine from the ground up for it, and I have had to use “console.log” (print function in JavaScript) for debugging purposes many, many times. To answer your question, the point of doing your own debugging is that doing your own debugging is the point of programming.

You can do ur own debugging on scratch anyway

You're ignoring what he's saying! This would help with debugging is the point!

gosoccerboy5 wrote:

dertermenter wrote:

the2000 wrote:

dertermenter wrote:

So would you have to do your own debugging? What is the point of that!

Because there are no syntax errors in Scratch? Most of programming is “doing your own debugging”, as you put it. I am currently developing a real game and building an engine from the ground up for it, and I have had to use “console.log” (print function in JavaScript) for debugging purposes many, many times. To answer your question, the point of doing your own debugging is that doing your own debugging is the point of programming.

You can do ur own debugging on scratch anyway

You're ignoring what he's saying! This would help with debugging is the point!

There are not syntax errors in scratch

dertermenter wrote:

gosoccerboy5 wrote:

You're ignoring what he's saying! This would help with debugging is the point!

There are not syntax errors in scratch

A debug window also helps with semantic errors when the program does not run the way the designer wants it to.

gosoccerboy5 wrote:

dertermenter wrote:

You're ignoring what he's saying! This would help with debugging is the point!

There are not syntax errors in scratch

A debug window also helps with semantic errors when the program does not run the way the designer wants it to.
Would it

dertermenter wrote:

gosoccerboy5 wrote:

dertermenter wrote:

gosoccerboy5 wrote:

You're ignoring what he's saying! This would help with debugging is the point!

There are not syntax errors in scratch

A debug window also helps with semantic errors when the program does not run the way the designer wants it to.

Would it

Yes. “Hmm, this function isn't working the way I want it to. Maybe this math equation doesn't do what I think it should? Maybe this variable, which updates once every frame, is giving wrong values because I calculated it wrong somewhere else? I'll use the ‘log’ block to find out.”

dertermenter wrote:

gosoccerboy5 wrote:

dertermenter wrote:

gosoccerboy5 wrote:

You're ignoring what he's saying! This would help with debugging is the point!

There are not syntax errors in scratch

A debug window also helps with semantic errors when the program does not run the way the designer wants it to.

Would it

Yes. Speaking from personal experience, it's extremely helpful. A debug window is like a flashlight in a dark cave.

the2000 wrote:

dertermenter wrote:

gosoccerboy5 wrote:

dertermenter wrote:

gosoccerboy5 wrote:

You're ignoring what he's saying! This would help with debugging is the point!

There are not syntax errors in scratch

A debug window also helps with semantic errors when the program does not run the way the designer wants it to.

Would it

Yes. “Hmm, this function isn't working the way I want it to. Maybe this math equation doesn't do what I think it should? Maybe this variable, which updates once every frame, is giving wrong values because I calculated it wrong somewhere else? I'll use the ‘log’ block to find out.”

So you can run this block any time if you think there is a bug and checks it? Cool! This would be useful for debugging stuff where you don’t know what caused the bug in the first place.

Maybe rename this to “Log” or “Logger”, as it's only for prints/logs. By saying “logs”, it should probably be named “Logs”.
Meanwhile, just do this:

delete all of [Logs v] ::list // use to clear logs

add [meow meow meeeeowwwww] to [Logs v] // change meow to anything, prints to log

dertermenter wrote:

the2000 wrote:

dertermenter wrote:

gosoccerboy5 wrote:

dertermenter wrote:

gosoccerboy5 wrote:

You're ignoring what he's saying! This would help with debugging is the point!

There are not syntax errors in scratch

A debug window also helps with semantic errors when the program does not run the way the designer wants it to.

Would it

Yes. “Hmm, this function isn't working the way I want it to. Maybe this math equation doesn't do what I think it should? Maybe this variable, which updates once every frame, is giving wrong values because I calculated it wrong somewhere else? I'll use the ‘log’ block to find out.”

So you can run this block any time if you think there is a bug and checks it? Cool! This would be useful for debugging stuff where you don’t know what caused the bug in the first place.

Well, it's basically a print() statement. It adds whatever text to the log. This lets you check if things are outputting the right values, or if code is running at right times or not.

ninjaMAR wrote:

samq64 wrote:

I do this using lists, but this would be easier Simi-Support.

If you support you say support and why

They have the right to refrain from saying why they support; your response was unnecessary and spam.