Notice: Beta 7.0.12 and Themes

[toricred]

Last night I updated to the latest version of the firmware for my HD200. Tonight I updated to Sage 7.0.12. After the Sage update I am having a problem with my HD200 where the screen doesn't seem to be redrawn as the cursor moves around. I tried reverting to a default .properties file for this extender and that didn't fix it. I have discovered that my 3 x HD100s work fine as does the PC client and the UI on my server. I'm trying to revert the firmware to 7/12 version right now to see if the firmware is the problem. Anybody else seeing anything similar?

* merged threads *

[toricred]

OK, the 7/12 firmware didn't fix the issue.

I copied the .properties file over from one of my HD100s and it is now working. For some reason the defaults that happened when I removed the .properties file didn't fix it. I wonder why.

Edit: I found the problem. It is the MBDiamond Theme that caused my problems.

[jorton]

Please disable the "MBDiamond" theme and select the "Standard" theme before updating to 7.0.12. From what I can see I need to make some changes to the theme.properties file to make things compatible again. I will release an update as soon as I can.

On my server and clients there was missing graphics etc... so I will need to correct.

Regards,

Jeremy

* merged threads *

[Opus4]

I hate to change things in mid-stream, but the theme system was overhauled & current themes may not be compatible. The new system should allow for more to be done with themes in the future.

- Andy

[jorton]

No problem Andy,

I noticed the new features and I think this will make my life easier, so thanks!

I just wanted to make sure that I didn't cause anyone any unneccessary grief

Cheers,

Jeremy

[jorton]

I have updated MBDiamond (1.5) for 7.0.12 and posted the plugin.

Prior to upgrading Sagetv to 7.0.12 select the "standard" theme and exit. After upgrading to 7.0.12 then you can download the version above from the plugin repository to update to the lastest version of MBDiamond (1.5).

If you would like to use the old version 7.0.9-7.0.11 compatible you can manually download from,

http://jorton.googlecode.com/files/MBDiamond.1.4.zip

and install by unzipping into your Sagetv\STV\ directory.

Thanks,

Jeremy

[Opus4]

BTW: You don't need to make a complete copy of the entire Standard theme when creating a custom theme.

How many images are you actually changing in your theme?

You only need to provide the images you want to change, include only the theme.properties lines that you are changing or adding, and be sure that your custom theme.properties either defines no parent theme (so that it uses the Standard theme as its parent) or specifies that the Standard theme (or some other theme) is its parent.

I see additional zip files in your theme directory -- are those other options that the user could manually use for other color options? If so, you could easily provide additional themes as part of your theme plugin. Use one as the direct child of the Standard theme, then the others will be children of your main theme or of the Standard theme if they don't share any files.

Providing only the files your theme changes will make the download smaller & more easily allow you to provide multiple themes at once.

- Andy

[jorton]

Hi Andy,

In the first versions I started with a copy of the standard as I didn't know any better

I am changing about 2/3 of the images in the current version of MBDiamond and will be changing almost all of them in the next release.

I'm really just getting a handle on a very small portion of the possible settings in the theme.properties file and hope with this new theme system to be a bit more efficient with the next version and utilize some of the new settings so I don't have to create as many changes in an STVi.

Those zip's contained alternative backgroung files as some liked the green and some like the blue, and like you and Jerekiwi pointed out, I could just make another "green" theme that used the "blue" theme as the parent etc.

Thanks, all this info helps.

Jeremy

[Brent]

If you have a custom theme loaded on SageTV be sure and switch back to the standard theme before upgrading to 7.0.12. Otherwise it will look very messy to say the least. I couldn't even see the screens well enough to navigate to switch the theme after upgrading.

So if you've done this also and would rather not reinstall the older beta just to get the theme switched here's what I did:

1. Shut down SageTV
2. Shut down SageTV Service
3. Open SageTV/SageTV/SageClient.Properties
4. Search for this in the properties "theme/currently_active="
5. Change that line to this: "theme/currently_active=Standard" without the quotes.
6. Restart SageTV and all should be well again

Alternatively, use mayamaniac's method which will work for all clients & extenders at once:
1. Close SageTV (and Shut Down SageTV service)
2. Go to \SageTV\STVs\SageTV7\Themes\ folder
3. Delete the custom theme that you were using - If you are unsure which one it was, delete all the folders except for "Standard".
4. Restart SageTV and you should be back in business

Hope this helps someone else.

* merged *

[mayamaniac]

Yes, Andy noted it in the release thread.

Another way to restore the standard theme is to close SageTV, then go to \SageTV\STVs\SageTV7\Themes\ folder and delete the theme that you were using. If you are unsure which one it was, delete all the folders except for "Standard".

[bialio]

Andy - it seems like things aren't quite working like I expect them to with the new theme system.

1) When I don't have a theme.properties file in my Theme folder, the theme doesn't even load. I thought it would default to the parent theme in the absence of this file?

2) When I just replace the Serenity images in my Theme folder, there are all kinds of animation artifacts - the only way I can get it to look right is to copy the entire Standard theme and then replace Serenity images on top of them - which of course makes the theme a lot larger to download.....

btl.

[Opus4]

Thanks for letting me know. I'll look into what's happening soon. Don't bother trying to 'fix' your theme until I can see what went wrong in the STV.

- Andy

[jorton]

FYI - I know my fix for MBDiamond was a bit trial and error since I don't quite understand all of the options in the theme.properties file (like Bialio and Opus4) but for me I only had to copy the newer theme.properties file over to my MBDiamond folder and set themeparent=standard and rezip. I didn't need to copy over all the image files from the standard theme to get it to work. I also realize that this means I am probably referencing things I don't need to in the theme.properties file as I don't replace all the images in the standard with my theme.

Hope this helps.

Jeremy

[DON3k]

I fixed the issue by putting the theme to 'standard' in the .properties file.

But man, I was freaked out after the update, when both my server, and my placeshifter looked like this:

[Opus4]

Originally Posted by bialio

Andy - it seems like things aren't quite working like I expect them to with the new theme system.

The v7.0.12.7 (2010071801) STV update should fix the theme issues you ran into. Let me know if your theme still has issues beyond needing to update its theme.properties.

- Andy

[bialio]

Thanks andy! The old theme is actually working now - It does have a property file, but it was just a copy of the Standard themes property file with the parent line uncommented.

btl.

[can3gxw]

Allow me to post my resolution to this - I too was getting the "black screen of death" () when I first updated to Beta 12, and reverting back to 11 was the solution for me. I re-read and saw that I had to disable the themes (which I wasn't even using - just the stock theme with SageMC).

Tried that - no avail - restarted Sage - nothing - restarted HTPC - nothing.

After already backing up my Sage folder before my first update attempt, I wasn't to worried about losing "much" information - only a day old (might not even have changed, so "meh").

Not knowing exactly was was involved with the installer/uninstaller (what was deleted, etc...) , I decided to UNINSTALL Sage. I let the uninstaller go through its paces, and when it was done I went into my Sage program files folder and deleted the entire THEMES folder.

I then re-installed Beta 12, and was PLEASED to see that my wiz.bin was the same one that I had backed up! I started SAGE, and although it took a few extra seconds of nail biting (screen was still black), it started just fine and looked normal. I checked the version, and it was, indeed, Beta 12. I manually updated the STV, and everything is looking perfect.

Please move this post to somewhere else, if you wish, but I though that since this was a sticky, and my resolution worked when the others did not, it would prove useful to others having the same problem.

[MrD]

There is a slight issue that may effect existing (i.e. upgrading) users with the new themes.

I updated to beta 12 and got the UI issue described in this thread. However, I am not using any themes. I was able fix the problem using Brent's approach with the client.properties file.

There was an earlier change where "Standard" was renamed from "Standard SDTV". Apparently that change did not make it into my client properties files. Once I removed "SDTV" all was well.