I am running into the problem described in bug 219426 on WM 6 Pro but I am having some trouble implementing the workaround. After adding a nested Shell and setting it visible and active, I am still getting two events when the keyboard is activated. The first one with the correct, smaller size, the second one with the size as when the keyboard is not active. I'm only trying to resize a child Composite and not one of the Shells so I don't think the setBounds() or setSize() call is causing the second resize event on the Shell. I'd appreciate any help in resolving this.
Best regards,