Exactly. I remember my past JBuilder experience for debugging program running with old options and close the tabs automatically.
-----Original Message----- From: Jonas Kvarnstr�m <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Date: Tue, 20 Aug 2002 21:46:07 +0200 Subject: [Eap-features] Re: Second run button and combobox... > > Igor Karpov wrote: > > A common scenario is to have client & server programs that should be > > run/debugged together. What I'm doing all the time is: > > > > start the server - start the client - stop the server - fix something - start > > the server - start the client > > start the server - start the client - stop the client - fix something - start > > the client > > When I'm in this situation I tend to keep a couple of run tabs open all > the time, one for the client and one for the server. When I've fixed a > bug or made some change in one program I press stop and then "play" on > the appropriate tab. This way I can have any number of run > configurations active/dormant, one for each run tab. > > A warning, though: Pressing play on the run tab will run the program > with the same options as before. It will not pick up any changes you > made to the run configuration, such as new command line arguments or VM > parameters. > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://lists.jetbrains.com/mailman/listinfo/eap-features > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
