Remove ContextMenuItems?

Hi,

Is it possible to remove context menu items such as 'Go to root' within a plugin?

f3ar007

yep checkout http://trac.xbmc.org/changeset/16314

addContextMenuItems(items, replaceItems = True)

Sorry to dredge up such an old thread, but it seemed an appropriate place to ask this:

Is it possible to remove some, but not all, of the existing context menu items? And if not, is it possible to re-add a default item? Can I get at the built-in string for "Add-on Settings" button for instance so I can re-add it?

I could add my own string in strings.xml but I'd rather use the existing one if possible for consistency.

-j

Nope - it's all or nothing.

jmarshall Wrote:Nope - it's all or nothing.

I also noticed that. Would a feature request (at least re-adding "Add to favourites") have a chance?

regards,
sphere

sphere Wrote:I also noticed that. Would a feature request (at least re-adding "Add to favourites") have a chance?

Curious about that myself. I basically have a ticket out for this here, but it could probably be worded in a more generic fashion.

FWIW, I achieved what I wanted in my own plugin like so:


String 1045 is "Add-on settings" and in my action handler for "settings" it calls xbmcplugin.openSettings(). This works, but it'd be nice to be able to add it back using the default handler and without hardcoding the string ID.

The thing is, a great majority of the default context menu items really don't apply to most addons. The all-or-nothing approach means most of us are probably going to go for "nothing," and that has the potential to ruin UI consistency between plugins and between the plugin and XBMC itself.

-j

Agreed that it's not ideal - basically the design of this was never considered in any detail - it was popped in as-is without too much thought to satisfy a particular use case back in the days when we were more carefree about what and how we exposed stuff to python.

Currently how the context menu works is before it's shown we run through and add buttons if they make sense according to the internal rules. I propose we change this so that instead what happens is each view has it's default buttons, and then a routine runs which filters out the ones that don't make sense (and possible adds in some extras). This could then be done by the plugin if the plugin wishes to do so.

XBMC then displays the menu. If it's a plugin-specific action, it calls back into the plugin to do it's thing (as is done already).

We "just" have to determine a suitable manner to do this (we probably need a nicer way to pass stuff from XBMC to the plugin - using a single string URL is really nasty).

Cheers,
Jonathan

jmarshall Wrote:Agreed that it's not ideal - basically the design of this was never considered in any detail - it was popped in as-is without too much thought to satisfy a particular use case back in the days when we were more carefree about what and how we exposed stuff to python.

Certainly not trying to complain too much. UI consistency is, IMHO, a big thing though. Addons have gained so much in popularity that anything we can do to make them feel like an integral part of XBMC is a good thing.

jmarshall Wrote:Currently how the context menu works is before it's shown we run through and add buttons if they make sense according to the internal rules. I propose we change this so that instead what happens is each view has it's default buttons, and then a routine runs which filters out the ones that don't make sense (and possible adds in some extras). This could then be done by the plugin if the plugin wishes to do so.

We "just" have to determine a suitable manner to do this (we probably need a nicer way to pass stuff from XBMC to the plugin - using a single string URL is really nasty).

Calling back to the plugin with a single-string URL is a bit ugly, but it's not a show-stopper at the moment I don't think.

I'm not entirely sure how the filter should work, though. I suppose it could be as simple as a bit mask with some constants defined (e.g., CONTEXT_MENU_SLIDESHOW)? Seems like the easy way to do it anyway, but you know more about the internals than I do

-j

How can I currently recreate the "Picture information" (string id 13406) and "Start slideshow here" (string id 13422) context menu items from within my plugin?

-j

I managed to somewhat recreate the "Start slideshow from here" context menu item with:


That works, but doesn't start it from "here;" instead, it starts it from the first image in the current list.

As for "Picture information," I'm still clueless how to get at this via an add-on.

Is there a way to access or reproduce these two functions from within an add-on?

-j