Community
Participate
Working Groups
There has been a usecase in RCP applications where people want to use the logview but not have it activate on new events. We should consider creating a preference to control this behavior via plugin_customization.ini or other means. Something like org.eclipse.ui.views.log/ACTIVATE_ON_EVENTS or something
I think that the Preference should specify the severity level that leads to activating the logview. Currently, it activates on any event, regardless of info, warning or error. Users should be able to specify by Preference that the logview activates on Errors only, but not on warnings or info severity. The use-case for this is that plugins may log interesting information as a kind of "tracing" for debugging issues, so the logview should not pop up on such "info" logs. "Error" logs, on the other hand, point to important issues that may explain misbehavior of the program, so the logview should pop up on those. Should I file a separate defect for this?
(In reply to comment #1) > Should I file a separate defect for this? > No, it makes sense for us to support different levels in the preference setting.
interesting.
fyi, there's already a preference for activation on new events. Go to view menu and see "Activate on new events". Property is stored in workspace/.metadata/plugins/org.eclipse.core.runtime/.settings/org.eclipse.ui.logs.view.prefs and property key is activate. The problem is it doesn't work when I set in plugin_customization.ini: org.eclipse.ui.logs.view/activate=false I'm checking out why.
Created attachment 119893 [details] patch fix current preferences implementation, to correctly read default values. After this patch is released, one can add following to plugin_customization.init: org.eclipse.ui.views.log/activate=false to deactive view by default.
(In reply to comment #1) > I think that the Preference should specify the severity level that leads to > activating the logview. > > Currently, it activates on any event, regardless of info, warning or error. > Users should be able to specify by Preference that the logview activates on > Errors only, but not on warnings or info severity. The use-case for this is > that plugins may log interesting information as a kind of "tracing" for > debugging issues, so the logview should not pop up on such "info" logs. "Error" > logs, on the other hand, point to important issues that may explain misbehavior > of the program, so the logview should pop up on those. I think this kind of logic is reserved for status handling mechanism. That is if error/warning/info is important enough, then developer decides to handle it accordingly - e.g. pup up the error dialog to the user. Your scenario sounds more like fixing someone else's wrong decision that error did not popped any error dialog.
done. > 20081214 Thanks Jacek!
