Bug 264183 - [plug-in registry] slow filter response
Summary: [plug-in registry] slow filter response
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: investigate
: 344595 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-02-09 09:32 EST by Krzysztof Daniel CLA
Modified: 2023-08-30 03:35 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Krzysztof Daniel CLA 2009-02-09 09:32:30 EST
Let's consider following scenario:

1. empty filter - 1000 items
2. some text typed - 300 items
3. more text appended - 10 items

It seems that in step 3 all 1000 items is taken into account. I believe that it should be easy enough to determine that new text has been appended in step 3 and take into account only 300 previously found items.
Comment 1 Jacek Pospychala CLA 2009-04-22 11:29:17 EDT
yea this is cool enhancement.
Unfortunately I believe it's jface FilteredTree who is responsible for search.
We just give a simple pattern class, that answers YES/NO to tell whether item is filtered or not.

our real problem is that now view has a real lot of data - so it takes time to go thru all of it.
Comment 2 Curtis Windatt CLA 2011-05-03 11:43:07 EDT
*** Bug 344595 has been marked as a duplicate of this bug. ***
Comment 3 Eclipse Genie CLA 2019-09-17 13:43:57 EDT
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.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2021-09-08 13:37:18 EDT
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.

--
The automated Eclipse Genie.
Comment 5 Eclipse Genie CLA 2023-08-30 03:35:01 EDT
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.

--
The automated Eclipse Genie.