Developing plugins

[jasonf]

Quote[/b] (sub @ Mar. 03 2005,10:37)]You can already set breakpoints and step through the plugins in the debugger. Just make sure you also add your .pdb file into the plugins directory, and set gbpvr.exe as the plugin executable.

Oh, sweet! I didn't know about that! In VS.NET 2003:

Project properties -> Configuration Properties - > Debugging

Set the Debug Mode to "Program", and then Apply. You'll then be able to set the Start Application to the path and filename for GBPVR.

I also set the working directory to the GBPVR directory, and set my project's build path so that the DLL gets created right in the plugin directory.

You can then hit "Run" from Visual Studio, and it will start up GBPVR. If you set a breakpoint inside your plugin's code, then you can examine your variables, etc.

[smeghead]

Works a treat - excellent

[McBainUK]

This thread has made my day. Didnt know about copying the pdb file. Been trying to get proper debuging working for ages. This is going to save me so much time!

Oh and Merry Christmas all, Only 2hrs and 35 mins to go in the UK

[Old Dog]

Currently the Appearance Manager only works with The Collection skin. If The Collection is not the current skin I would like to prevent the Appearance button from being displayed in the Main Menu.

What is the best way to disable a plugin and prevent it's button from appearing on the Main Menu at runtime?

Thanks,
David

[sub]

What is the best way to disable a plugin and prevent it's button from appearing on the Main Menu at runtime?

There isnt currently a mechanism for this.

[Jeff]

I do something like this in the video archive plug-in when deciding if I should show the dvd2mpeg button on the mvp or not. I also do this in the VA Panel so that I can use GBPVR to set the configuration settings of the panel as if it was a plug-in but to not show a button for it at run time. GBPVR decides to show a plug-in if the name returned by getName() matches the name configured in the config application. So, what you can do is return your proper name from getName() when called by the config app or when the active skin is Collection and return some other string or String.Empty in other cases.

For example, here is what I do for the VA Panel

Code:

public string getName()
{
    // Only show this in the config app
    if (PluginHelperFactory.getPluginHelper() == null)
        return  "Video Archive Panel";
    else
        return "VAPanelScreenSaver";
}

Jeff

[sub]

Very creative. Yes, you could do that.

[Old Dog]

I do something like this in the video archive plug-in when deciding if I should show the dvd2mpeg button on the mvp or not. I also do this in the VA Panel so that I can use GBPVR to set the configuration settings of the panel as if it was a plug-in but to not show a button for it at run time. GBPVR decides to show a plug-in if the name returned by getName() matches the name configured in the config application. So, what you can do is return your proper name from getName() when called by the config app or when the active skin is Collection and return some other string or String.Empty in other cases.

For example, here is what I do for the VA Panel

Code:

public string getName()
{
    // Only show this in the config app
    if (PluginHelperFactory.getPluginHelper() == null)
        return  "Video Archive Panel";
    else
        return "VAPanelScreenSaver";
}

Jeff

Thanks Jeff! It works like a charm.

[Old Dog]

I spoke too soon. It works too well.

It not only prevents the button from appearing, it also drops it to the bottom of the menu list.

When the skin is changed back to the collection, the button is in the wrong place.

[Old Dog]

Please refer to the attachment.

From my plugin, I am trying to inform the user that they cannot use the plugin. What you see below is a IPluginHelper.ShowMessage() box inset in an error message box. The light colored sliver near the bottom is the lower part of the error box's okay button.

Both appear when and only when I call IPluginHelper.ShowMessage().

If I click on the sliver, they both go away. If I do nothing, the inset message box goes away by itself, then I have to press the error box's okay button to get it to go away.

As I said earlier, I wish to inform the user, but I do want an acknowledgement. Also, I believe I can only depend on facilities provided by the core GBPVR application being available.

Please educate me.