[flexcoders] Re: Every second time I debug my app, Flex closes Safari :(
I think you can avoid this if you open another site in the first tab before debugging and leave it open as you debug and re-debug. --- In flexcoders@yahoogroups.com, Josh McDonald [EMAIL PROTECTED] wrote: If I reload the app (and kill the debugging session) in the browser beforehand, then Builder will reuse the tab correctly without killing the browser. -Josh On Wed, Oct 15, 2008 at 3:41 PM, Josh McDonald [EMAIL PROTECTED] wrote: Doing that kills the entire browser process. I really can't for the life of me figure out the problem. I've had it happen from Builder and from Flex Plugin, and only in some workspaces even on the same machine :( -Josh On Wed, Oct 15, 2008 at 3:24 PM, Rob Kunkle [EMAIL PROTECTED] wrote: I think this happens because the debugger is still running when you start it the second time. Try pressing the red stop debugging square in flex builder to stop the debugger, and see if that fixes the problem. r --- In flexcoders@yahoogroups.com, Josh McDonald dznuts@ wrote: Hey guys, In one or two workspaces, everything works fine. In most of them, however, every second time I debug an app, everything goes as normal but then Builder kills the Safari application (not just the old tab, but the entire app). This is of course *incredibly* annoying given how slow all this stuff is. Any ideas what causes this? -Josh -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: josh@ :: http://flex.joshmcdonald.info/ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Alternative FAQ location: https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] :: http://flex.joshmcdonald.info/ -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] :: http://flex.joshmcdonald.info/
Re: [flexcoders] Re: Every second time I debug my app, Flex closes Safari :(
Nope, nor if I have a bunch of sites open in another window. On Thu, Oct 16, 2008 at 5:22 PM, arieljake [EMAIL PROTECTED] wrote: I think you can avoid this if you open another site in the first tab before debugging and leave it open as you debug and re-debug. --- In flexcoders@yahoogroups.com, Josh McDonald [EMAIL PROTECTED] wrote: If I reload the app (and kill the debugging session) in the browser beforehand, then Builder will reuse the tab correctly without killing the browser. -Josh On Wed, Oct 15, 2008 at 3:41 PM, Josh McDonald [EMAIL PROTECTED] wrote: Doing that kills the entire browser process. I really can't for the life of me figure out the problem. I've had it happen from Builder and from Flex Plugin, and only in some workspaces even on the same machine :( -Josh On Wed, Oct 15, 2008 at 3:24 PM, Rob Kunkle [EMAIL PROTECTED] wrote: I think this happens because the debugger is still running when you start it the second time. Try pressing the red stop debugging square in flex builder to stop the debugger, and see if that fixes the problem. r --- In flexcoders@yahoogroups.com, Josh McDonald dznuts@ wrote: Hey guys, In one or two workspaces, everything works fine. In most of them, however, every second time I debug an app, everything goes as normal but then Builder kills the Safari application (not just the old tab, but the entire app). This is of course *incredibly* annoying given how slow all this stuff is. Any ideas what causes this? -Josh -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: josh@ :: http://flex.joshmcdonald.info/ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Alternative FAQ location: https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] :: http://flex.joshmcdonald.info/ -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] :: http://flex.joshmcdonald.info/ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Alternative FAQ location: https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] :: http://flex.joshmcdonald.info/
Re: [flexcoders] Re: Every second time I debug my app, Flex closes Safari :(
If only I could get Flex debugging working in Idea 8! On Wed, Oct 15, 2008 at 6:14 PM, Nik Derewianka [EMAIL PROTECTED] wrote: Yep or close the window with the app before re-launching the debug session also works as well. FB on OSX has a lot of drawbacks - on win, the help gets its own window (so it doesn't get killed by the debugging), syntax colouring works better, images actually appear in design mode all the time, it builds a lot faster (iMac in BC spanks my mac pro in OSX), the text editor doesn't lag when doing fundamental things like selecting text. Oh and I love it when FB seems to get confused and tries to launch a debug session but in reality it's just sitting there and waiting to time out. At least embedded fonts still disappear on both platforms in between compiles for no apparent reason so I don't feel completely screwed over. If it was edge case stuff, it wouldn't be a problem, but this is stuff you have to put up with every couple of minutes. Nik -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Alternative FAQ location: https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] :: http://flex.joshmcdonald.info/
Re: [flexcoders] Re: Every second time I debug my app, Flex closes Safari :(
Yep or close the window with the app before re-launching the debug session also works as well. FB on OSX has a lot of drawbacks - on win, the help gets its own window (so it doesn't get killed by the debugging), syntax colouring works better, images actually appear in design mode all the time, it builds a lot faster (iMac in BC spanks my mac pro in OSX), the text editor doesn't lag when doing fundamental things like selecting text. Oh and I love it when FB seems to get confused and tries to launch a debug session but in reality it's just sitting there and waiting to time out. At least embedded fonts still disappear on both platforms in between compiles for no apparent reason so I don't feel completely screwed over. If it was edge case stuff, it wouldn't be a problem, but this is stuff you have to put up with every couple of minutes. Nik
[flexcoders] Re: Every second time I debug my app, Flex closes Safari :(
--- In flexcoders@yahoogroups.com, Nik Derewianka [EMAIL PROTECTED] wrote: Yep or close the window with the app before re-launching the debug session also works as well. FB on OSX has a lot of drawbacks - on win, the help gets its own window (so it doesn't get killed by the debugging), syntax colouring works better, images actually appear in design mode all the time, it builds a lot faster (iMac in BC spanks my mac pro in OSX), the text editor doesn't lag when doing fundamental things like selecting text. Mine does this sometimes on XP. I think that it depends on if the Help is open and how many projects you have open. -Amy
Re: [flexcoders] Re: Every second time I debug my app, Flex closes Safari :(
yeah that sucks...I actually managed to kill that issue, but I can't remember exactly how (sorry). Try this: http://www.visible-form.com/blog/ending-a-flex-builder-debug-session-would-cause-safari-to-quit/, and I believe that somewhere in FlexBuilder preferences there is a setting (or multiple settings) for dealing with launching multiple debug sessions. I know there's one about warning when trying to launch multiple debug sessions, try turning that off. On Wed, Oct 15, 2008 at 7:22 AM, Amy [EMAIL PROTECTED] wrote: --- In flexcoders@yahoogroups.com flexcoders%40yahoogroups.com, Nik Derewianka [EMAIL PROTECTED] wrote: Yep or close the window with the app before re-launching the debug session also works as well. FB on OSX has a lot of drawbacks - on win, the help gets its own window (so it doesn't get killed by the debugging), syntax colouring works better, images actually appear in design mode all the time, it builds a lot faster (iMac in BC spanks my mac pro in OSX), the text editor doesn't lag when doing fundamental things like selecting text. Mine does this sometimes on XP. I think that it depends on if the Help is open and how many projects you have open. -Amy
Re: [flexcoders] Re: Every second time I debug my app, Flex closes Safari :(
FB on OSX has a lot of drawbacks - on win, the help gets its own window (so it doesn't get killed by the debugging), syntax colouring works better, images actually appear in design mode all the time, it builds a lot faster (iMac in BC spanks my mac pro in OSX), the text editor doesn't lag when doing fundamental things like selecting text. Oh and I love it when FB seems to get confused and tries to launch a debug session but in reality it's just sitting there and waiting to time out. At least embedded fonts still disappear on both platforms in between compiles for no apparent reason so I don't feel completely screwed over. Just wanted to say, yes. I experience all these issues as well on OSX. All of my other development tools tend to work better on OSX, but Flex... nope. I used it for a long time under Parallels, but switching back and forth between Windows-style keyboard shortcuts and OSX-style keyboard shortcuts was driving me crazy. So, I *like* having a native OSX app... I just don't understand why it has to be crappier than the Windows version? And, to add insult to injury, I found that FB3 was *worse* on OSX than FB2 was... very frustrating! Troy.
Re: [flexcoders] Re: Every second time I debug my app, Flex closes Safari :(
To quote a Monty Python sketch, Luxury! Us Linux guys have no profiler, no refactoring, no designer, features like Find all references simply don't (sure, they find *some* references, but often enough not all), symlinks confuse the heck our of FB, and the current (fourth!) alpha lasts another 412 days, meaning that we probably won't have major improvements before then. It would be really nice to have FlexBuilder truly cross-platform. Eclipse itself seems to do it reasonably well. I certainly appreciate the effort at Linux support (the interactive debugging is great), but it would be nice if cross-platform support were taken more seriously, and not just used as a feature bullet point. -- Maciek Sakrejda Truviso, Inc. http://www.truviso.com -Original Message- From: Troy Gilbert [EMAIL PROTECTED] Reply-To: flexcoders@yahoogroups.com To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Every second time I debug my app, Flex closes Safari :( Date: Wed, 15 Oct 2008 11:13:20 -0500 FB on OSX has a lot of drawbacks - on win, the help gets its own window (so it doesn't get killed by the debugging), syntax colouring works better, images actually appear in design mode all the time, it builds a lot faster (iMac in BC spanks my mac pro in OSX), the text editor doesn't lag when doing fundamental things like selecting text. Oh and I love it when FB seems to get confused and tries to launch a debug session but in reality it's just sitting there and waiting to time out. At least embedded fonts still disappear on both platforms in between compiles for no apparent reason so I don't feel completely screwed over. Just wanted to say, yes. I experience all these issues as well on OSX. All of my other development tools tend to work better on OSX, but Flex... nope. I used it for a long time under Parallels, but switching back and forth between Windows-style keyboard shortcuts and OSX-style keyboard shortcuts was driving me crazy. So, I *like* having a native OSX app... I just don't understand why it has to be crappier than the Windows version? And, to add insult to injury, I found that FB3 was *worse* on OSX than FB2 was... very frustrating! Troy.
Re: [flexcoders] Re: Every second time I debug my app, Flex closes Safari :(
It would be really nice to have FlexBuilder truly cross-platform. Eclipse itself seems to do it reasonably well. You know, if someone ported FlashDevelop to OSX/Linux, it would really put the pressure on Adobe to improve their game. Also, I never use FB as a plug-in to Eclipse. But if I did, are there features of FB I'd lose as compared to the FB IDE? And if there's not, how difficult would it be to create an open-sourced FB eclipse plug-in that accomplished the same stuff (while fixing some of these problems) since MXML is freely available (and source)? Troy.
Re: [flexcoders] Re: Every second time I debug my app, Flex closes Safari :(
Well, the design view would be incredibly difficult without help from Adobe (and the state of the Linux Builder shows even with their help), as it's (as far as I can tell) a customised version of Player that's glued in with JNI. The rest of the features are pretty standard, and Idea 8 shows it can be done (although I can't for the life of me make the debugger work). -Josh On Thu, Oct 16, 2008 at 4:32 AM, Troy Gilbert [EMAIL PROTECTED]wrote: It would be really nice to have FlexBuilder truly cross-platform. Eclipse itself seems to do it reasonably well. You know, if someone ported FlashDevelop to OSX/Linux, it would really put the pressure on Adobe to improve their game. Also, I never use FB as a plug-in to Eclipse. But if I did, are there features of FB I'd lose as compared to the FB IDE? And if there's not, how difficult would it be to create an open-sourced FB eclipse plug-in that accomplished the same stuff (while fixing some of these problems) since MXML is freely available (and source)? Troy. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Alternative FAQ location: https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] :: http://flex.joshmcdonald.info/
[flexcoders] Re: Every second time I debug my app, Flex closes Safari :(
I think this happens because the debugger is still running when you start it the second time. Try pressing the red stop debugging square in flex builder to stop the debugger, and see if that fixes the problem. r --- In flexcoders@yahoogroups.com, Josh McDonald [EMAIL PROTECTED] wrote: Hey guys, In one or two workspaces, everything works fine. In most of them, however, every second time I debug an app, everything goes as normal but then Builder kills the Safari application (not just the old tab, but the entire app). This is of course *incredibly* annoying given how slow all this stuff is. Any ideas what causes this? -Josh -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] :: http://flex.joshmcdonald.info/
Re: [flexcoders] Re: Every second time I debug my app, Flex closes Safari :(
Doing that kills the entire browser process. I really can't for the life of me figure out the problem. I've had it happen from Builder and from Flex Plugin, and only in some workspaces even on the same machine :( -Josh On Wed, Oct 15, 2008 at 3:24 PM, Rob Kunkle [EMAIL PROTECTED] wrote: I think this happens because the debugger is still running when you start it the second time. Try pressing the red stop debugging square in flex builder to stop the debugger, and see if that fixes the problem. r --- In flexcoders@yahoogroups.com, Josh McDonald [EMAIL PROTECTED] wrote: Hey guys, In one or two workspaces, everything works fine. In most of them, however, every second time I debug an app, everything goes as normal but then Builder kills the Safari application (not just the old tab, but the entire app). This is of course *incredibly* annoying given how slow all this stuff is. Any ideas what causes this? -Josh -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] :: http://flex.joshmcdonald.info/ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Alternative FAQ location: https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] :: http://flex.joshmcdonald.info/
Re: [flexcoders] Re: Every second time I debug my app, Flex closes Safari :(
If I reload the app (and kill the debugging session) in the browser beforehand, then Builder will reuse the tab correctly without killing the browser. -Josh On Wed, Oct 15, 2008 at 3:41 PM, Josh McDonald [EMAIL PROTECTED] wrote: Doing that kills the entire browser process. I really can't for the life of me figure out the problem. I've had it happen from Builder and from Flex Plugin, and only in some workspaces even on the same machine :( -Josh On Wed, Oct 15, 2008 at 3:24 PM, Rob Kunkle [EMAIL PROTECTED] wrote: I think this happens because the debugger is still running when you start it the second time. Try pressing the red stop debugging square in flex builder to stop the debugger, and see if that fixes the problem. r --- In flexcoders@yahoogroups.com, Josh McDonald [EMAIL PROTECTED] wrote: Hey guys, In one or two workspaces, everything works fine. In most of them, however, every second time I debug an app, everything goes as normal but then Builder kills the Safari application (not just the old tab, but the entire app). This is of course *incredibly* annoying given how slow all this stuff is. Any ideas what causes this? -Josh -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] :: http://flex.joshmcdonald.info/ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Alternative FAQ location: https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] :: http://flex.joshmcdonald.info/ -- Therefore, send not to know For whom the bell tolls. It tolls for thee. Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] :: http://flex.joshmcdonald.info/
