| Summary: | hovering over the context menu item 'Run' takes too much time | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Raj Mandayam <ramanday> |
| Component: | Debug | Assignee: | Platform-Debug-Inbox <platform-debug-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | hudsonr, jbr, quartz12h |
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Raj Mandayam
I do not see this delay, but maybe my machine is fast? Forwarding report to Debug UI in case they're doing something expensive whenever this submenu is created. *** Bug 65966 has been marked as a duplicate of this bug. *** Yes - we are doing something expensive when the menu is created. However, we only take the hit when the user wants to expand the menu. This is by design, and currently, there is not much we can do to improve it - this is the complexity/cost of context sensitive launching. actually as I had said before I wanted to select the option 'Compare with' but depending on how fast you move the mouse pointer over other options to that option ,you can cause the Run menu to expand even without clicking on it. Nothing planned for 3.0 *** Bug 70752 has been marked as a duplicate of this bug. *** how about a simple read-cache of that info... It is already in memory anyway... The favorites at least because the toolbar has it. And if it is about discovering if the class has a main or not, this could be done much later, when the user actually click the launch. No need to fetch anything to display a run/debug menu item... This has been addressed in 3.1 Marking as dup of bug 78503, that addressed the problem. *** This bug has been marked as a duplicate of 78503 *** closed |