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.
[dev-200501181900, JDK 1.5.0_02] Add button cannot be added to form toolbar. Most of the time it's not possible to show add button on form toolbar. Usually after using new component palette. Once I was able to show the button but after clicking the palette it wasn't possible again.
I cannot reproduce this. There is no problem with add button on my machine with latest q-build candidate.
It works for me as well.
Yes, works the same way as in 4.0. If user selects some component then it's not possible to show the button until the component is deselected.
This is good candidate for usability enhancement. You can see how confusing this was for experienced user of NB, now imagine the confusion of new user. The clicks within IDE during add active behaves deifferently and sometimes user does not know why. The solution would be to change mouse cursor to arrow with little plus sign (similar to arrow displayed when windows are drag&dropped) or arrow with the gui component underneath.
The add button is likely going to be removed. By default it is not in the toolbar and I doubt anybody ever found how to add it. Contextual "Add from palette..." is enough in most cases. Also in 4.2 the added components will be moved with the cursor (previewed). So closing this.
"By default it is not in the toolbar and I doubt anybody ever found how to add it." - how can you be so certain? I personaly use it because I don't want the palette to steal half of my work place if I just need to tune layout manager, for example. Are there any data to support removing the Add button from UI?
It is only my guess. The Add button is not in UI by default. It is hidden - you must know about it to enable it. It is in no UI spec. It is even not in help (I believe). Also the icon does not match with the other icons in the toolbar. I'd say it is rather an unofficial feature that was forgotten somehow. We should either make it official, or drop it. The later means less work ;) And you can do the same job via context menu on a container. (Maybe it stays there if we forget to remove it and nobody will file bugs on it, but don't tell anybody ;)