from some reason, my previous thread was locked before i could even reply it:
and i can't find how to PM whoever done it.
anyway, my reply is:
Whether you can click on the composite and drag it in the design view depends on what layout it has and how much white space there is to grab on to. You would need to click somewhere not occupied by one of its children. This is quite easy to do if the composite is using a GridLayout or null layout, for example. In the extreme case where you have a FillLayout and the child completely fills the composite, you would need to select the composite in the tree. Once the composite has focus, you can drag it by one of its edges to another cell.
-what? why not treat the composite just like any other component, so it could move freely on the gridLayout ?
You can reveal any child of a StackLayout by clicking on it in the component tree. The child that is showing can then be edited in the design view.
-that doesn't work. maybe it has something to do with the fact that on one of them i have a JOGL component via AWT ?
i also have some suggestions, since i've learned some C# recently , using Visual Studio 2008 . i found there some really cool stuff, that i wish we could have on window builder too :
1.on VS2008 , there is full seperation between the events and the design of the window. not only that, but the GUI components are seperated as well, by comments with their names.i wish we could do something like that automatically on window-builder too. on Window builder, everything is merged into one file, so we have a mess and it's easy to have bugs, even if all you did is just moving a button in the design view.
2.on VS2008 , you can see all of the available events of a control via a window that is also used for viewing the properties of it. also, all of the events that are already used are marked there and are shown with their full name.you can also sort by alphabet and in categorized view , for both the events and the properties. on window builder , we have to right click on the component instead, and look for the desired event by ourselves.
3.when there is a situation of a component behind another , VS2008 allows you to choose the one you wanted, by right clicking on this area and choose which component you wish to choose.on windowBuilder, you have to find which of them you want to choose, via the tree of the GUI components.
4.you can see the code of a specific component by right clicking on it and press 'view code' . this is quite odd on VS2008 , since what it does is showing the code of the default event of this component. i would suggest having a menu of what code of the object to show - each of the events of it, and also the design code of it. windowBuilder has it for the events, but not for the properties of the object.