Actually, if you use the open file command in your browser and open either the debug build or release build, then neither of them work.
On the other hand, accessing either the release or debug versions using a HTTP call results in both of them working. As I understand it, this is the way it is supposed to work. You have to deploy your SWF to a web server to have BrowserManager support. --- In flexcoders@yahoogroups.com, devek <nab...@...> wrote: > > > No rush, but if someone is bored compile this and release an export build. > For me if I go into the bin-debug folder and open it, it works. If I go into > the bin-release folder and open it, it doesn't. I am using flex builder > 3.0.214193 > > Why would it work differently when compiled for release? I'm curious now if > there are any other things that stop working on a release build. This isn't > a big problem for me, I am just curious why. > > For those who don't want to view the attachment. I am merely using > BrowserManager's setTitle() function. It isn't working when ran locally on a > release build but works fine when ran locally on the debug build. > > http://old.nabble.com/file/p26498653/test.mxml test.mxml > -- > View this message in context: > http://old.nabble.com/BrowserManager%27s-setTitle%28%29-function-doesn%27t-work-on-local-release-build--tp26498653p26498653.html > Sent from the FlexCoders mailing list archive at Nabble.com. >
