config.xml & unvisible

[steeb]

Greetings all,

just wondered, with NextPVR/GB-PVR I do something like:

<!-- MVP Study -->
<MAC-000DFxxxxxxx>
<MVPVideoStandard>auto</MVPVideoStandard>
<MVPSendIncrementalUpdates>true</MVPSendIncrementalUpdates>
<MVPFlickerFilter>none</MVPFlickerFilter>
<MVP16x9Mode>false</MVP16x9Mode>
<MVPOutput>1</MVPOutput>
<MVPWidth>680</MVPWidth>
<MVPHeight>554</MVPHeight>
<MVPOffsetX>20</MVPOffsetX>
<MVPOffsetY>20</MVPOffsetY>
<MVPTranscodeTS>false</MVPTranscodeTS>
</MAC-000DFxxxxxxx>

where the

<!-- hello world -->

or

<!-- MVP Study -->

is ignored by NextPVR and does not affect the config loading.

My question would be is there a way to read that part of the config.xml and link it to the MVP specific underneath?

with vb.net and the xml document class?

I didn't want to bother Mr bgowland too much on this one as I constantly pester him

cheers

steeb

[mvallevand]

A comment is just a Node of the Parent so you shouldn't have trouble getting the contents. I would just add my own markup to config.xml and expect that sub will ignore it. ie <FriendlyName>Kitchen MVP</FriendlyName>

Martin

[steeb]

A comment is just a Node of the Parent so you shouldn't have trouble getting the contents. I would just add my own markup to config.xml and expect that sub will ignore it. ie <FriendlyName>Kitchen MVP</FriendlyName>

Martin

Thanks Martin, just, exactly what I needed to hear, so I should be able to treat the comment as a child node and that would still be readable in the document class? I did try but could not get that work. Note to self: I MUST try harder

steeb

[steeb]

A comment is just a Node of the Parent so you shouldn't have trouble getting the contents. I would just add my own markup to config.xml and expect that sub will ignore it. ie <FriendlyName>Kitchen MVP</FriendlyName>

Martin

Ahhh, no just re-read that. What do you find when you try? If I put ANY tag <Steeb>Hello</Steeb> into config.xml we have burn out?

steeb

[mvallevand]

Try harder is your mantra tonight. I added your markup and using basic XPath there is no issue with

Code:

System.Xml.XmlNode steeb = NUtility.SettingsHelper.GetInstance().GetSettingsNode("//Steeb");
            Debug.WriteLine(steeb.InnerText);

Martin

[steeb]

Try harder is your mantra tonight. I added your markup and using basic XPath there is no issue with

Code:

System.Xml.XmlNode steeb = NUtility.SettingsHelper.GetInstance().GetSettingsNode("//Steeb");
            Debug.WriteLine(steeb.InnerText);

Martin

we need to be loading xml.document class with .net 2.0. syntax. xpath not, I believe, in my realm. Also here you are treating this, I think, as a plugin to NextPVR?

I wish I could I am hoping with time my editor would integrate itself better with NextPVR. You are saying that if I utilise the plugin code built within NextPVR then I can achieve what I want to do

Ummm that sets back my project again! again, again, again

I try, thanks Martin

steeb

[mvallevand]

I used a plugin simply to show that NPVR should not have problems with custom markup, you don't need to use a plugin or XPath if you don't want to,

Martin

[steeb]

I used a plugin simply to show that NPVR should not have problems with custom markup, you don't need to use a plugin or XPath if you don't want to,

Martin

Thanks Martin, difficult as I am.....

Gotcha now. And I don't mean 'gotcha' like caught you out. I mean 'gotcha' as in where you are coming from and explaining to me.

I don't want to use xpath. Fine.

I was not closing my nodes

An open and closed node around, say, a PCH specific, does not appear to cause a problem (I know, that is what you were saying, all along!)

But geniui sometimes have to talk to their lowest common denominator. That's me!

Maybe my ACE for NextPVR will see the light of day, sometime.

very best

steeb

[steeb]

Many thanks Martin, just for a follow up I realised something else that was causing problems.

In the past I had always used something like:

<!-- MVP Study -->

purely as a referential note to myself when digging about in the config.xml

I found one of the problems I was having was translating this into a readable reference in the config.xml file without upsetting NextPVR. The reason..... whitespace I guess

An extra node

<steebtest>
</steebtest>

would appear to be handled very gracefully by NextPVR

but

<steeb test>
</steeb test>

does appear to cause problems?

could I check then that you tried with

<FriendlyName>Kitchen MVP</FriendlyName>

which of course has the whitespace? And therefore what I may have missed?

many thanks

steeb

[steeb]

I take that all back, writing stuff down clears the mind often

I, of course, am using the whitespace within the node name as opposed to the comment... hmmm off to think

all the best

steeb