Community
Participate
Working Groups
When a container with multiple nested containers and components (> 2 levels) is moved, sometimes ( ~50%) the position of the nested components is calculated wrong. As a consequence, the borders of JLabels or JPanels and the resize handles do not match the bounds of the live bean. As I found out empirically, most of time the error is the movedelta plus the errors of the parent containers. In v1.2M3 this problem occurs less frequent, but is still there.
Created attachment 40175 [details] screenshot
Could you attach a non-confidential class to help reproduce this problem. Please describe in more details the scenario (steps) to reproduce the problem. What layout are you using? null, GridBagLayout? Also... what JRE are you using? JDK 1.4.2, 1.5? Thanks...Peter Walker
I´m using a custom layout manager similar to Borlands XYLayout, but I could reproduce it with other layouts too (I tried GridBag, null and FlowLayout). It happens when a container with nested elements is moved, either by moving itself (i.e. in null layout) or due to insertion of another component (i.e. in Flowlayout). One possible way to reproduce: 1. Create new VisualClass 2. Set layout to null layout 3. Insert a new JPanel (jpanel1) with null layout 4. Insert a new JPanel (jpanel2) into jpanel1 with null layout 5. Insert any component into jpanel2 (I took a JLabel, because you see the error without having to select the component) 6. Move jpanel1 around After moving jpanel1, half the time the position of the resizehandles/border of jlabel doesn´t match the real position My installed versions are: JDK 1.4.2_06 Eclipse 3.1.1 (no difference with 3.1.2) VE 1.1.0.1
Created attachment 40341 [details] A Simple TestClass Open the class in VE and move around the panel called 'moveMe'
