Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 181802 - WorkbenchWindow commands aren't useful in the monitor-log
Summary: WorkbenchWindow commands aren't useful in the monitor-log
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 2.0 M3   Edit
Assignee: Mik Kersten CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-10 13:15 EDT by meghan CLA
Modified: 2007-05-10 15:30 EDT (History)
0 users

See Also:


Attachments
mylar/context/zip (1.57 KB, application/octet-stream)
2007-05-10 15:30 EDT, Mik Kersten CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description meghan CLA 2007-04-10 13:15:12 EDT
There are a lot of commands with an origin ID like this - org.eclipse.ui.internal.WorkbenchWindow@17704280 - in the interaction log (monitor-log.xml).  These aren't terribly useful, so I'll figure out where they are coming from and either stop logging them or suppress reporting them.
Comment 1 Eugene Kuleshov CLA 2007-04-15 21:46:55 EDT
There could be a better way to retrieve more representative id for such actions, like class name.
Comment 2 Mik Kersten CLA 2007-05-10 15:30:43 EDT
These events happen for window activations (e.g. via Alt+Tab) and deactivations.  I have changed them not to include the class name, but am not removing them since they are a useful indication of how often the user is switching in and out of Eclipse.  To avoid them being overly high we now only capture activations, not deactivations.
Comment 3 Mik Kersten CLA 2007-05-10 15:30:47 EDT
Created attachment 66755 [details]
mylar/context/zip