blaher wrote:Thank you very much. I look forward to trying it.
Thanks for testing the events support.
Edit: It seems to work well triggering events, thanks, but I'm not sure how to use the information in the curly brackets. Probably simple for experienced people.

EventGhost events can contain two parts, the event string that you use to activate a macro and a payload part that can contain extra information (the part in the curly brackets).
To access the payload part you need to access it via a Python variable
eg.event.payload- Code: Select all
16:33:14 XBMC2.JSONRPC.Player.OnPlay {u'item': {u'type': u'song', u'id': 2240}, u'player': {u'playerid': 0, u'speed': 1}}
16:33:34 XBMC2.JSONRPC.Player.OnPlay {u'item': {u'type': u'movie', u'id': 1}, u'player': {u'playerid': 1, u'speed': 1}}
From your example events to access the type you could use
eg.event.payload['item']['type'], you could put this in a
Show OSD action
{eg.event.payload['item']['type']} to get the result
song or movie(The curly brackets are needed in the Show OSD action to indicate it's Python code and not just text)
You need to know a bit about Python variables especially the
Dictionary type.
When I drag the event into my tree I just get: XBMC2.JSONRPC.Player.OnPlay. What should my event be to differentiate between songs and movies?
Unfortunately not all events have the type information so I chose not to put that information in the event string on this test version, but I'm probably going to, I just need to figure out how to handle it the best and would appropriate any feedback on it.
jonib