Community
Participate
Working Groups
Task stays active after switching Eclipse workspace if both workspaces share the same .mylar folder. This is quite critical, because projects may disappear, or even worse, workspace has completely different projects under the same names. It probably would be better if active task saved info within workspace data.
I don't see how this is critical because it does not cause any damage to the Task List, contexts, or workspace, nor does it cause any crashes. Our entire architecture currently relies on the task activation data being stored in the task list, and this is where we get our history list as well as task timings. But I agree that we have a problem with the current story of sharing Mylar across workspaces (bug 130658). We need to wait for progress on Platform bug 154097 to figure out how to best resolve that. The current work-around for this particular problem is to deactivate the active task before switching workspaces. Btw, could you mention more about your use case for switching workspaces?
You can't rely on users remembering things like deactivate tasks before doing something. It is critical because task view may not be in focus, so it is easy to screw task context after switching workspace.
Is there any problem in activating a task in a workspace with whose projects doesn't belong to it? i.e. there can be some type of "damage" to the context data?
Activating is not a problem. The problem is that context will be updated with unrelated events.
Our current model is that the active task is saved with the Task List, note with the workspace. The benefit of this is that importing task data or switching workspaces preserves the exact state that the task list was left in, including the active task. I believe that more users would complain if they imported or switched workspaces and their active task was not preserved. However, this is a design decision that could be revisited with more input.
