|
|
|
[
Permlink
| « Hide
]
jeff tapper - [02/08/08 09:34 PM ]
What was the fix for this issue?
This issue is not a Flex issue. It's a decision on the side of the AIR team. A bug has been filed in their database.
Can we get a link to the bug? I haven't been able to find it...
Is there an Adobe AIR bugbase? If so: Could we get the link? The bug still exists in Adobe AIR 1.5.1
I've been watching this issue for about 6 months now and am amazed that there's been no official comment other than to say, "yes we know".
It's the reason I'm not using AIR applications on a daily basis, as everytime I want to work on Flash (which being a Flash developer, is funnily enough every day) I have to close down all the AIR apps that I'm running. Further to this, there's some great debugging tools out there built in AIR - but ironically as they're built in AIR they can't access the flashlog.txt file. Which is kinda stoopid, give that's these debugging tools primary purpose. So come on Adobe, what gives with the decision to lock the file? And can we get around this? Is this issue already fixed? When the release is going to come out?
Since this was closed and AIR does not have a public bug system I opened one in Flash Player:
https://bugs.adobe.com/jira/browse/FP-2163 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||