It's ok, we recognize frustration when we we see it.
However, I think there is a reason for FB to change file permissions. I keep the output-bin folder in source control so it is easier to deploy to our internal servers. Usually I keep the compiled files checked out but sometimes forget. If FB did not clear the read-only attribute on the compiled files, the compile would fail. And I verified that it does definitely remove the read-only attribute from the compiled swfs, I just tested it explicitly. Tracy ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Troy Gilbert Sent: Wednesday, March 05, 2008 3:50 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Flex Builder 3: *major* bug in deleting linked folders > Wow, it really nuked the file system... I'm running on OSX, and my > htdocs folder (document root that got nuked) had all its permissions > reset to "No Access" (even though my user account is still the > owner/group). Wow, just wow. Okay, FB... forgive me for getting upset. I've had a bad day. Very stressful. Sorry if I got a little unhinged. We can get back together, right? Apparently, the only thing that FB did was to clear the permissions on the file (which makes me think it's *definitely* a bug, because I wouldn't expect FB to ever need to mess with permissions on files). When I reset the permissions all of my files re-appeared (you know, since I didn't have read-access on the directory I couldn't see its contents!). Apologies for the flaming nature of my previous e-mails... happy that it worked out okay in the end, though there's still a bug in there! ;-) Troy.
