Noobie Here!

[sub]

I corrected my errors and the new "delete" feature is working.
By the way, is there an event that signals that a recording has started?

There is no events for this. This stuff happens in another process (nrecord.exe), and it's events are only visible inside the recording service.

Is it possible for my plugin to call your Recurring-Recordings menu?
i.e. I press a button in the hidden menu and control passes to your screen.

No, that popup is a feature of the Recordings screen. There is no way to share popups from elsewhere in the application.

[jrockow]

How about this idea...

I want to have my own Pending-Recordings screen.
(actually, I already did a stand-alone version of this)

I would like to redo that version, making it very similar to the Ready-Recordings screen I'm working on now.
I would call that new screen from the hidden menu of my current project.

I assume I would create a new CLASS and SKIN file?
I've been doing a lot of reading, but still not sure what I need to do to move back and forth between the 2 classes.

[sub]

Yes, you could create a new class and skin file. In my Recordings I was able to get away with a single skin file, since each view shows the same list, just with slightly different list of recordings in each. If you needed a different layout for different views etc, then yes you'd probably be best to use a different class/skin.

You can switch to another screen by calling:

Code:

PluginHelperFactory.GetPluginHelper().ActivateScreen(myOtherScreen);

[jrockow]

Just to be sure, when you say "screen" in your command you are actually referring to the new class?
(my first quick and dirty gave me an error)
'Pending' is a type and cannot be used as an expression. (Pending is what I named the new class)

[sub]

Yes, if you wanted to use a new screen, it would be a new class.

[sub]

(my first quick and dirty gave me an error)
'Pending' is a type and cannot be used as an expression. (Pending is what I named the new class)

That's not great name, and in this case is something already defined by VB. Call it something more descriptive, like PendingRecordingsScreen.

[jrockow]

I already tried a different name; the same thought crossed my mind.
However, I'll still make it something other than "Pending".

[jrockow]

I'm having a problem changing screens.

If I code this line: "Dim myPendScreen As New Class2" in my "Class1" class, I can switch to this screen (Class2) without any problem.
I'm using this code you gave me earlier: PluginHelperFactory.GetPluginHelper().ActivateScreen(myPendScreen)

If I add this line: "Dim myPrimeScreen As New Class1" in my "Class2" class, I can't even start NPVR. I get an immediate error.

Here is a snippet from the logfile:

2014-04-01 08:23:13.071 [DEBUG][1] Load@1
2014-04-01 08:23:13.071 [DEBUG][1] About to look for plugin directories in: C:\Users\Public\NPVR\Plugins\
2014-04-01 08:23:13.071 [DEBUG][1] About to check for plugin interfaces in: C:\Users\Public\NPVR\Plugins\CallTest\CallTest.dll


**************************************** With the DIM statement in Class2 it stops at the above line ****************************************
**************************************** With the DIM statement removed it continues on and starts normally ********************************


2014-04-01 08:23:13.086 [DEBUG][1] About to check for plugin interfaces in: C:\Users\Public\NPVR\Plugins\NewRec\ICSharpCode.SharpZipLib.dll
2014-04-01 08:23:13.102 [DEBUG][1] About to check for plugin interfaces in: C:\Users\Public\NPVR\Plugins\NewRec\ManagedUPnP.dll
2014-04-01 08:23:13.133 [DEBUG][1] About to check for plugin interfaces in: C:\Users\Public\NPVR\Plugins\NewRec\NewRec.dll
2014-04-01 08:23:13.133 [DEBUG][1] Plugin PDB also exists: C:\Users\Public\NPVR\Plugins\NewRec\NewRec.pdb
2014-04-01 08:23:13.133 [DEBUG][1] About to check for plugin interfaces in: C:\Users\Public\NPVR\Plugins\NewRec\System.Data.SQLite.dll
2014-04-01 08:23:13.149 [DEBUG][1] About to check for plugin interfaces in: C:\Users\Public\NPVR\Plugins\Test4\Test3.dll
2014-04-01 08:23:13.149 [DEBUG][1] Plugin PDB also exists: C:\Users\Public\NPVR\Plugins\Test4\Test3.pdb
2014-04-01 08:23:13.165 [DEBUG][1] Skipping non-existant plugin directory: C:\Program Files\NPVR\Plugins\
2014-04-01 08:23:13.165 [DEBUG][1] Load@1.1

I'm sure I have some incorrect code somewhere, but since I've been working on this for quite some time I was hoping you could point me in the right direction.

[sub]

Class1 creates a Class2, which creates a Class1, which creates a Class2, which creates a Class1, which creates a Class2, which creates a Class1 and so on for ever (or until it crashes with a stack fault).

You'd be better of not declaring a new class1 instead class2, and instead passing in a reference to your existing class1.

[jrockow]

I'm sorry, but I have been struggling with this all day; "passing in a reference to your existing class1".
I think I understand the concept of what you're telling me, I just don't know how to convert that concept into actual code.