I've cc'd some folks who were involved in discussions about the priority
order of screen updates vs. dynamic content manipulation. maybe they
can shed some light on where we're at, and where we're going.
steve
Kurt A. Johnson wrote:
> I have a page that contains a number of <DIV>s. We are constantly changing
> and adding controls or tables. The end-result is that the screen is very
> jerky -- updates are rendered while code is still executing.
>
> IE5 is fairly good at waiting and then the results are revealed at once. In
> Navigator, our page changes look a little slap-dash.
>
> Is there a property that I can set, or some other workaround, to prohibit
> screen updates until my function completes?
>
> Many thanks,
>
> Kurt
>
>
>
