Skin.arctic.horizon: [Request] Play Using in Info Dialog

Do you think this search option https://github.com/jurialmunkey/skin.arctic.horizon/issues/184 would solve this issue?

I'm a bit wary of adding too many buttons as the real estate is fairly limited. The other thing might be a generic "Actions" button that would pop-up a menu of options (similar to "Manage" button).

Yeah, a "Search" or "Actions" (maybe better) button would be workable, I think. Would it be feasible for an "Actions" menu to mimic the standard context menu for the item?

Nope, no way to get the context menu items from the skin. All the "Actions" would need to be hard coded into the skin using builtin commands.

The new "Search" option is perfect for this 👍

@jurialmunkey, would this knowledge of how they work internally help in any way? https://github.com/xbmc/xbmc/pull/18106#issuecomment-651660727

That's only for attaching a specific context menu item to a specific list item in a plugin directory via python - most context menu items don't use this method and instead come from built-ins or context menu addons.

Those properties will only be there for context items specifically added by the python method - the others won't display as those properties. And still, even then I would need a script to retrieve the items - there's nothing in the skinning engine which will expose them. (It'd be really neat if there was because then I could write a script to effectively recreate the context menu for the season viewtype).

@jurialmunkey For what it's worth (and taking into account those only exist for items added via xbmcgui.ListItem.addContextMenuItems(...)), you can retrieve those actions and labels via ListItem.Property(ContextMenuAction(...)) and ListItem.Property(ContextMenuLabel(...)), respectively, and using the index as a parameter.

I'm not sure how well you can handle an indeterminate number of items on the skin side, but these properties should be accessible to you there as well. I can read them via DevHelper Web, just by focusing an item.

Ah of course! I completely didn't even think about actually just using $INFO[ListItem.Property(Context...)] - I wonder if it would actually execute the command if it was put in an <onclick> though...

I'm not sure how well you can handle an indeterminate number of items on the skin side

Not easily... It's basically a case hard-coding X number of entries and having !String.IsEmpty(foo) visibility conditions to check if there's a value.

@jurialmunkey Well, just thought I'd show you my findings 😁