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.
If you click the "..." button for a disabled property with a string value, you get an editor which allows you to make changes. However, once you ok those changes, they are ignored. It's nice that the user can open this editor because it makes an easy way to view long strings without having the expand the properties window, but allowing the user to edit and then ignoring these changes is misleading. The basic string editor for all such properties in the IDE should be passed the "uneditable" state, and should not allow editing.
The problem was fixed for String editor. In general this problem is hard to solve as this feature is not supported in Java Beans specification. Using NetBeans extensions it is possible to solve it for other NetBeans based custom property editors (using ExPropertyEditor...). To harmonize this functionality within whole IDE, this changes should be done also for all modules, which introduce new custom property editors (if not working this way yet). In case of further problems issue request for enhancement please.
I would like to see the text area in the popup have a gray background instead of a white one.
My comment about gray vs. white still needs to be addressed.
I have added this (to StringCustomEditor): textArea.setEnabled(editor.isEditable()); It makes the area disabled --- I hope that LookAndFeel takes care of colors. Probably wouldn't be wise to fiddle with colors directly. Marking as fixed. If you have better idea please propose another solution. Thanks for your comments.
I think you should use setEditable instead of setEnabled otherwise I think copy/paste won't work.
SetEditable was there before and you didn't like it. So a added setEnabled (right after setEditable).
Sorry. I guess the goal is: disabled text color + copy/paste support. Why don't you check for the correct behavior on nbui?
New behaviour is adequate to me. If you think so, please mark this as verified, thanks.
I agree that the goal here should be that the background color should indicate that it is disabled, but we need to allow copy/paste. I confirmed with Dirk Ruiz about how this should work. We need to get rid of the setEnable call so that text can be copied. As for the background color, it should be set to the window background color. This will make it gray in most cases, but will respond to the L&F settings if window backgrounds are some other color.
This seems to me more like a bug, then an enhancement. It disables some functionality. In VCS there are many RO properties, that contain valuable information. I would like to see it fixed in 3.3. IMHO the TextArea should not be disabled, to allow copy, setEditable should be enough. Just the color can be changed if it's needed to emphasise, that it can not be changed (I agree with Jan Benway at this point).
Changing to DEFECT, since it's a defect in functionality.
Background Color is ok. Just the text color should be changed from black to gray, that's all.
Fixed.
*** Issue 15135 has been marked as a duplicate of this issue. ***
no more comments ? marking as verified. I hope that you all will agree ;)
The colors still aren't right. The background should be gray and the text should be black. Right now, the background is white and the text is gray. When you select text, then it turns black.
Jan, I'm closing this issue. Seems that default colors for disabled textArea are white background and gray foreground, so I think it should follow the defaults. If you don't agree, please let discuss the problem at [nbui] so we get what audience wants.
Nbui discussion took place on this thread: http://www.netbeans.org/servlets/ReadMsg?msgId=181371&listName=nbui Consensus was that people thought that the colors should be changed. There were no objections to my proposal to use textfield colors for this. I posted a summary/last call message on Nov 12th, but it seems to be missing from the archives. Here is what it said: I'd like to try to wrap up this thread, which started with this message: http://www.netbeans.org/servlets/ReadMsg?msgId=181371&listName=nbui The proposal is to make the text areas in disabled string editors appear the same as disabled text fields (typically gray background with black text). In the discussion on this topic, there was general agreement that the current colors were not acceptable. There were a number of alternative solutions suggested, but I didn't hear any disagreement on the proposal. Therefore, I propose that we go ahead and change the colors for this text area to match those of text fields. Any further discussion? If there are no objections by Wednesday, I will update the bug with this solution. Thanks, Jan Benway HIE
Jan, I would love to have this bug fixed. But I have no idea what you mean by "the same as disabled text fields". Your "typically ..." is not very helpfull since those values can vary significantly across L&Fs. Moreover (and please correct me if I am wrong) in Metal Look and Feel the colors for disabled textfields are exactly the same as the colors used in the custom panel now.Please reopen and state what colors should be there (please don't send in any RGB but rather entries in swing palette from the colors dialog or at leat any place in the IDE where those are used). Don't you by chance know a UI engineer who would like to volunteer on this issue? It would be better if someone who closely watch the nbui list would do such changes. The change should be extremely easy in org.netbeans.beaninfo.editors.StringCustomEditor. Thanks.
x
Jano is working on accesibility in the org.netbeans.beaninfo.editors package - so assigning to him. It is in StringCustomEditor.
Target milestone -> 3.3.1.
Target milestone -> 3.4
It's an editor issue I reassing to Ales.
Fixed in trunk. BTW: I also don't aggree with such ugly workarounds.. JTextArea is not JTextField, so why it should behave like it?
verified in [nb_dev](20020531)
Resolved for 3.4.x or earlier, no new info since then -> closing.