This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Usability of Features in fresh 6.7.1 installation | ||
---|---|---|---|
Product: | platform | Reporter: | ats37 <ats37> |
Component: | Plugin Manager | Assignee: | dlipin <dlipin> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | jtulach, olangr |
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
ats37
2009-08-11 14:17:50 UTC
Actually, thinking about it, asides from the other categories' modules being described as "to be installed" rather than activated, the only real problem with the rest is that the "greyed out" inactive features and modules are completely disabled including (and especially) the Select checkboxes. I can understand the desire to differentiate them visually from the active ones, and giving them a "disabled" appearance kind of makes sense. The problem is that, although the module/feature is disabled, the checkbox/row in the table should not be (since it still needs to be possible to interact with it). Thanks for detailed description of your inquiry. I'll try to reproduce it tomorrow, but from what I can say, the problem is in shared installation. Somehow the Installed tab disables the checkboxes. Strange, I thought it was already reported and fixed as bug 165841. The trouble is that due to some mistake, the fix was not probably integrated into 6.7 release. *** This issue has been marked as a duplicate of 165841 *** Looks like it is something to do with shared installation; I ran netbeans with "sudo /usr/local/share/netbeans-6.7.1/bin/netbeans" and things worked okay; the feature names were in bold and the Select checkboxes were enabled. Should I raise a separate report about the message saying "installed" rather than "activated" for the other category's modules, or is that likely to be related? (i.e. without the user/permissions problem, it wouldn't have done that anyway) I just tried to reproduce the problem and imho, the primary issue is that you need to check at least one checkbox before trying to activate/deactivate a module. I admit that having a popup menu that needs its item to be checked before showing it to really work, is sort of unnatural. This is at least for the second time I see similar confusion. I am not sure what could be done with it, but I am CCing Ondra to provide some advices. ats37: If checking the checkbox workarounds your hassle, then the bug is not P1, in fact it is a feature and not a bug. But feel free to report another P3 usability bug. |