Description Gili Mendel 2005-07-28 17:35:08 EDT

Currently VE treats the createXXXX() method as following:

 void createC1() {
            C1 = new Composite (....)
            Button B1 = new Button(C1....)
            ....
            createC2()

            Button B11 = new Button (C1....)            
   }
  void createC2() {

          C2 = new Composite (C1, ....)
          ...
          Button B2 = new Button (C2, ....)
  }

The call to createC2() in the createC1() method is mached up with the
          C2 = new Composite (C1, ....) constructor to determine its Z order.
ie., moving createC1() after the B11 constructor will change C2's Z order.

VE fail now if the createC2() method will have multiple controls that consider
C1 as a parent... e.g:
  void createC2() {

     C2 = new Composite (C1, ....)
     Button B2 = new Button (C1, ....)  <-------- C1 is both a parent for C2, B2
  }


VE should choose the first constructor to be paired with the call to createC2()
in createC1()