Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <25871672.1194913550574.JavaMail.jira@brutus>
Date: Mon, 12 Nov 2007 16:25:50 -0800 (PST)
From: "Alan Batie (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Commented: (DIRSTUDIO-234) Greyed out menu items should have
 a tool tip explaining *why* they're greyed out
In-Reply-To: <10806143.1194899030647.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DIRSTUDIO-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542001 ] 

Alan Batie commented on DIRSTUDIO-234:
--------------------------------------

The third option is certainly the most user friendly one.

However, in this case, something is changing and I don't know what.  Specifically, we're doing some mail routing with the standard sendmail schema.  I used Directory Studio to remove one sendmailMTAClassValue attribute from a sendmailMTAClassName entry.  This worked once, and then while doing another search, the results started coming back italicized, which I'm guessing means non-editable.  The parent entry *is* still editable, just not the member attributes.  It acts like it's locked or something, i.e. an operational decision rather than a structural decision from a schema interpretation.

> Greyed out menu items should have a tool tip explaining *why* they're greyed out
> --------------------------------------------------------------------------------
>
>                 Key: DIRSTUDIO-234
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-234
>             Project: Directory Studio
>          Issue Type: Improvement
>          Components: studio-ldapbrowser
>    Affects Versions: 1.0.1
>         Environment: OSX 10.4
>            Reporter: Alan Batie
>
> All GUIs should have a tool tip explaining why something is greyed out and what needs to be done to make it active (and it needs to be *useful* information, not just "it doesn't apply" or "you're not allowed to do that now" --- it's obvious the *application* thinks that because it's greyed out).  In this case, I did a search against our ldap server, found an attribute that needed removing and did so.  Then I did another search.  This time the font changed to italic, and when I go to delete an attribute, Delete is greyed out.  There is no clue anywhere as to what's going on.  I searched in help for the ldap browser, and found very little.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.