| Summary: | Promptable filter's shouldn't require supportsCommands on the subsystem to be false | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] Target Management | Reporter: | Kevin Doyle <kjdoyle> | ||||
| Component: | RSE | Assignee: | David McKnight <dmcknigh> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Martin Oberhuber <mober.at+eclipse> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | kjdoyle, rdibugs | ||||
| Version: | 3.0.1 | ||||||
| Target Milestone: | 3.1 M3 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 254641 | ||||||
| Attachments: |
|
||||||
|
Description
Kevin Doyle
Kevin, just to clarify, does this defect have any bearing on bug 254605 and/or bug 249245? Is supportsCommands() still needed for determining when to show the Go Into and Show In Table actions? (In reply to comment #1) > Kevin, just to clarify, does this defect have any bearing on bug 254605 and/or > bug 249245? Is supportsCommands() still needed for determining when to show > the Go Into and Show In Table actions? Nope. Those still need to be the way they are. Created attachment 117349 [details]
patch to not use supportsCommands() when determining whether to prompt
Kevin, does this patch resolve this?
Yes, that fixes the issue. We need this backported as well. I've committed this to cvs and opened backport bug 254641. |