Community
Participate
Working Groups
3.2 M6 The problems view updates itself in the background. During the last weeks I was confused quite a few times due to a log delay till the problems view responded to changes in the workspace. However, I was never able to track this down. Today I made another observation, which I believe is worthwhile to report here. I had a Java source file in my workspace with 3 compile errors (fatal problems, grouping is on). I simply deleted the file and then was confused again because the problems view still showed the problems. I remembered that I saw this behavior in the past. Thus I decided to simply wait and watch this time. In the past I often tried a "clean" to force a rebuild. I waited approximately 20 seconds till the problems were removed from the view. The interesting thing is that the view title did not indicate any ongoing activity. Usually it's cursive to indicate ongoing update work. There was no activity on my laptop during the 20 seconds. Thus, I don't know what caused the delay. I also noted, the no build was caused by the deletion of the compilation unit (at least the progress monitor didn't show an ongoing build and there was no hard disk activity). I think it's hard to track this down but it does cause quite a bit confusion to an end user.
This is due to problems with the auto build complete not always coming in. In M6 I put in a 30 second wait before I force an update - until we can track down whene this is missing this will happen sometimes. There was a problem with no updates on an exception which John fixed - do you have anything in your log? One thing I have not done is set the cursor to busy while the calculation is going on - I will add a showForFamily for the marker update jobs.
(In reply to comment #1) > There was a problem with no updates on an exception > which John fixed - do you have anything in your log? No, there is no entry in the log file.
Fixed in build >20060404 to show busy while calculating updates. I have also fixed up some places where we weren't looking for a null progress service.
Verified in 20060425
