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.
[nb_dev](20030725), [jdk1.5.0](b12) Steps to reproduce: - run IDE - select two files (with different values of property "compiler") -> "different values " label is visible, in the write state customizer button "..." isn't visible It's regression against old property sheet implementation. There has been possible to invoke customizer even if values were different
This was done as a fix for another issue. The real problem is that the "Different Values" state is not built into the property editor infrastructure from the ground up (yet another reason to rewrite the whole property infrastructure) - and also that there is no real interface for custom editors, just a random Component. Some customizers will handle it fine, some will get the DifferentValuesException and choke - this was always the case. So $1000 question is: Which is worse - no customizer button for multi-selections, or occasional exceptions and problems? The right solution is to make DifferentValuesException public, and go through all of our customizers and property editors to make it work. That, however, is a pretty substantial amount of work. Adding Dusan to the CC list - what do you think?
Okay, I'm closing this as won't fix - the custom editor buttons are gone by design, when the value is different values (you can still multi-select and use the editor in the property sheet, just not the open one). There is simply no way to allow custom editors over a multiple selection without some of them failing and throwing exceptions. I can't see enabling something that will be broken part of the time. If you strongly feel that this should be possible, we need an interface for custom editors which we will encourage and enforce. We could then allow multi-select custom editors *if* the editor implements that interface. Doing that is a good idea, since it will also allow us to do Apply/Cancel property editors and things like that. So, if you feel strongly, file an enhancement to make that possible. Turning off something that never could work right isn't a regression, it's just good sense.
> Turning off something that never could work right isn't a regression, it's just good sense. -> :) I would like to see a way change value by property customizer (dialog opened after pushing ...), but if it is not possible to do it I verified
Reopening as an enhancement. It can be done, but it requires an API for custom editors that is able to tell the editor it is editing more than one value. We need a real API for custom editors anyway - just "Component" is not enough.
Anyone wants to provide a patch?