The editor is not a dashboard (no synths)

General
1

When I was young, a band called Queen came along.

On there early albums, they proudly said "No synths used"

This was later dropped (Also see Google and "Do No Evil" as well) :slight_smile:

Is it time to drop "The editor is not a dashboard"?

I say this but I'm just after a small change :slight_smile:

Currently, debug node status is limited to 32 chars

Which is enough in many cases

But us hard-core NRers often need more debugging chars than that

We are prepared for them to ruin the editor aesthetics but we need more!

So we write our own function debug nodes and set node.status ourselves to whatever length we need/want/crave.

Could we have an option in the debug node to remove the 32 char restriction please?

#ThinEndOfTheWedge ???

2

Not yet. You can use the jsonata capability of the debug node to reformat/ recode your debug messages to fit.
Oh ok. How about 33 chars ?
And yes vinyl is still better. :slight_smile:

1 Like
3

Come on - it's 2023 now!

But what's the magic JSONata sauce to output a node.status > 32 chars?

4

The secret sauce is to use jsonata to trim/strip/filter your long debug messages down to less than 32 charsā€¦

5

Agree, surely the NR user should determine if they are more comfortable using the editor to monitor performance, or a dashboard.
It's been raised previously by users, and dissed by the NR team.

I don't necessarily disagree with the 32 chars debug limit, there are other options available.
Maybe an option to click & expand the debug from 32 chars default to the full msg??

6

Just because ....

3 Likes
7

Thank you Santa :slight_smile:

I'll finally be able to see what the sixth colour was :slight_smile:
image

And what have cheerlights been?

image

2 Likes
8

I love to see a can-do attitude! :grinning:

3 Likes
9

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.