[bengalih]

Thank You for the new version. I removed the previous version, laid down the new version and rebooted. I see you have auto fullscreen according to the documentation. The video still does not go full screen. Do I need to configure something?

Here is the debug output:
....
Sikuli debug: in toggleNetFlixFullScreen (F+11)
[log] CLICK on (512,384)
[log] CLICK on (958,747)
Sikuli debug: Click Full Screen result (manual toggle): 1
....

After the video started playing I did:

ctrl+alt+shift+n for next video(Skipped to next video, but still no full screen).

ctrl+alt+shift+f for fullscreen(This worked).

ctrl+alt+shift+f to exit fullscreen(This worked).

ctrl+alt+shift+q to quit(This worked).

Ok...so I took a look at this again. I had some issues with certain resolutions. I had done a lot of my testing outside of XBMC (just launching Netflix in IE) and had not always remembered to put my IE in Kiosk/Full screen mode (F11), which is how XBMC launches it. Because of this, some of the scan regions were off at certain resolutions.

However your tests are not entirely accurate. It is not possible that CTRL+ALT+SHIFT+F worked for you to GO INTO full screen, because the button would not be in the scan region. You can see this in your output above where it says:

Sikuli debug: in toggleNetFlixFullScreen (F+11)
[log] CLICK on (512,384)

That shows that although you tried to toggle full screen, nothing happened. Now, it is possible that the way you were hitting the keys you also then just hit the "F" key by itself which is Netflix's built in Full Screen key... Once in Full Screen the Full Screen button would have been visible in the scan region...so when you see in your log:

[log] CLICK on (958,747)
Sikuli debug: Click Full Screen result (manual toggle): 1

That shows that it clicked near the corner of your screen and the result (1) was a success. The lack of a second "Sikuli debug: in toggleNetFlixFullScreen (F+11)" may have indicated you were doing things too fast as well. Normal circumstances wouldn't have you changing these things within a second or two of each other (no reason to keep toggling full screen unless testing...). So, when doing testing you should always wait about 5-10 seconds in between giving it commands. In reality (and non-debug mode) you can usually go very quickly, but not for testing's sake...

In any event, I have upped a new 1.5b version which should fix the scan regions on the 1024x768 resolution as well as with some other minor things I found.

Let me know how it works out.