Stefan Seelmann commented on DIRSTUDIO-1115:

The text editor is only meant for string attributes (e.g. Directory String 
attributes), but also works for binary attributes if it can be UTF-8 decoded to 
a string. (There is some inconsistency in handling binary values that I'll fix.)

But in your case, if the encoding is unknown, we would need a more enhanced 
editor where you can choose the encoding in the editor windows and then the 
editor tries to decode the value and let you edit it.

> Value editor settings are not used and the menu displays wrong entries
> ----------------------------------------------------------------------
>                 Key: DIRSTUDIO-1115
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1115
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-ldapbrowser
>    Affects Versions: 2.0.0-M10 (2.0.0.v20151221-M10)
>         Environment: Windows 7 x64
> Linux Debian 8.5 x64
>            Reporter: Nagy Attila
>            Priority: Minor
> The following two issues are really close related to each other, so I'm 
> reporting them here together. If they should be reported separately, then 
> please indicate so, and I'll separate them.
> I was trying to set custom value editor for some attributes (vacationInfo 
> octet stream) when I discovered that the settings are ignored. I added a new 
> entry into Value Editors (Eclipse Preferences -> LDAP Browser -> Value 
> Editors):
> attribute: vacationInfo
> value editor: "Text Editor"
> Applied the settings (even restarted Eclipse) but on double clicking a 
> vacationInfo attribute nothing happens, not even if I right click and select 
> "Edit Value". The only way to edit the attribute value is to right click the 
> attribute, select "Edit Value With" and there selecting "Hex Editor".
> While I was messing with these settings I noticed that the "Edit Value With" 
> submenu contains a changing entry (top one, besides the alternative editors 
> and the "Preferences..." one) which as I found out is the entry corresponding 
> to the previously selected attribute. So if selecting a password, afterwards 
> selecting a string attribute  and then looking into the "Edit Value With" 
> submenu, it will contain a "Password Editor" entry which will do nothing. And 
> sometimes it does really weird things.
> Eg:
> Selecting a Boolean and afterwards a Password: the "Boolean Editor" entry is 
> displayed but it opens the "Password Editor".
> Selecting a Password and afterwards a Boolean: the "Password Editor" entry is 
> displayed but it opens the "In-Place text Editor".

This message was sent by Atlassian JIRA

Reply via email to