[mythtv] render2019 comments

Klaas de Waal klaas.de.waal at gmail.com
Sun Oct 6 21:14:46 UTC 2019

Hi Mark,

It is not a problem if the Frontend ID is enabled, it is read-only
anyway. Navigating to this field means that there can be a help text
presented which is also nice. See for example the field "Delivery
system" (mythtv-setup page Input Connections, select one input and
then the page with this field shows) which also only presents a value
but is enabled and so it can be selected.

There are other places where the enabled is used to prevent changing
the value. It would be good to have a ReadOnly setting for this and it
would be even better to change the presentation to remove the
decorations that show the field can be modified.
For example, the down-arrow button at the left of the field which
indicates a popup list should not be drawn if the field is ReadOnly.
So to summarize I think that Enable/Disable which does greying out and
disables navigation, and a ReadOnly that prevents editing and that
removes the arrows would be great. However, I have no idea how much
work this would be and how many people would like this also.

About the greying-out itself, it does only grey out the label value
(at the left) but not the field value (at the right). I would expect
both the field and the value to be greyed-out. It is not really
visible with a checkbox but with the "Frontend ID" field it does look
really odd.

Sorry for hijacking this thread...


On Sun, 6 Oct 2019 at 19:18, Mark Kendall <mark.kendall at gmail.com> wrote:
> On Sat, 5 Oct 2019 at 07:51, Klaas de Waal <klaas.de.waal at gmail.com> wrote:
> >
> > The grey-out, as implemented now in 2019-render with commit "4fe3b:
> > Settings: Update standard theme to 'gray out' disabled settings" does
> > break mythtv-setup page "Capture Card / Card type". Here I apparently
> > use this attribute to skip the field 'Frontend ID' and that is now
> > grey. This field should not be grey because it is relevant to the
> > page; the field is skipped with editing becausee it shows content that
> > cannot  be edited.
> > Maybe we do need a separate function to set the grey/not-grey state of
> > a field? Or should I do something different for the "Frontend ID"
> > field?
> Klaas,
> Looking at that setup page and the code - it looks like the Frontend
> ID is informative (i.e. it helps the user identify what /dev/dvb/xxx
> actually is - in the case where there are multiple cards) and it is
> not stored in the database. So it is essentially not a setting - but
> the settings ui does not currently have the ability to show something
> that isn't a setting.
> I would suggest either extending standard settings to have a
> 'ReadOnly' state - though not sure how much code that would require -
> or alternatively, on that setup page, append the Frontend ID to the
> device/adapter selection. So instead of DVB device showing (in my
> case) '/dev/dvb/adapter0/frontend0' it would read
> /dev/dvb/adapter0/frontend0 (ST STV0299 DVB-S) - which I think would
> require only a slight modification to the code. The one obvious
> problem is that string is quite long...
> Thoughts?
> Regards, Mark
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

More information about the mythtv-dev mailing list