Eric Clayberg wrote:It is important to keep in mind that we are not experts in using either Nebula or the Eclipse Data Binding framework (neither are used internally to create WindowBuilder, for example). A complex question that involves usage of both of those combined is well outside our area of expertise (thus the suggestion to ask the question in the most likely places to find someone knowledgeable to help you).
Let me ask, then, whether this is the correct forum.
I eventually tracked the problem down to the generated code. It seems that SWT Designer always called "InitDataBindings()" if it is present in the form code, even if it's not called from CreateContent(). (i.e, I moved the explicit call to it out of that method). When I use the DataBindingWizard to generate code, and then move the code it generates to another method ("MyDataBindingInit()"), the generated code works properly when I run my application. However, SWT Designer will not render the form properly if I leave the generated code in place. This may be due to how the underlying objects being bound are initialized, or it might be due to how SWT Designer is processing the code when it gets ready to render the page for the visual editor. Since the code works when I run it, I have to guess I'm creating the objects properly, but there might be another step I need to let SWT Designer access them when it needs to do whatever-it-does to set up the DataBinding Wizard?
If you think it will be valuable for me to post the source here, I will try to provide as much of the relevant code as possible.