generic label overrides ignored in skin.conf?

[kip...@gmail.com]

I tried overriding some label text (not to be confused with unit labels) in a skin.conf like so:

[Labels]
    [[Generic]]
        outTemp = Out Temp

But the overrides weren't honored for the image generation (captions) or html generation ($obs.label.outTemp). Changes in the weewx.conf StdReport, Defaults section work:

[StdReport]
   [[Defaults]]
       [[[Labels]]]
           [[[[Generic]]]]

              outTemp = Out Temp

As are changes placed into the specific skin section of weewx.conf without a "Defaults" heading:

[StdReport]

    [[SeasonsReport]]
        skin = Seasons
        enable = true
       [[[Labels]]]
           [[[[Generic]]]]

              outTemp = Out Temp

Am I missing something here? Are ImageGenerator and CheetahGenerator not merging the label overrides from skin.conf?

[Tom Keffer]

Apologies for how complicated these overrides have gotten!

1. Which version of WeeWX?

2. Make sure the files are actually getting regenerated. Deleting them before running wee_reports is best.

3. There is a hierarchy of precedence on options. Having said that, an override at the specific skin level is at the top of the hierarchy, so that should always work.

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d4196a9b-8e3b-48a8-a16a-151071d15249n%40googlegroups.com.

[kip...@gmail.com]

1. 4.5.1

2. Deleted all files and retried - same behavior

3. It seems to work at skin level through weewx.conf but not through skin.conf (nested under specific skin without "Default").

Thanks for all the hard work, I've been a happy weewx user for years. This is one of the few times it's made me scratch my head.

[Tom Keffer]

3. It seems to work at skin level through weewx.conf but not through skin.conf (nested under specific skin without "Default").

Sorry. I didn't follow this.

1. Perhaps you can post your [StdReport] section?
2. If you're editing skin.conf, remember that it falls pretty low in the override hierarchy. Anything in [StdReport] will override it.
3. Make sure wee_reports is using the same weewx.conf that you're editing.
4. If all else fails, set debug=1, then run wee_reports. Post the log.

-tk 

[gjr80]

Options hierarchy can be a challenge to remember unless you are using them all the time. I always like to refer to the table in the How options work section of the Customization Guide, in particular the Comments column.

Gary

[Tom Keffer]

Heh. Wait until V4.6, which introduces yet another level: the locale files.😯

-tk

--

You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/1116cbac-4d59-4e07-960f-6796acfa0f19n%40googlegroups.com.

[kip...@gmail.com]

Whoops, looks like I just have the priority backwards. I expected skin.conf to override weewx.conf, not vice-versa. Sorry all, thanks.

[Tom Keffer]

The theory is that skin.conf is in the domain of the skin writer, while weewx.conf is in the domain of the user. 

The user always has the final say.

--

You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/38fb5153-d002-4efa-9eab-7afcc18e4531n%40googlegroups.com.