Community
Participate
Working Groups
There is very noticeable flickering of the Package Explorer view when opening closed project, importing, or refreshing large projects with active Mylar task.
This is due to every resource becoming interesting when a project is opened, checked out, or imported, since Mylar adds every resource created by the user intereresting. I'm going to mark this down to major since there is a known work-around (which I'm frankly getting quite annoyed with): deactivate the task before hand. Scheduled for 0.5
Right, I know about it but always forgetting to do it. Also, as I recall correctly there had been suggestion to not make new projects interesting and only make new resources interesting if there are any interest in the project they belong to.
Yup, that was a very good suggestion and most likely the way this will get fixed.
*** Bug 130508 has been marked as a duplicate of this bug. ***
We can fix it by providing a method addResourceToContext(List<IResource>) for ResourceInterestUpdater and do some other changes. If so, we can refresh it only once.
This has now been resolved by making mylar.ide.ResourceChangeMonitor batch interest updated for the entire resource delta, rather than issuing seperate events (and a method similar to what Wang suggests was added). However, note that opening a new project will still make every resource in that project interesting (just not result in flicker). The suggested work-around in comment#2 is problematic because it breaks the case of moving a resource to an uninteresting project (e.g. via Refactor -> Move), so we're stuck with the policy: if a resource is created when a context is active, it becomes interesting (I'm going to add this to a tips & tricks doc). But on the bright side it's quick to right-click the project and mark it uninteresting, and even if that's not done the interesting resources will decay quickly. So we should still watch over this but the behavior should be much better now.
