Author Topic: Full xLights Control-Bug or intended behavior?  (Read 1301 times)

Offline poporacer

  • Full Member
  • ***
  • Posts: 184
    • View Profile
Full xLights Control-Bug or intended behavior?
« on: January 31, 2021, 09:24:33 PM »
At first, Full xLights Control basically would "clear" the ports and then upload the the configuration for the ports that are actually defined in xLights. If you had the Set Brightness enabled on a model, then that setting would get uploaded as well. If not, then the brightness setting would not get changed (at least that is how I remember it?)
Now there is a default brightness option and if you have Full xLights Control enabled when you upload your output ports configuration, xLights will set the brightness for every port (except the ones that you have defined with Set Brightness) to the default setting. Should it be setting all ports to the default value or only the ports that are not defined in xLights?
My thoughts are that, for example, you want to manually set your brightness in your controller (not necessarily all the same value) and you don't want to use the Set Brightness option in xLights but you do want to "reset" unused ports because you might move a string from one port to another you would want the Full xLights Control option enabled (to "reset" unused ports), but in doing so all of your ports get configured to the default value in xLights.

Offline keithsw1111

  • Administrator
  • Hero Member
  • *****
  • Posts: 2733
    • View Profile
    • Kellyville Christmas Lights
Re: Full xLights Control-Bug or intended behavior?
« Reply #1 on: February 02, 2021, 02:27:37 PM »
It?s changed a bit over time but the current behaviour is the default brightness is applied to all ports unless a mode overrides it.

It is that way because we find people tend to set their shows up that way. They are 30% brightness people so everything is that way unless they have a prop or two that is different.

Offline keithsw1111

  • Administrator
  • Hero Member
  • *****
  • Posts: 2733
    • View Profile
    • Kellyville Christmas Lights
Re: Full xLights Control-Bug or intended behavior?
« Reply #2 on: February 02, 2021, 02:28:12 PM »
I should say further it really wouldn?t matter what we chose someone wouldn?t like it.

Offline poporacer

  • Full Member
  • ***
  • Posts: 184
    • View Profile
Re: Full xLights Control-Bug or intended behavior?
« Reply #3 on: February 02, 2021, 02:47:46 PM »
Thanks,
I wasn't sure if it was by design that way, that is why I posted here to be sure. And I agree with you that whatever method you chose, there would be those that didn't like the method that you chose!
How difficult would it be to add an option to the Default Brightness of "Unassigned Only" or "None"

I can see a use case where people would want the "old" Full xLights Control where it would blank out unassigned ports but not want the Brightness to be altered. If it wouldn't be that difficult, let me know and I will submit an enhancement request.

Offline keithsw1111

  • Administrator
  • Hero Member
  • *****
  • Posts: 2733
    • View Profile
    • Kellyville Christmas Lights
Re: Full xLights Control-Bug or intended behavior?
« Reply #4 on: February 02, 2021, 08:26:00 PM »
But won?t setting it to 100 achieve that?