<div class="gmail_quote">On Thu, Sep 8, 2011 at 9:59 AM, David Austin <span dir="ltr"><<a href="mailto:david.austin@terransoftware.com">david.austin@terransoftware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<br>
I just tried VLC 1.1.11 on Windows 7 with the same result. The <fullscreen /> element have no value regardless of the actual fullscreen state. I also tested 1.1.8 under windows with the same result.<br>
<br>
I have a workaround under OSX by using AppleScript to get the fullscreen state but it would be nice to be able to do it all via http. :)<br>
<br>
Cheers<br>
David<br>
<br>
On 07/09/2011, at 2:45 AM, "VLC" <<a href="mailto:trac@videolan.org">trac@videolan.org</a>> wrote:<br>
<br>
> #5293: OSX 1.1.11 HTTP inteface status.xml does not update the fullscreen element.<br>
> --------------------------------------+-----------------------------<br>
> Reporter: david.austin | Owner:<br>
> Type: defect | Status: new<br>
> Priority: normal | Milestone: Bugs paradize<br>
> Component: Interface: HTTP server | Version: 1.1.11<br>
> Severity: normal | Resolution:<br>
> Keywords: OSX HTTP | Difficulty: unknown<br>
> Platform(s): MacOS | Work status: Not started<br>
> --------------------------------------+-----------------------------<br>
><br>
> Comment (by fkuehne):<br>
><br>
> Is this an OS X only problem? Can you reproduce it on Windows or Linux?<br>
><br>
> --<br>
> Ticket URL: <<a href="http://trac.videolan.org/vlc/ticket/5293#comment:1" target="_blank">http://trac.videolan.org/vlc/ticket/5293#comment:1</a>><br>
> VLC <<a href="http://www.videolan.org/vlc/" target="_blank">http://www.videolan.org/vlc/</a>><br>
> VLC media player<br>
_______________________________________________<br>
vlc-devel mailing list<br>
To unsubscribe or modify your subscription options:<br>
<a href="http://mailman.videolan.org/listinfo/vlc-devel" target="_blank">http://mailman.videolan.org/listinfo/vlc-devel</a><br>
</blockquote></div>Not sure if relevant, but its fixed in 1.2.0<br>