[mythtv-users] bug in mythbackend setup

[Paul Harrison]

On 14/12/2023 11:18, James Linder wrote:

>
>> On Dec 14, 2023, at 18:49, James Abernathy <jfabernathy at gmail.com> wrote:
>>
>>
>>
>> On Wed, Dec 13, 2023 at 11:13 PM james <jam at tigger.ws> wrote:
>>
>> On 14/12/23 12:01, james wrote:
>>> I went to Input Connections
>>>
>>> Down to Max Recordings
>>>
>>> Increased mine from 1 to 2
>>>
>>> [save] is greyed (!!)
>>>
>>> [next]
>>>
>>> If you continue you may lose changes
>>>
>> mythtv-setup to the rescue !
>>
>> I suggest [save] is never greyed, save  ALWAYS saves the data, even if
>> redundant. That way warning/no warning logic is unchanged. Simple fix
>> rather than setting unsaved for yet another condition (and perhaps others)
>>
>> James
>>
>>
>> Was this on a working system?  Did you Click on Enable Updates before you tried to edit and then save? I just tried to change Max recordings and Save was greyed but once I Enabled updates Save worked.
>>
> Jim thanks. I’ll leave the UI design alone but clearly I think …
> specially since [next] says “you're gonna be sorry …” and pressing the greyed [save] stops the ‘unsaved’ message.
>
> James


I'm sure Peter will explain in greater details but basically making the 
Save button active and working all the time would require a complete 
re-write of mythbackend because it was never written in such a way that 
things like tuners, inputs, sources etc are able to be changed on the 
fly. So instead the backend has to be put into a special mode that 
effectively shuts everything down except the webserver. Only then can 
you save many settings which is why you have to enable changes before 
you can press Save to save them. It doesn't mean the UI side of things 
can't be improved to make things more obvious if necessary though. It's 
no different than using mythtv-setup where you are warned to shutdown 
the backend before making any changes at least in Ubuntu you are not 
sure about how other distros handle things.


Paul H.