bigstep+ / bigstep- / smallstep+ / smallstep- command in conditions not getting processed in site co

Dev Community Dev/API Corner
1

Hi,



Just trying to play around with one of the plugins which currently lacks navigation and add that in. The flash player it’s interacting with is one of those players where the controls and progress bar get show / hidden away completely depending on the mouse location: if it’s anywhere in the player’s window it shows, anywhere else it hides.



Obviously, the ideal scenario is to have the controls / progress bar hidden away when playing and having those show when needing to skip forward / backward so that Plex can correctly calculate the jump position. It’d be really nice if Plex would move the mouse over to where the scroll bar has been defined in the site config before executing the calculations but it doesn’t seem to do that, instead using whatever the current duration status is, which in the case where the controls are hidden, is complete rubbish.



So, as a workaround, my plan was to manually catch the navigation events (smallstep+, smallstep-, bigstep+, bigstep-) and manually move the mouse to a point where the controls would be shown so that the duration state could be correctly updated. However, it looks like these are not getting caught and passed to act on.



Here’s the relevant section from the site config:



[xml]


<state name="playing"><br />
	<event><br />
		<condition><br />
			<command name="smallstep+" /><br />
		</condition><br />
		<action><br />
			<run script="plexEMP.pauseVideo();" /><br />
			<goto state="paused" /><br />
		</action><br />
	</event><br />
	<event><br />
		<condition><br />
			<command name="pause" /><br />
		</condition><br />
		<action><br />
			<run script="plexEMP.pauseVideo();" /><br />
			<goto state="paused" /><br />
		</action><br />
	</event><br />
</state><br />

[/xml]



The pause command is getting caught / processed correctly. The smallstep+ not so much. From the logs…



<br />
Nov 07, 2011 02:42:07 [0xb0491000] DEBUG - LINE: PAUSE<br />
Nov 07, 2011 02:42:07 [0xb0491000] DEBUG - Executing Javascript(plexEMP.pauseVideo();)<br />
Nov 07, 2011 02:42:07 [0xb0491000] DEBUG - Executing Moving to state paused<br />






<br />
Nov 07, 2011 02:42:57 [0xb0923000] DEBUG - LINE: SMALLSTEP+<br />
Nov 07, 2011 02:42:57 [0xb0923000] DEBUG - Pixels played = 0, need to click on 32<br />
Nov 07, 2011 02:42:57 [0xb0923000] DEBUG - Clicking on dead point (600, 300)<br />


This is on Plex Media Server 0.9.3.4 and 0.9.5 running against either clients 0.9.3.4 and 0.9.5.

Any ideas, fixes, work arounds?
2

Hey ReallyFuzzy!

If this is not the iPlayer site config, you probably need something other than plexEMP to control the player (if you can control it using javascript at all).

My experience is that when a Flash player is hiding its controls, the mouse clicks are not registered, even if you try to move the mouse cursor first to make controls visible. It is also not possible to move the mouse cursor with javascript :frowning:

3


Hi Sander ,

This is indeed not the iplayer plugin, it's the unsupported ITV plugin. The player does expose a bit of functionality to JS, but sadly only play / pause. From a quick decompilation of the flash player it would appear that these are pretty much the only methods it exports out and there's also no external events to hook into :(.

I've got all the of the core parts needed to make navigation (I.e.: skip forward / backwards) work using a plain old simple seek bar just as long as the player controls stay on the screen.

I've also got all the parts I need to show / hide the controls (click, move and dead from the site configs can do wonders) and these work correctly and do the right thing.

All that's missing is a way to tie the two up together. And the 4 would fit the bill perfectly *if* they triggered in the same way that play / pause do... This would give the site config a chance to show the controls, have Plex update it's state (big assumption made here being that this part of Plex (i.e: site config event processing and general seek bar processing) are threaded), and then process the click.

Now this may not even work due to the way event processing and duration updates are carried out by Plex, but without being able to catch the step commands, I can't even try it out to see...

Guess just wanted to know if the missing triggers was a known bug, if I was just being thick or if the documentation hadn't been updated to the newest way of achieving the same thing. Sounds like it might be the worst possible option: a new unseen bug. :(
4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.