| Marker object contributions no longer work in 3.4 [message #328242] |
Mon, 19 May 2008 15:59  |
Eclipse User |
|
|
|
Originally posted by: george.adobe.com
Hey all,
We have a few object contributions to objectClass
org.eclipse.core.resources.IMarker so that we can add a couple of
custom menu items to the context menu of some errors in the problems
view from our builder. This worked great in eclipse pre-3.4 but now
seems to be broken. The problem appears to be that the selection items
are no longer markers but a new internal class to 3.4 called
MarkerEntry. It seems wrong to use this as the class to make an object
contribution to and even if i do it still doesn't work because i can't
filter the contribution based on properties of the marker like i could
before (using visibility specifier on object state for type, severity,
etc). Is there a different way I should be doing this for Eclipse 3.4??
I also found it very limiting even in 3.3 that i couldn't filter the
visibility based on custom attributes of the marker but only on a set
of like 4 baked in ones like type, severity, and message, but i'll take
it how it was before over not working at all..
any thoughts?
thanks!,
-george
|
|
|
| Re: Marker object contributions no longer work in 3.4 [message #328409 is a reply to message #328242] |
Sat, 24 May 2008 02:48  |
| Eclipse User |
|
|
|
George Comninos wrote:
> Hey all,
> We have a few object contributions to objectClass
> org.eclipse.core.resources.IMarker so that we can add a couple of
> custom menu items to the context menu of some errors in the problems
> view from our builder. This worked great in eclipse pre-3.4 but now
> seems to be broken. The problem appears to be that the selection items
> are no longer markers but a new internal class to 3.4 called
> MarkerEntry. It seems wrong to use this as the class to make an object
> contribution to and even if i do it still doesn't work because i can't
> filter the contribution based on properties of the marker like i could
> before (using visibility specifier on object state for type, severity,
> etc). Is there a different way I should be doing this for Eclipse
> 3.4?? I also found it very limiting even in 3.3 that i couldn't filter
> the visibility based on custom attributes of the marker but only on a
> set of like 4 baked in ones like type, severity, and message, but i'll
> take it how it was before over not working at all..
> any thoughts?
File a bug report.
Dani
> thanks!,
> -george
>
|
|
|
Powered by
FUDForum. Page generated in 0.03300 seconds
Home