[RFE] Allow user to configure 200 node cut-off for warning #12

CathySue commented 2024年03月31日 21:06:26 +02:00

First of all, thank you for keeping Lightbeam alive! Much appreciated.

I have an RFE: it would be nice if it were possible to configure the 200 node cut-off above which the warning about performance issues/crashes with graph rendering is displayed. I am not seeing any issues whatsoever with (at the moment) 201 nodes, and would like to raise the bar a bit so I don't get the same warning every time I open Lightbeam.

Thank you!

First of all, thank you for keeping Lightbeam alive! Much appreciated. I have an RFE: it would be nice if it were possible to configure the 200 node cut-off above which the warning about performance issues/crashes with graph rendering is displayed. I am not seeing any issues whatsoever with (at the moment) 201 nodes, and would like to raise the bar a bit so I don't get the same warning every time I open Lightbeam. Thank you!

chikl commented 2024年04月02日 10:16:16 +02:00

Thanks for this issue, @CathySue. The warning was a quick solution because users reported that Lightbeam was crashing when they had many nodes. The problem was that I didn't know which number of nodes led to the crashs so I decided to set a limit of 200. This way users should be always on the safe site.

But the solution is far from perfect and I agree it would be good to raise the limit or even disable it. I will look into this.

Thanks for this issue, @CathySue. The warning was a quick solution because users reported that Lightbeam was crashing when they had many nodes. The problem was that I didn't know which number of nodes led to the crashs so I decided to set a limit of 200. This way users should be always on the safe site. But the solution is far from perfect and I agree it would be good to raise the limit or even disable it. I will look into this.

chikl commented 2024年04月14日 17:40:37 +02:00

With commit bacbebbb9d it is possible to configure the limit. As you can see in the metadata of this issue this improvement will be part of version 3.0.0.

With commit bacbebbb9d4a36318f7a93963d812c05fd766ec5 it is possible to configure the limit. As you can see in the metadata of this issue this improvement will be part of version 3.0.0.