Every time i compile or run, the flex builder opens a browser showing the output... is there anyway we can destory the older window when newer ones open... i mean a setting in flex.
no. but i think if your pressing debug test and that opens a new browser and starts debugging your app, when you hit stop on the debugging, the app will terminate and close the browser as well. this if the debugging app is the only tab you have opened in the browser. other than that, you can't really do anything about it.
If you have flex builder set up to build automatically then you just need to save the file that you have changed and then when flex have finished building (you can see the status down in the right corner of the screen) reload your browser.
That is pretty much the workflow i have when i develop in flex. This way i only get new browser windows opened when i debug.
Related
I have a solution in Visual Studio 2017 with multiple Asp.Net startup projects.
Current Behavior
When I start debugging each project starts in a new Chrome window with a single tab.
Desired behavior
When I start debugging all web pages start in the same new Chrome window, each in its own tab.
I had the desired behavior in Brave browser, apparently by default—but for business reasons I now need to switch to debugging primarily in Chrome.
So, I suspect this is a browser setting, but as long as I get the desired behavior I am willing to adjust settings in either the browser, Visual Studio or both.
UPDATE:
To be clear this is not:
How to use the same browser window every time you start a project in Visual Studio?
Nor is it:
Stop Visual Studio from launching a new browser window when starting debug?
I do want a new browser window, apart from any previous debugging and indeed a separate instance from any browser I may have already started on the same machine.
To Launch Multiple Asp.Net Projects In The Same Browser Window
You can go Tools menu => Options => Project and Solutions => Web Projects, then you can find a setting called:
Stop debugger when browser window is closed, close browser when debugging stops
Uncheck it and click OK, then you can start the multiple projects in same Browser Window. Note: This behavior after uncheck that setting may not meet all your needs.It will not open in new Chrome instance but in a already running Chrome instance if it exists.
When set the Chrome as default browser in VS. If you've already have a Chrome browser running, start the solution and it will open several tabs in that existing Chrome instance. And only when you have no Chrome instance running, it will start same new Chrome browser window as you expected. So actually this setting only meet part of your expected behavior I guess.
To Launch Multiple Asp.Net Projects In The Same New Browser Window
It seems only when you have no Chrome instance running, this behavior can be reached. And as far as I know, there's no setting in VS can configure VS to always launch Chrome in a new instance with several tabs when start the solution with multiple startup projects.So maybe you can go Developer Community to share your requirement to the Product Team by Suggest a Feature option. Hope it makes some help:)
To avoid using an open browser you can use Browse with... if you can give any argument to chrome however arbitrary, it will open a new browser window. It provides the chrome instance a new "signature" and VS will see the browsers as separate applications.
I'm a C++ programmer, but I'm a newbie in Flex. I'm developing a Flex 3 application for a social network using the FlashDevelop. For debugging I'm using the stand-alone FlashPlayer (10.3 debug) downloaded from Adobe. The application is a simple audio player which shows artist/album images.
The application worked properly on both local computer and remote server until I made some layout changes in Main.mxml. I added some HBoxes and changed Image placement. After that the application still works on my local computer, but it doesn't work properly after I upload it to a server.
Application buttons are not highlighted on over/out/click events, images loaded from the Internet are not displayed, text changed dynamically is not displayed, but when I click buttons a sound file is loaded from the internet and starts playing. It looks like some events which are responsible for components displaying are not dispatched, because some part of functionality not related to displaying still works.
To make sure that this is not a server problem, I rolled back to the previous revision. All works fine.
I suppose that this is a known issue, but I have no idea what is the reason.
Could anyone please help me to resolve the issue?
Thanks.
UDP: I observed the issue in IE and FF, I didn't test Opera and Chrome.
Are you tying to access the pixel data of the images in the new version? If so, that might be the problem, as pixel data for loaded images is not (always) accessible so that might throw a security error, which in turns breaks the rest of the interface.
Also, did you try running the remote version in the debugger? If so, is there any exception being thrown?
And no, it's not a known issue, it's the kind of annoying and hard to debug error that you sometime get when using the Flex SDK.
I have some problems running FlexUnit tests in IntelliJ.
Every time I execute test, Internet Explorer (which is not even set as default browser) pops up and blocks unit test, i.e. blocks it as add so I must allow access through that dumb top bar and then another confirmation and then finally test runs. Is there any way to reconfigure it to another browser or to run it some other way so I just hit the Run button on Idea and I can see results right away?
Thank you for help
As you are using Windows have a look at the first comment by Alexander Doroshko in this bug report: http://youtrack.jetbrains.net/issue/IDEA-49795
Current behavior:
if 'Use system default browser' is selected at Settings | Web Browsers | Default Web Browser then swf/html is started in default OS application (either default browser of standalone Flash player)
if default browser is overridden in IDEA then it is always used both for swf/html.
It would be more convenient if standalone Flash player is used for swfs independently of this setting as soon as it is OS default program for sfws.
I recommend to configure the stand alone flashplayer executable for executing unit tests. As you can also see from the report this has been improved in IDEA 10.
Using Flex Builder 3 :
I have been getting this problem in every single debug launch for past few hours.
I used to get this earlier too, but once in a while, not with every debug launch.
I found out that flex debugger uses a certain 7935 port but I can't figure out
how to change it?
I remember getting this problem a few times. It might have to do with the Flex Profiler (I used to accidentally click that every now and then trying to launch the debugger).
If you start the Profiler and stop it too fast, it will add something to a file in your home directory that it shouldn't.
Check out /path/to/home/mm.cfg on your operating system (on mac, you can open it in textmate with mate ~/mm.cfg). The mm.cfg file stores some information about debugging in Flex
Then in that file, make sure this is the only content:
ErrorReportingEnable=1
TraceOutputFileEnable=1
If there's an extra line (can't remember/find it, something like PreloadSwf=/Users/[username]/Documents/workspace/.metadata/.plugins/com.adobe.flash.profiler/ProfilerAgent.swf?host=localhost&port=9999), delete it.
Let me know if that fixes it.
Lance
Also just make sure you're not using Chrome. Flash Player debugger (at the time of writing this) does not work in Chrome.
This worked for me: right click on a SWF, select "Open with...", choose "Other...", select the Debug player and check the "Always Open With" checkbox.
Mac OSX / FlashBuilder4
Right click your launched flash application, either in the browser or standalone flash player and click on debugger if enabled and change the radio button from localhost to other machine and enter the ip 127.0.0.1 and you are free to debug. I guess the problem maybe from your host file.
Changing the browser from default (chrome) to IE worked for me
Similar to danjp - This started happening to me after a Flash Player automatic update. I simply reinstalled the debug flash players from the Adobe Flash Player download page and everything works as expected.
Make sure there is a swf file with the proper name in your bin-debug directory and that name matches the swf name specified in index.template.html file for the project.
I had replaced index.template.html file by mistake with a similar one from another project. When I tried to debug, I got this "Waiting for flash player to connect to debugger…" status till it timed out.
To me the problem was that internet explorer opened and showed a certification problem, if i didn´t continue this the debugger would show this error. If i continued on ie, no problem happens.
I have installed Flex Builder 3 and Flash Player 10 on my machine.
I don't know where the trace output goes because I just don't see it (I tried debug and output windows).
Also the breakpoints don't hit.
Salut Omule :)
If you press the Debug Icon(the bug thingy) or go to Run > Debug you should go to the Debugging perspective.
If might be handy to install the Flash Tracer plugin for Firefox to see your traces from the browser.
First you need to make sure you have the Debug version of Flash Player 10. You can do that by checking is Debugging is true using this test.
You can view traced messages in the console (Menubar - Window - Console).
But since you said that breakpoints are not hit, I guess the problem is somewhere else. Make sure that you are debugging instead of running the app (select Debug from the Run menu or just hit F11 while at the corresponding mxml file).
If that doesn't help, and if you are on Firefox, try uninstalling the last addon that you installed. Some addons (including older versions of google toolbar and adblock plus) have known to block swfs from connecting to the flex builder's debugger.