Just out of curiosity... Why are you deploying your application as a stand-alone projector when you could deploy it as an Adobe AIR application?
On Mon, Feb 16, 2009 at 2:03 PM, Glen Pike <[email protected]>wrote: > Hi, > > I don't think that updating the FP updates the IDE one normally - I have > never worked out how to do this, even with Kewbee's Plugin Switcher. > > Not wishing to sound too cynical, but if everyone upgrades their FP so > easily, then content creators will have to keep up and they are the one's > who have to shell out for the Adobe products, so maybe that's the reason > behind this -or maybe it's the rush to keep the IDE on a high calorie diet > of new features rather than concentrating on keeping it trim and mean by > fixing the important things that it might be nice to get fixed. I guess I > am just bitter because I have not had a chance to play with CS4 yet :( > > Glen > > > jonathan howe wrote: > >> Well, it doesn't disprove my theory - that is the packaged version prior >> to >> the security patch. The version of projectors that my IDE now creates is >> 9.0.151.0 >> >> So, the mystery remains. >> Anyone with the unpatched version: Test your fullscreen projectors in >> Vista. >> Anyone with the patched version: Test your fullscreen (if it's called >> outside a button event and is invoked by stage.displayState) to make sure >> it >> actually works >> >> Mystery #2: why doesn't the Adobe Updater apply the patches to the >> "Players/" directory if this is such an important security fix? >> >> -jonathan >> >> (Glen, I think I beat your test score by 0.0.106. Booyah.) >> >> >> >> On Mon, Feb 16, 2009 at 2:06 PM, Glen Pike <[email protected] >> >wrote: >> >> >> >>> My IDE published to 9.0.45.0 for that projector. >>> >>> HTH >>> >>> Glen >>> >>> >>> jonathan howe wrote: >>> >>> >>> >>>> Glen, thanks for the response. >>>> >>>> As an interesting (?) complication to this matter, I recently installed >>>> the >>>> new versions of the players to CS3 Professional IDE: >>>> >>>> >>>> >>>> http://kb.adobe.com/selfservice/viewContent.do?externalId=b62ce659&sliceId=2 >>>> >>>> Before I updated, the stage.displayState = >>>> StageDisplayState.FULL_SCREEN; >>>> command worked but full screen was completely black on Vista. >>>> >>>> After I updated, fullscreen wasn't black but the fullscreen didn't work >>>> anymore. Did adobe sneak in more stringent security? If so, why does my >>>> fscommand work? >>>> Glen, would you mind telling me what player version shows up when you >>>> export >>>> a projector from your IDE? >>>> >>>> -jonathan >>>> >>>> On Sun, Feb 15, 2009 at 6:43 PM, Glen Pike <[email protected] >>>> >>>> >>>>> wrote: >>>>> >>>>> >>>> >>>> >>>> >>>>> Hi, >>>>> >>>>> I have no problem with this when publishing a projector from CS3: >>>>> >>>>> this.stage.displayState = StageDisplayState.FULL_SCREEN; >>>>> >>>>> The projector I created is just a shell that loads in another SWF >>>>> containing the App. >>>>> >>>>> But I did run into problems with trying to make a non-projector SWF go >>>>> full screen without using fscommand - (we were running flash player >>>>> from >>>>> the >>>>> command line in Linux because we are compiling the SWF on Windows and >>>>> it >>>>> is >>>>> virtually impossible to create a projector when you are running the >>>>> system >>>>> without a desktop manager.) >>>>> >>>>> I think keeping fingers crossed that fscommand does not get deprecated >>>>> would be a good thing because there are cases where this would cause >>>>> serious >>>>> problems :) >>>>> >>>>> Glen >>>>> >>>>> >>>>> >>>>> jonathan howe wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> Hello, >>>>>> >>>>>> According to docs "Full-screen mode is always permitted in the >>>>>> stand-alone >>>>>> player or in a projector file." >>>>>> >>>>>> Yet I get a "SecurityError: Error #2152" when I call >>>>>> stage.displayState >>>>>> = >>>>>> StageDisplayState.FULL_SCREEN; from a projector. But I don't get it >>>>>> when >>>>>> I >>>>>> use the old fscommand method of going fullscreen. >>>>>> >>>>>> For projectors, shouldn't the mouseevent-click security requirement be >>>>>> waived in order to automatically go fullscreen? Why would it work with >>>>>> fscommand but not the official way, displayState? Anyone do this >>>>>> regularly >>>>>> who has a hint? Should I just be glad fscommand works? >>>>>> >>>>>> -jonathan >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> -- >>>>> >>>>> Glen Pike >>>>> 01326 218440 >>>>> www.glenpike.co.uk <http://www.glenpike.co.uk> >>>>> >>>>> _______________________________________________ >>>>> Flashcoders mailing list >>>>> [email protected] >>>>> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>>> >>> -- >>> >>> Glen Pike >>> 01326 218440 >>> www.glenpike.co.uk <http://www.glenpike.co.uk> >>> >>> _______________________________________________ >>> Flashcoders mailing list >>> [email protected] >>> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders >>> >>> >>> >> >> >> >> >> > > -- > > Glen Pike > 01326 218440 > www.glenpike.co.uk <http://www.glenpike.co.uk> > > _______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > -- Cheers, Nate ---------------------------------------- http://blog.natebeck.net _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
