Two basic problems with Segments

Issues
1

WLED 0.14.0-b6 (and earlier)

When adding a new segment, before selecting an effect for it, it’s a coin toss whether or not the palette area will be populated as expected - or just show a single Fx colour and report “Color palette not used”.

Obviously, before an effect has been selected, no effect has been able to set the flags that indicate if a palette is used or not. Even selecting an effect that uses the palette does not subsequently force the palette to show.

Usually deleting the segment and adding a new one again gets around this.

The other issue is that if more than one segment in play and segment 0 has it’s brightness slider lowered, then when “Reset segments” is selected segment 0 brightness remains low but the slider is hidden and the only way to restore it is to reset the ESP or select a preset that has appropriate brightness levels defined (similarly the JSON API can be used - but it strikes me that “Reset segments” should restore full brightness).

Maybe I’m misunderstanding some deliberate design? Or maybe it’s something worth opening a GIT issue about?

2

File a bug report on Github.
It may not be an easy solution though and it will not be available in 0.14.0. Most likely in 0.14.1.

3

OK, will do but I feel obliged to look through the source to see if I can offer a fix first. The problem with that is understanding the structure of the project which is no small task!

On a related matter, Is it appropriate to ask questions about writing new effects code in this forum? for example I’ve been struggling to work out the significance of calling:

SEGMENT.setUpLeds();

Not all effects call it (usually when initialising at SEGENV.call == 0) but if I add it to an effect I’m writing it changes what I get back from SEGMENT.getPixelColor(). I’m trying to use that to merge my effect with underlying segment pixel data from effect patterns in overlapping segments.

4

That is not available (and no longer needed) in 0.14.0-b5 or b6.