Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313237 - [ui] category checkmark selection in the available software dialog not really responsive
Summary: [ui] category checkmark selection in the available software dialog not really...
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.6   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-17 16:29 EDT by Pascal Rapicault CLA
Modified: 2019-09-25 15:37 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Rapicault CLA 2010-05-17 16:29:00 EDT
When I browse the helios repository and select a category, the time it takes to enable the check mark seems rather long compared to selecting something in other places in the eclipse ui.
Therefore I'm wondering if there is not some heavy computation going on.
Comment 1 Susan McCourt CLA 2010-05-17 16:37:18 EDT
I observe:
- it's slower if you do it without the category expanded (this isn't too shocking I think)
- it's still "heavy" feeling once items have been expanded.  One can definitely see that the check mark of an expanded category is taking longer than the corresponding uncheck mark.  

I suspect somewhere someone is going to the content provider for children (which does a query) rather than just manipulating the viewer model
Comment 2 Susan McCourt CLA 2010-05-17 16:38:08 EDT
it also feels like there's a defer redraw in play.
If one were to see the checkmarks ripple, it would feel faster than having a subsecond-pause followed by the appearance of all checkmarks.
Comment 3 Eclipse Genie CLA 2019-09-25 15:37:15 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.