Debug refactor

[blazoncek]

Separate different debug components]

• generic (WLED_DEBUG)
• FX (WLED_DEBUG_FX)
• bus manager (WLED_DEBUG_BUS)
• pin manager (WLED_DEBUG_PINMANAGER)
• usermods (WLED_DEBUG_USERMODS)
• math (WLED_DEBUG_MATH)
• all (WLED_DEBUG_ALL)

In an attempt to reduce flash usage while still getting a few debug messages.

It would still be preferable to implement #3396 instead or alongside.

[netmindz]

From a brief look - QuickDebug has more features

With this MR I think it would be all to eat to use the wrong value going forward with new development, then lost time with people not seeing the logs they expect etc. It's one thing to do a find and replace, it's quite another to ensure correct usage going forward

[netmindz]

Out of interest, how much smaller is that the image without the logs?

[blazoncek]

From a brief look - QuickDebug has more features

True, but it also uses more RAM and flash and is not a drop-in replacement. I would still prefer to use it, though, if we can manage to change entire codebase.

It's one thing to do a find and replace, it's quite another to ensure correct usage going forward

The debug options are divided into separate groups which makes debug output even less crowded. I.e. if you want to debug segment and effect handling then you'd use WLED_DEBUG_FX and your output would not be overwhelmed by other unnecessary debug information. Or, if you are working on enhancing bus manager you would only want to see WLED_DEBUG_BUS output.
There are no restrictions to keep using WLED_DEBUG (or add WLED_DEBUG_ALL) for anything an uneducated user wants.

Out of interest, how much smaller is that the image without the logs?

Instead of receiving 100.1% to 105% flash usage on my development builds I can use debug I need and still be around 98.9% of flash usage. Non debug builds yield about 97%.

[netmindz]

From a brief look - QuickDebug has more features

True, but it also uses more RAM and flash and is not a drop-in replacement. I would still prefer to use it, though, if we can manage to change entire codebase.

Hopefully not so much that it's a blocker

It's one thing to do a find and replace, it's quite another to ensure correct usage going forward

The debug options are divided into separate groups which makes debug output even less crowded.

Yes I understand what you are trying to achieve, it's just the code discipline and chance for user error when coding to use the wrong DEBUGXX_PRINTLN by mistake. That's where QuickDebug has a big advantage

Out of interest, how much smaller is that the image without the logs?

Instead of receiving 100.1% to 105% flash usage on my development builds I can use debug I need and still be around 98.9% of flash usage. Non debug builds yield about 97%.

A fair chunk of space then. I think QuickDebug will produce smaller builds based on the log level, I'm not sure if changing the log level for specific tags would also reduce the filesize