February 1st, 2008 by Kyle
Tags: , , , , , ,
Posted in: Uncategorized


In the past year I have basically become a Firefox convert. I rarely use IE, except to troubleshoot a few customer issues and when double checking my website layout to make sure it works in various browsers. Don’t even mention IE7…cause I haven’t upgraded to it and am quite wary. A colleague of mine had upgraded to IE7 and then got into a situation where he desperately needed to have IE6. Another colleague found this cool utility:

FireFox with the IE Tab plug-in: http://ietab.mozdev.org/

This took care of that…and all is well.

-Kyle



3 Comments »

I have been asked this a few time by customers and figured this was worthy of a quick post:

The release and debug player cannot co-exist on a machine.
(You can’t have release and debug activeX or release and debug plugin installed at the same time, but you can have release activeX and debug plugin)

A player (plugin/activeX control) with the same version#, regardless of debug or release type cannot upgrade an installed player with the same version#. You must first uninstall the player then install the other version of the same player# to switch between release and debug player of the same version#.

The debug player is not available to the general public; it is only available within purchase products (like Flash Authoring, Flex Builder, FDS).

A debug swf will run in either player, but only produce trace and throw RTEs in the debug player.

You can determine what version of the player you are running from within a Flex app using the following code:

<mx:Label text="{Capabilities.playerType} {Capabilities.version} {(Capabilities.isDebugger)? ‘debugger’ : ‘release’}"/>
 


No Comments »