Bug 149139 - [Contributions] PropertyDialogAction enabled when there are no applicable property pages
Summary: [Contributions] PropertyDialogAction enabled when there are no applicable pro...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 148424
  Show dependency tree
 
Reported: 2006-06-29 08:26 EDT by Kevin Barnes CLA
Modified: 2019-09-06 15:35 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Barnes CLA 2006-06-29 08:26:06 EDT 
In the debug view we're contributing a vm capabilities property page. We'd like the page to be enabled based solely on a property tester. This mostly works already, however if a launch is selected the property dialog action is enabled even though there are no property pages, leading to an error dialog with a confusing message. Seems that the property testers should be checked when deciding the enablement of the action.
Comment 1 Paul Webster CLA 2007-04-05 19:05:17 EDT 
Assigning to component owner
PW
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:31:13 EDT 
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.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:35:31 EDT 
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.