I am not sure why any of your windows would refresh themselves without
refresh code, unless you have picture fields or other self refreshing
goodies in there. (Console mode??)

If your window 3 is remaining white, then in your doDialog FN _wndRefresh
area, I would place a copy FN to recopy the content to it.

Otherwise, it may be that there is nothing with which to refresh window 3
at that point? (if your GWorlds are gone)

Other things that cause white windows for no reason...bad copy destination,
window output setting,  Copybits fore/back colors not set correctly to
black/white when Copyblitzing, and nepton-leutrino quarkination.

Demo code would be needed otherwise. The bad thing about that is that often
in doing a demo, the problem presents itself and nullifies necessity. One
is then honor bound to disclose the cure for posterity's sake . :)

rc

>Hi FB'ers,
>    I am having trouble with one window of four that doesn't refresh
>automatically.  These are 4 appearance windows (2 are for text) and the
>second two are for display of GWorlds copybitten to them.  First stuff
>is drawn to one GWorld and then copybitten to Window 1, then stuff is
>printed out and sent to window 2, then more stuff is written to another
>GWorld and copybitten to window 3, then the Pixels are unlocked and the
>  GWorlds dismissed, then after the program has reached the handlevents
>loop the forth window correctly displays data about the point where the
>mouse is clicked.  Each of these windows is well behaved and can be
>dragged about,  and enlarged or reduced.  Each of them that is except
>window 3 which leaves a permanent trail of white whenever something is
>dragged across it -- the other windows can have parts of windows dragged
>over them or be obscured and nothing happens, their image immediately
>reappears.  I do not have any _wndRefresh responding code and thought
>that since the other 3 windows don't need it then window 3 shouldn't
>need it either. Once I had a compile in which all four windows did
>refresh automatically - quite accidentally, and then, of course, never
>found it again before I had overwritten the code... It doesn't matter
>whether I copybits to window 3 before window 1 or activate either one
>before fooling with them.  As far as I can tell the code to window 1 and
>3 is identical, yet they behave differently.
>    Does this behavior suggest something I should check out?
>    Can this description suffice to generate some suggestions or shall I
>try to work up a demo snip?  As always, thanks in advance for any
>suggestions.  Hayden Coon
>
>
>--
>To unsubscribe, send ANY message to <futurebasic-unsubscribe@...>