[hari_k]

Hi,

1st option is : Use the SmartGWT scrolling system instead of browser scrolling. For my application i need browser scrolling.

2nd option is : clear() any widget that becomes hidden yet extends out of the browser viewport.

I had made the changes in the demo application. attached is the changed code. I got the expected result in demo application.

But the same i am using in my actual application. Here i am not getting the browser changes.

Any suggestions....

Thanks,
Hari.

[hari_k]

Info : In demo application i have only one level menu/tabset....but in actual application i have 3 levels menu/tabset.

It requires to clear all levels widgets. But the actual page will appear in the innermost (3rd level) menu. i am calling destroy() method for innermost (3rd level) menu.

[Isomorphic]

There is no need to clear() all levels of widgets, children are automatically clear()d with the parent.

Just a reminder that our recommendation is to use the scrolling built into SmartGWT, and this clear() approach is a distant second choice.

If the clear() approach is working for you in a standalone case and not working in your actual application, you need to troubleshoot to determine what the difference is. The Watch tab in the Developer Console can shown you which components are drawn or not drawn (if something is clear()d it becomes not drawn), and this may help isolate a logic bug in your code.

Let us know if you discover something that appears to be a framework issue.