Community
Participate
Working Groups
It looks like the "Unmatched" category does not show the incoming arrow if it has incoming tasks, neither expanded or collapsed.
Created attachment 87443 [details] Screenshot
Rob: this is because the UnmatchedContainer class (I just renamed it) doesn't store synchronization state. For the corresponding rendering code see the landmark in the attached context.
Fixed.
Created attachment 88154 [details] mylyn/context/zip
Almost fixed. It doesn't work when in focused mode (build I20080203-2200).
This is by design. All containers in the task list don't reveal incoming state when in focused mode. The reasoning for this was that when in focused mode, tasks with incoming are revealed making the additional incoming on the query redundant. There was a large design discussion about this on another bug report that escapes me at the moment. Let me know if you would like to read up on it and I will track it down for you.
Well... I have an bugzilla query here that shows the incoming icon when collapsed in focused mode. Anyway, I particularly don't get why it has to be different in focused mode. It doesn't hurt to be the same as the normal presentation. If you remember the bug number where there was this discussion, please post here.
Created attachment 88926 [details] Screenshot
Mik, do you recall where this conversation took place?
We remove them in focused mode because they are redundant when the container is expanded, i.e. you will always see the arrow underneath the query if the query has an incoming. That's not the case in unfocused mode, where there could be an item that has an incoming filtered.