So basically, my suggestion is to tell you what is happening during the project.
So basically this http://prnt.sc/a61mvt .

Or

TheScratchHobbiest wrote:

TheScratchHobbiest wrote:

Thanks to TheScratchHobbiest!

Perhaps this would be useful if the log were configurable, so that you could decide what you want to see in the log?

And also the log would have to be toggle-able of course right?

liam48D wrote:

Perhaps this would be useful if the log were configurable, so that you could decide what you want to see in the log?

And also the log would have to be toggle-able of course right?

Yes, it would ofcourse be toggle-able(you can select wether to have it or not.)

support

fredfish10 wrote:

support

Reason?

Support, would be useful for debugging, but what if, let's say, a variable was being changed forever? Would it just print a bunch of stuff showing it changed? Or would it just say
“x is 2” then changes to “x is 3”?

alexphan wrote:

fredfish10 wrote:

support

Reason?

Support, would be useful for debugging, but what if, let's say, a variable was being changed forever? Would it just print a bunch of stuff showing it changed? Or would it just say
“x is 2” then changes to “x is 3”?

You don't need a reason to support, just one to no support, and also, it would say 'variable x has changed from 2-3(and in this bracket -how many times it is doing it)

I think the log should act like the browser console, with users being able to print something with a block similar to console.log(). I would rather have the programmer decide what is logged rather than automatically logging information such as variable changes, for more versatility.

Chibi-Matoran wrote:

I think the log should act like the browser console, with users being able to print something with a block similar to console.log(). I would rather have the programmer decide what is logged rather than automatically logging information such as variable changes, for more versatility.

Yep..

Support, would be very helpful.

Support!

Chibi-Matoran wrote:

I think the log should act like the browser console, with users being able to print something with a block similar to console.log(). I would rather have the programmer decide what is logged rather than automatically logging information such as variable changes, for more versatility.

You can do that with a list.

Support for a configurable log though, it would be a lot easier.

stickfiregames wrote:

Chibi-Matoran wrote:

I think the log should act like the browser console, with users being able to print something with a block similar to console.log(). I would rather have the programmer decide what is logged rather than automatically logging information such as variable changes, for more versatility.

You can do that with a list.

Support for a configurable log though, it would be a lot easier.

Support

Support for

log [Success!] in the console::control

(or something like that)
and the console only appears when the block is in the project, like having a graphic effect block in the project; once it is dragged out, the console disappears.
And the console is resizable.

Chibi-Matoran wrote:

I think the log should act like the browser console, with users being able to print something with a block similar to console.log(). I would rather have the programmer decide what is logged rather than automatically logging information such as variable changes, for more versatility.

So much support for that. I would love this for debugging. But in the meantime, I'll go make a workaround.

Scratcher1002 wrote:

Chibi-Matoran wrote:

I think the log should act like the browser console, with users being able to print something with a block similar to console.log(). I would rather have the programmer decide what is logged rather than automatically logging information such as variable changes, for more versatility.

So much support for that. I would love this for debugging. But in the meantime, I'll go make a workaround.

Okay everyone, if you want to use it, here it is.

Bump!

Bump.

Support, but it would say “Running forever” or “Running in loop ”LOOP NAME“” if there is a loop in the project.

If you don't, then this would break a project if someone used

repeat (99999999)

end

or

forever

end

Mind if I make a better mock up?

Support, this really helps, since I find it useful.