NextPVR Forums
  • ______
  • Home
  • New Posts
  • Wiki
  • Members
  • Help
  • Search
  • Register
  • Login
  • Home
  • Wiki
  • Members
  • Help
  • Search
NextPVR Forums Public Add-ons (3rd party plugins, utilities and skins) Old Stuff (Legacy) GB-PVR Support (legacy) v
« Previous 1 … 632 633 634 635 636 … 1231 Next »
Should I be worried ?

 
  • 0 Vote(s) - 0 Average
Should I be worried ?
silver217
Offline

Member

Posts: 51
Threads: 17
Joined: Oct 2006
#1
2007-01-09, 06:09 PM
I noticed this in my log:

09-1-2007 7:01:55 PM.015 VERBOSE [1] Initializing skin helper for: .\skin\Blue\main menu\skin.xml
09-1-2007 7:01:55 PM.015 ERROR [1] Unable to find node: /settings/SpecialElements/SpecialElement[@name="MenuType"]

I don't know what that is ? schould it be fixed ? or "if it isnt broken, don't repair it"
I have no idea how long this is already there. I upgraded to 99.5 around christmas.
Carlito
Offline

Posting Freak

Posts: 817
Threads: 41
Joined: May 2006
#2
2007-01-09, 06:23 PM
I don't believe this is anything to worry about. You will see these if a skin doesn't support a certain option.
----------------------
[SIZE="1"]PVRX2 1.3.11
Shuttle SG33G5 Case
Core2Duo E8400 3Ghz -- 4 GB RAM
Hauppauge PVR-150
Adaptec AVC-3610 Dual Tuner
Onboard Intel GMA 3100 through HDMI -- 500GB
37" Westinghouse LCD (1920 x 1080p)

Projects
Program Image Tool[/SIZE]
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,807
Threads: 769
Joined: Nov 2003
#3
2007-01-09, 06:32 PM
Yeah, nothing to worry about.
silver217
Offline

Member

Posts: 51
Threads: 17
Joined: Oct 2006
#4
2007-01-09, 06:40 PM
thanks guys
nightwalker
Offline

Senior Member

Posts: 733
Threads: 54
Joined: May 2005
#5
2007-01-09, 08:43 PM
I also see these types of errors in lots of logs, some the config, some the gbpvr log. My skins still work just fine as far as i can tell, but if i knew what they were I'd go in and fix them.
Any of you skinning guru's documented the errors and what they really mean, as opposed to nothing to worry about?

I get errors like these
Unable to find named image: /settings/CompositeImages/CompositeImage[@name="NormalButtonImage"]
1/9/2007 7:46:44 AM.328 ERROR [1] Unable to find named image: /settings/CompositeImages/CompositeImage[@name="SelectedButtonImage"]
and this
1/9/2007 7:35:48 AM.718 ERROR [1] Unable to find font node: /settings/TextStyles/TextStyle[@name="ButtonText"]
and this
1/9/2007 7:35:48 AM.718 ERROR [1] Unable to find named image: /settings/CompositeImages/CompositeImage[@name="NormalButtonImage"]

You get the idea. from what i see skins now are either image based or xml based or a combination of both but something is generating the errors, even if they don't seem to effect the way a skin works. It would be nice to to look at them, if i only knew what they meant.
Carlito
Offline

Posting Freak

Posts: 817
Threads: 41
Joined: May 2006
#6
2007-01-09, 08:49 PM
There is nothing really to fix. The skin your using just does not support those features. It's not technically an error.
----------------------
[SIZE="1"]PVRX2 1.3.11
Shuttle SG33G5 Case
Core2Duo E8400 3Ghz -- 4 GB RAM
Hauppauge PVR-150
Adaptec AVC-3610 Dual Tuner
Onboard Intel GMA 3100 through HDMI -- 500GB
37" Westinghouse LCD (1920 x 1080p)

Projects
Program Image Tool[/SIZE]
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,807
Threads: 769
Joined: Nov 2003
#7
2007-01-09, 09:21 PM
Quote:I also see these types of errors in lots of logs, some the config, some the gbpvr log. My skins still work just fine as far as i can tell, but if i knew what they were I'd go in and fix them.
Any of you skinning guru's documented the errors and what they really mean, as opposed to nothing to worry about?
They're not errors at all. They're just saying that some optional features arnt being used. For example, the default menu has buttons in a vertical line, but if the "MenuType" tag is specified then it can be used to switch to other menus types like the horizonal menu buttons.

It would be nice if these message didnt confuse people by showing with the message category of "ERROR", but this just happens because usually a missing skin element is an error and it shares all the same logic. It would be hard to differentiate these specific elements from other elements, and not worth the effort, so easier just to leave these log messages as is.
nightwalker
Offline

Senior Member

Posts: 733
Threads: 54
Joined: May 2005
#8
2007-01-09, 10:06 PM
ok, i think that's clear. Just let me ask one question, a skin is fine, no matter what the logs say, as long as it runs and displays correctly?
« Next Oldest | Next Newest »

Users browsing this thread: 1 Guest(s)



  • View a Printable Version
  • Subscribe to this thread
Forum Jump:

© Designed by D&D, modified by NextPVR - Powered by MyBB

Linear Mode
Threaded Mode