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.
Migrated from woodstock: Issue 962: https://woodstock.dev.java.net/issues/show_bug.cgi?id=962 .1.1 RC2 NB6.0 RC2 1. Drop a button at the top of the page and an addRemove component onto the design surface. 2. Run & deploy the app. The button renders on top of the addRemove component. 3. Remove addRemove - redeploy. The button renders in the correct/desired spot on the page. see the attached. I'm not sure if this is a button bug or addremove bug, and therefore filed it against the component most affected. ----- Additional comments from camucci Thu Nov 29 18:32:54 +0000 2007 ------- Created an attachment (id=250) button displays on top of addremove ------- Additional comments from camucci Thu Nov 29 18:36:16 +0000 2007 ------- Created an attachment (id=251) button appears in desired spot when no add remove ------- Additional comments from camucci Thu Nov 29 20:00:18 +0000 2007 ------- I was able to reproduce this with the dropdown and addremove components as well so I feel it is either a designer issue and/or the addremove component. I will continue to debug this test until I have a reproduceable test case to document here. ------- Additional comments from camucci Thu Nov 29 20:12:00 +0000 2007 ------- New bug description. ------- Additional comments from camucci Thu Nov 29 20:41:36 +0000 2007 ------- Repeatable, reproduceable steps: 1. Start with an empty Page 2. Add a component (I chose button) at the top, accept all defaults 3. Drop AddRemove on page, update: a. add label, set to on top b. change to vertical c. click duplicate allowed, sorted, required 4. Drop another button the page ---position it ABOVE the add remove component 5. Build & deploy. I could get it to happen with components added *after* I drop the vertical Addremove component and when they are placed above the component on the page. Again, this could be a NB6.0 designer issue. ------- Additional comments from danl Thu Nov 29 21:00:06 +0000 2007 ------- Reassigning to component owner. There seems to be a difference in the way the designtime and runtime components are rendered on to the page which should not be happening.
Moving it back to woodstock.. Looks like an issue with the way add remove is getting rendered. Its affecting other components in the page like the button.
This is a great inspiring article.I am pretty much pleased with your good work.You put really very helpful information. Keep it up. Keep blogging. Looking to reading your next post. <a href="http://www.facebook.com">FB</a>