Reply to thread

Message

<blockquote data-quote="brainbone" data-source="post: 492986" data-attributes="member: 24130">The newer versions don't click the fullscreen button.&nbsp; Instead, they stretch the browser window to avoid problems with keeping the host window (SageTV in my case) focused and accepting remote input -- but the newer version is more directed at the Netflix SageTV and less general purpose.&nbsp; Take a look at the Netflix SageMC thread on the SageTV forums.&nbsp; There have also been some recent changes to the sensitivity of the image search and the time-line slider loop solving issues with silverlight 3 and the the SLPLayer that you may not be aware of. At this point, I'm looking into how VMC center handles nearly seamless integration of the player.&nbsp; Unfortunately, they use what Netflix calls the &quot;Netflix Branded&quot; api... something that Netflix will only allow for app developers that target ~50,000 users in the first months of app release.&nbsp; I'm trying to use greasemonkey, etc., injecting code I've captured with wireshark, trying to get the standard player to expose the API, but it appears that much of the enforcement is on the server side.(Edited for typos)</blockquote>

[QUOTE="brainbone, post: 492986, member: 24130"] The newer versions don't click the fullscreen button. Instead, they stretch the browser window to avoid problems with keeping the host window (SageTV in my case) focused and accepting remote input -- but the newer version is more directed at the Netflix SageTV and less general purpose. Take a look at the Netflix SageMC thread on the SageTV forums. There have also been some recent changes to the sensitivity of the image search and the time-line slider loop solving issues with silverlight 3 and the the SLPLayer that you may not be aware of. At this point, I'm looking into how VMC center handles nearly seamless integration of the player. Unfortunately, they use what Netflix calls the "Netflix Branded" api... something that Netflix will only allow for app developers that target ~50,000 users in the first months of app release. I'm trying to use greasemonkey, etc., injecting code I've captured with wireshark, trying to get the standard player to expose the API, but it appears that much of the enforcement is on the server side. (Edited for typos) [/QUOTE]

Verification