Here's the jinx: Disabling Symantec Anti-Virus seems to have fixed it. Can't believe I didn't think of this earlier...
Thanks a bunch for the good ideas! Steve --- In [email protected], "steve.baney" <[EMAIL PROTECTED]> wrote: > > I thought I had this figured out, but apparently the issues run deeper > than I thought. > > I'm running: > > Eclipse Platform > Version: 3.3.2 > Build id: M20080221-1800 > > Flex Builder Plug-In Version 3.0 (build 3.0.194161) > > Flex 3.0 SDK > or > Flex 3.0.0.477 SDK > > When I pull a fresh copy of my program from my CVS repository > everything seems to be fine, but as I work on it several Eclipse/Flex > Builder features stop working. > > Syntax checking breaks just as it was in my earlier post ( > http://tech.groups.yahoo.com/group/flexcoders/message/117968 ) > > The 'References' option in the right-click menu only finds the first > couple of instances, then ignores the rest. > > I'm sure this is an issue with my program, as I've reproduced it > across several installs from fresh downloads and on two different > computers, as well as in the standalone Flex Builder. > > I'm not changing anything other than adding lines of code to a freshly > checked out copy of my project (which works fine when I first check it > out) when this occurs. It doesn't seem to matter what code I'm > entering, as I fixed this issue the first time by reverting to an > older version, and then adding the code from the broken copy, testing > it after each line I added, and then making a new branch once I got > the project updated and functioning with the new code. Now when I > check that branch out it works, until I start coding again. > > The only related issue I could find (and it's a bit of a stretch) is this > > http://tech.groups.yahoo.com/group/flexcoders/message/105055 > > So I tried deleting any unnecessary files in /bin to no avail. I'm > not positive on what I can and can't delete from /bin tho, so I may be > leaving whatever is messing me up. > > I'm pretty stumped here, and my last post didn't get much response, so > I'm thinking this is a really obscure issue. This is killing my > production schedule though, so if anyone has any ideas, thoughts, > reflections, comments, commiseration, or whatever over the weekend > please drop me a line. > > Thank You! > Steve >
