[Preview | Development] Debug Console

[botder 23]

Hello everyone.

I am scripting a debug console, which should seperate the 3 types, info, warning and error and it allows custom types too.

Github: https://github.com/Necktrox/debugconsole

Take a look:

Small Preview (to fit forum width):

Original size:

Features:

• 3 Standard tabs for info, warning and error
  
• Custom tabs for other purposes
  
• Pause the debugconsole whenever you want (per tab)
  
• Copy the debugmessage on click
  
• Switch tabs using mouse
  
• You can move the complete window
  
• You can scroll with mouse wheel
  
• Caches debug messages for tabs, which aren't visible
  
• Ability to hide tabs by pressing on a text-button 'X'
  
• Scrolling with click-and-move

Planned:

• API

Edited November 5, 2014 by Guest

[StreetSaintz 0]

looks very nice man keep it up

[GERgta 0]

That looks useful and clean, I would love seeing it completed

[Jaysds1 5]

It looks very useful!

[Castillo 56]

Isn't that what the debugscript pretty much does?

[Woovie 91]

Looks useful.

[manawydan 5]

nice

[botder 23]

Isn't that what the debugscript pretty much does?

Yes, but seperated.

It's useful when you have 5 resources, which output debug information, because you have either 5 tabs for each resource or an other tab solution.

[Chillax 0]

Looks pretty good.

Goodluck!

[botder 23]

Had not that much time in the last days. The resource needs refactoring for some parts to avoid code repetition.

I added a close text-button (see 2nd image in the first post) and changed the code structure.

Just some questions:

• Should a tab get auto-created when outputting messages to an unknown tab name (my opinion: no)?

• Would you add something to the planned features?

[Woovie 91]

Perhaps log the information to a lua table, so that if you DO add the tab, it's backlog exists. Otherwise, I'd agree with no.

[botder 23]

There will be 2 functions: One function deletes the tab (and keeps the messages) and the second function clears the tab (deletes all the messages, but keeps the tab)

[Woovie 91]

There will be 2 functions: One function deletes the tab (and keeps the messages) and the second function clears the tab (deletes all the messages, but keeps the tab)

What I mean is for a new message type. Don't auto open the tab, but log that in case I decide I want to open it.

[botder 23]

Okay, will add that.

[botder 23]

Update

As mentioned last time, I am not investigating all my time into this resource, so don't expect fast development.

Anyway, I added today the scrollbar inclusive scrolling with the mouse wheel. Going to add the click-and-move scrolling and API functionality later and finally release it.

Pictures from scrollbar (small & original):

P.S. I hope that no moderator will strike me down for double posting (after 1 week)

[botder 23]

Pushed the almost beta-ready version to github (https://github.com/Necktrox/debugconsole)

[UAEpro 1]

if you could make a tab for all this will be good

[botder 23]

Do you mean a tab with every message? Use /debugscript 3.

[Woovie 91]

Why not make it so you can have any tab have what you want? Do it like MMOs do where you have a popup that has some checkboxes to choose what is displayed on said tab. That way you could have the user choose what they want.

[Dealman 37]

Great job, Neck. I do like the fact you also put down comments to help others understand how things are working, and even more so that you're spending so much time refactoring.

This looks like a very useful resource to me, especially if you have a few resources running and they all spit out various shit. I've never been a fan of the default debugscript, especially if something goes wrong with a render event

I'd agree with what Woovie said, also another suggestion I'd have is;

For example when something goes wrong with a function attached to a render event, it'll spam several of those warnings/errors per second - could you make it so they show up as one line? But the ability to collapse it?

Other than that, great work!

[botder 23]

I didn't do much in the last time (to be honest, nothing yet). Was only thinking about how to split the code actually and keep it simple (the current version is a 774 line long piece of code in one file).

What I am going to add

+ Resize (still not sure)

+ Tabmoving (e.g. split debug into 2+ windows with different tabs)

+ Remove the long "Server/Client" and time indicators

+ Add right-click-action for messages (where you can see some info (time received, server/client) in a hover-window)

+ Prevent spamming

+ Make scrollwheel jump page-wise

Should I add logging for the custom tabs, because right now only the default tabs (info, warning, error) have the MTA file-logging available.

[Solo 18]

So basically you're using onDebugMessage in a more advanced way along with dx functions, eh well, good job, I still rather the default debugger, no offence.

[botder 23]

The regular debugscript does a great job if you are not going to spam it from different sources.

[Solo 18]

You can just try, not to make buggy resources?

[botder 23]

It's not only about debugging resource warnings/errors/bugs, you can also use it to show useful information when something happens without editing the resource (which output the debug message). And that's where the debugconsole has it advantage - you can seperate the messages into tabs.