Community
Participate
Working Groups
PropertyDialog#createDialogOn(...) presents bad messages if it is called with an object which does not adapt to IWorkbenchAdapter. If no property pages are found for the object, a message dialog is opened which reads: "No property pages found for ." If property pages *are* found for the object, the property dialog is opened with the title: "Properties for" If a valid name cannot be determined for the object, these messages should read: "No property pages found." "Properties"
The "Properties for" case can e.g. be observed when File > Properties is called when an editor is active.
Created attachment 112716 [details] Patch to make changes from description This patch adds two messages: PropertyDialog_noNameNoPropertyMessage PropertyDialog_noNamePropertyMessage and changes the public static method getName(Object) to return null when the object does not adapt to a IWorkbenchAdapter. I was able to test the case in the comments manually, ie File > Properties with a Editor active. But I was not able to create a situation where I could ask for properties of an object which had no property pages and was not a IWorkbenchAdapter. Feedback appreciated Trevor Kaufman
Hey, this is getting old.. Whats up here?
Reassigning to inbox.
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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.
