|
Bugzilla – Full Text Bug Listing |
| Summary: | Better placing of 'Implement Interface' command | ||
|---|---|---|---|
| Product: | [Mono] MonoDevelop | Reporter: | Alan McGovern <amcgovern> |
| Component: | texteditor | Assignee: | Mike Krueger <mkrueger> |
| Status: | RESOLVED FIXED | QA Contact: | MD Bugs <monodevelop-bugs> |
| Severity: | Enhancement | ||
| Priority: | P3 - Medium | CC: | alan.mcgovern |
| Version: | 0.10 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Thomas Wiest
2007-09-15 20:50:02 UTC
This is not trivial to implement because the parser service does not provide information about the context surrounding a language item. That is, it can give the type of a given identifier, but it can't tell if this identifier is in a base class declaration, a variable declaration or a type cast, and this information would be needed to implement what you propose. Maybe someday we'll improve the type resolver. Setting to enhancement meanwhile. *** Bug 376141 has been marked as a duplicate of this bug. *** *** Bug 369984 has been marked as a duplicate of this bug. *** This issue is important to fix. My wife had the same problem using this function and I remember that I did ran into it when I was new to monodevelop too. Let's see, if something can be done to solve it. Implemented. I've left the 'old way' in the context menu of the types. I don't think that it does hurt there. |