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.
Error label on Import Reference Schema dialog affects other controls so they became smaller. See screenshot for details. Detailed steps to show this dialog and error message described at 105708.
Created attachment 43236 [details] combined screenshot
I have to say I don't have any idea where this dialog comes from .. so reassign to xml ... feel free to reassign.
I wrote link to issues with detailed steps BTW ;) Possible this is really XML but I think (don't know why exactly) such dialogs use common layout defined somewhere in core...
Is the dialog really distorted like in the image? Also, which 'other' control has become smaller exactly?
Screenshot shows exactly: projects/files list (main control on this dialog) changes his height in few pixels.
I dont see this issue in the latest build. Tony, Can you please take a look?
I'm not sure exactly how to reproduce this or what the problem even is. I see the screen shot and that the namespace field and horizontal scroll bar are skewed, but I have never seen this. Please provide steps to reproduce.
Well it's easy. 1. Create something like BPEL module. 2. Add Sample XML schema into. 3. Open schema, select Referenced Schemas and open Add Import dialog. 4. Expand ByFile / BpelModule1 / Process Files / newLoanApplication.xsd node. 5. Select Process Files node and note tree view size and Namespace textbox position. 6. Select newLoanApplication.xsd node (just press Down Arrow) and note new size and new position.
I did the steps and pressing the down arrow doesn't result in even a pixel shift in the GUI. I repeatedly pressed up/down arrow and I don't see any changes in GUI What's the version of OS, JDK?
Michael, Can you update this bug with ur OS/JDK version since we are unable to reproduce this bug?
Java: 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105 System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)
Doesn't sound like an issue related to our code, this is more of a platform/environment issue.
Not worth the time and resource.