Community
Participate
Working Groups
I20051004-0800 Could you move the marker limits option (view menu > Preferences) to the Filters dialog as well? I'd like to set marker limits per filter, not globally. Use case: 1) normal development: on any element, show only errors, limit: 100 errors 2) fixing nls/deprecation/etc. warnings: on any element in same project, show all severities, limit: none In older builds I could switch this on one page. Now, I always have to open two dialogs.
How do you reconcile 2 filters with different marker limits? The purpose of the limits is to limit the markers shown for performance reasons so it does not belong to a particular filter.
> How do you reconcile 2 filters with different marker limits? Take the largest number (or all, if the limit is disabled in one filter). This is the same as if you have a filter "On any element" and one "On selected element only" -> result is to take the larger set. > The purpose of the limits is to limit the markers shown for performance > reasons so it does not belong to a particular filter. In my use case, it does: during normal development, I'm only interested in global errors and it's nice that I can limit the Problems view's CPU consumption. When I hunt for special kinds of warnings, I don't care about performance - I want them all.
*** This bug has been marked as a duplicate of 124883 ***
Sorry, but this is not a dup of bug 124883. The problem here is independent from grouping, and I still have to open two dialogs to switch between my two main usage patterns.
Marker limits are on the preference page of the new markers view.
Verified in I20071029-0100
Sorry, this is not fixed. The new preference is at odds with the trend to move view-specific preferences to the view (to avoid cluttering the Preferences dialog). Moreover, I still have to open two configuration dialogs to change the filters and the limit.
I'm going to mark this as FIXED so that I can track the bug you were reporting (which was a code error). I have logged bug 209017 for you for this other issue.
Verified in Version: 3.4.0 Build id: I20071210-0930
There's no reason for this enhancement request to be closed, since comment 0 has not been addressed at all. Clarified subject to talk explicitly about separate marker limits *per filter*.
Requires some rework.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
