Calling NextPVR restart after config.xml changes

[bgowland]

Thank you all for invaluable input. I didn't want to get any further into what I am trying to do without hearing really helpful stuff like this.

I guess I was hoping that I could get a scenario whereby an 'apply' changes would do exactly that. Changes made could stop/restart anything needed and re-open NextPVR (if necessary) for an instant check to see any results.

From the sounds of it this may be getting a little too complex......

Hi steeb,

One thing I'd say is don't be disheartened. Coding is often about tackling hurdles - either you work out how to get over them or you learn to walk around them if they're too high.

A GUI-based editor for config.xml sounds like a good idea in my book even if it doesn't automatically restart things to apply changes. I thought about this on a couple of occasions for GB-PVR. Even though the N-PVR config.xml isn't as convoluted (yet) as the GB-PVR one became, an editor for it seems like a useful tool for you to develop.

My usual approach when hitting snags is to sit back, do something else, have a re-think and then try a different angle. There's normally beer involved at that stage - not sure if it helps but what the heck.

One day I might tell the story of the day my wife (a non-techie) asked me out of the blue what a 'double word' is.

Cheers,
Brian

[ACTCMS]

My usual approach when hitting snags is to sit back, do something else, have a re-think and then try a different angle. There's normally beer involved at that stage - not sure if it helps but what the heck.

Let's face it - there's always beer involved (just... preferably not green):eek:

[mvallevand]

One day I might tell the story of the day my wife (a non-techie) asked me out of the blue what a 'double word' is.

Funnier knowing this is also a "long long"!

Martin

[steeb]

Hi steeb,

One thing I'd say is don't be disheartened. Coding is often about tackling hurdles - either you work out how to get over them or you learn to walk around them if they're too high.

A GUI-based editor for config.xml sounds like a good idea in my book even if it doesn't automatically restart things to apply changes. I thought about this on a couple of occasions for GB-PVR. Even though the N-PVR config.xml isn't as convoluted (yet) as the GB-PVR one became, an editor for it seems like a useful tool for you to develop.

My usual approach when hitting snags is to sit back, do something else, have a re-think and then try a different angle. There's normally beer involved at that stage - not sure if it helps but what the heck.

One day I might tell the story of the day my wife (a non-techie) asked me out of the blue what a 'double word' is.

Cheers,
Brian

Many thanks Brian.

I wasn't getting too disheartened, and with help here it makes it much easier to get around hurdles before hitting some of them! In this instance I think I will walk around the restart issue as this was only the last step in what I was trying to do. Now if I can get the other things I would like to do to work, then that would still be an achievement And if there is an excuse for a beer, well I won't argue with that!

Though perfectly at home with a bit of notepad editing I always though a GUI editor for the GB-PVR config.xml would be a handy thing to have. And though I believe Sub has said the NextPVR one will never become as convoluted it seems like it could be a handy tool.

Am going back to the start just to see if I may be better off doing this in VB anyway (even though I've spent 6 weeks learning and working in AutoIT, all good experience)

Intrigued by the story of the 'double word'

very best

steeb

[steeb]

Let's face it - there's always beer involved (just... preferably not green):eek:

I like this beer approach but I may stay away from too many of the green ones

[bgowland]

And if there is an excuse for a beer, well I won't argue with that!

Well as Alex pointed out, there's always beer involved (it helps lubricate the braincells). Just watch out for the 'one too many' where you end up staring at code you wrote an hour before and haven't go the slightest idea what any of it means.

Am going back to the start just to see if I may be better off doing this in VB anyway (even though I've spent 6 weeks learning and working in AutoIT, all good experience)

Being an external tool then there's no need to conform to any particular language so just go with whatever you're comfortable with and gives the easiest XML parsing and GUI design options.

Intrigued by the story of the 'double word'

Early 1990s, I was working on some Pascal code which did some integer calculations on the output from some lab equipment. In the code, the result data type was a LongInt and all worked well (LongInt is a 32-bit signed integer - Pascal didn't have a 32-bit unsigned integer type).

One day we had some occasional spurious results and after a couple of hours of not being able to see the wood for the trees, I went to bed mulling over my code. The next day I woke up with an idea, went into work and defined my own 32-bit unsigned data type (DWORD), plugged it into the code and everything was fixed.

After work that night, sitting in the pub, my wife said "OK, so what exactly is a double word?". Slightly confused I told her it's an unsigned 32-bit integer then asked why she wanted to know.

Apparently in the middle of the night I'd been talking techno-babble in my sleep then suddenly sat bolt upright, pointed into thin air and said "I need to use a double word!!!". At that point I closed my eyes, lay down and went out like a light.

To this day my only recollection is going to sleep thinking about the code and waking up the next morning somehow knowing how to fix it. Strange but true.

Cheers,
Brian

[steeb]

Well as Alex pointed out, there's always beer involved (it helps lubricate the braincells). Just watch out for the 'one too many' where you end up staring at code you wrote an hour before and haven't go the slightest idea what any of it means.

Without the beer I am still finding I get this effect! Due to the steep learning curve I keep looking at stuff I did before and thinking 'what was that I did that works' and 'how does it work'!

Being an external tool then there's no need to conform to any particular language so just go with whatever you're comfortable with and gives the easiest XML parsing and GUI design options.

Yes that is why originally I went with AutoIT as I have to say there are many aspects to it that for a newbie work very well and are quick to pick up logically. For simple GUI's IMHO it is very powerful, however I think long term I would have met with some difficult scenarios dealing with the XML parsing which appears to me at best with AutoIT is a hack. I think with VB I am going to have a more stable platform to build from. However that has set me back a few steps.

Particularly having a problem at the moment at working out where is best to store my vars. Alot of the help and google searching jumps from basic programming to advanced without filling the 'inbetweens'. To keep my code in easy to find places I didn't want to declare the vars within the routines. Stick 'em in modules? Classes? Not a request as I realise that this is not a VB NET support forum but should anyone care to enlighten me as to the best procedure to hold a bunch of var definitions I would be very interested

Early 1990s, I was working on some Pascal code which did some integer calculations on the output from some lab equipment. In the code, the result data type was a LongInt and all worked well (LongInt is a 32-bit signed integer - Pascal didn't have a 32-bit unsigned integer type).

One day we had some occasional spurious results and after a couple of hours of not being able to see the wood for the trees, I went to bed mulling over my code. The next day I woke up with an idea, went into work and defined my own 32-bit unsigned data type (DWORD), plugged it into the code and everything was fixed.

After work that night, sitting in the pub, my wife said "OK, so what exactly is a double word?". Slightly confused I told her it's an unsigned 32-bit integer then asked why she wanted to know.

Apparently in the middle of the night I'd been talking techno-babble in my sleep then suddenly sat bolt upright, pointed into thin air and said "I need to use a double word!!!". At that point I closed my eyes, lay down and went out like a light.

To this day my only recollection is going to sleep thinking about the code and waking up the next morning somehow knowing how to fix it. Strange but true.

Cheers,
Brian

Now this is a gem of a story, isn't it only genius's that do such things?

very best

steeb

[bgowland]

Without the beer I am still finding I get this effect! Due to the steep learning curve I keep looking at stuff I did before and thinking 'what was that I did that works' and 'how does it work'!

Yep, that happens too when learning new systems but it gets easier with perseverance.

...I think long term I would have met with some difficult scenarios dealing with the XML parsing which appears to me at best with AutoIT is a hack.

XML (as with other markup languages) should be so simple but without a good parser (or even with one) it's often more complex than it first appears. One good thing with doing this with npvr's config.xml is that it doesn't nest deeply.

Particularly having a problem at the moment at working out where is best to store my vars....To keep my code in easy to find places I didn't want to declare the vars within the routines. Stick 'em in modules? Classes?

If you're going VB.NET then you're talking OOP so routines and modules don't apply as such...Classes on the other hand are fun.

Now this is a gem of a story, isn't it only genius's that do such things?

Well my wife's take on it is simply that only 'odd people' do such things.

Cheers,
Brian

[steeb]

Well my wife's take on it is simply that only 'odd people' do such things.

Cheers,
Brian

All Geniuses are odd

[ACTCMS]

All Geniuses are odd

I'm not odd...:confused:

Alex