This feat has been requested previously, its on our todo list.
Re: Find and Replace in File Top Folder History
↧
↧
Re: Split view vertically - Edit/compare multiple files at once
I think this should be a plugin or a script.
↧
Re: Show and hide output panel together with debugger
Please log this suggestion to github.
↧
Re: Improve debugger theme-ability
On todo list.
↧
Re: Style the output panel scrollbar according to current theme
On our todo list, if possible.
↧
↧
Re: Refactor rename behavior request
Please log this to github.
↧
Re: AppMan doesn't install AIR 18 SDK
Update coming soon.
↧
Re: lost mouseover property debugging in FD5
Please log this issue to github with all the details you can come up with.
↧
Re: Recognition of imported Classes
Please log this to github.
↧
↧
Re: Bug with autocomplete by mouse click
Please log this to github.
↧
Re: Compiler constants should be read after the prebuild scripts
Please log this to github.
↧
Re: AppMan doesn't work
Still not working?
↧
Re: AppMan doesn't work
I gave up trying to get it to work and just installed the updates I needed manually.
I've just tried launching it now though and I get something very different to before (despite not updating anything as far as I'm aware).
I get an error: Could not find file appman\Config.xml
If I click OK on that I get another error: Null reference exception at AppMan.MainForm.PopulateListView()
If I click OK on that AppMan does appear but it is empty. So that appears to be a significant improvement to before and presumably hinges on this missing Config file?
I've just tried launching it now though and I get something very different to before (despite not updating anything as far as I'm aware).
I get an error: Could not find file appman\Config.xml
If I click OK on that I get another error: Null reference exception at AppMan.MainForm.PopulateListView()
If I click OK on that AppMan does appear but it is empty. So that appears to be a significant improvement to before and presumably hinges on this missing Config file?
↧
↧
Re: AppMan doesn't work
Try putting these files in place manually:
https://github.com/fdorg/flashdevelop/t ... ols/appman
https://github.com/fdorg/flashdevelop/t ... ols/appman
↧
Re: AppMan doesn't work
Yep, that sorted it, it works fine now, thanks!
↧
Re: Show and hide output panel together with debugger
Already added
https://github.com/fdorg/flashdevelop/issues/836
https://github.com/fdorg/flashdevelop/issues/836
↧
Re: Improve debugger theme-ability
Lovely!
↧
↧
Re: Style the output panel scrollbar according to current theme
It's not high priority for me, but if it's easy to do, would be great!
↧
Re: Community testing release for FlashDevelop 5
Highlight Matching Words delay indeed works after a restart. However with my current theme colors, it's almost invisible. The color needs to be customizable (or use quick-find's highlight all color). And I think delay should be able to set to 0 ms.
"Disable Highlight Guide" - can you illustrate the difference between true and false with a couple of screenshots? I've tried this and that and can't see any difference in the indent guides.
"Disable Highlight Guide" - can you illustrate the difference between true and false with a couple of screenshots? I've tried this and that and can't see any difference in the indent guides.
↧
Display runtime errors (target neko)
Hello,
I am brand new using FlashDevelop and still learning OpenFL.
I was experimenting some OpenFL tutorial when i stumbled upon a frustrating problem: no runtime error (exception stack trace) is displayed in FlashDevelop.
My target is neko (on windows 7) and launching my program in a terminal displays the exception trace correctly.
I didn't find any option to display the runtime output but i would expect this is something enabled by default, right? (who in their right mind would not want to see the error location ???)
I actually installed FD for quite some time without using it and updated it (along with OpenFL) yesterday, maybe this is an update problem ?
Any thoughts about what could be wrong or did I miss something ?
I am brand new using FlashDevelop and still learning OpenFL.
I was experimenting some OpenFL tutorial when i stumbled upon a frustrating problem: no runtime error (exception stack trace) is displayed in FlashDevelop.
My target is neko (on windows 7) and launching my program in a terminal displays the exception trace correctly.
I didn't find any option to display the runtime output but i would expect this is something enabled by default, right? (who in their right mind would not want to see the error location ???)
I actually installed FD for quite some time without using it and updated it (along with OpenFL) yesterday, maybe this is an update problem ?
Any thoughts about what could be wrong or did I miss something ?
↧