I too would like too know what the WebGadget is up to sometimes, and I feel like I've been to some of the places y'all have, trying to find out.
For what it's worth, with reference strictly to (Word) "Documents", I had some luck with the following code:
***********************************************************
;Sorry, I don't know how this code will show up if copied to your system.
If OpenWindow(0, 0, 0, 1000,1000, #PB_Window_SystemMenu|#PB_Window_Screencentered, "View Word document(s)...")
If CreateGadgetList(WindowID())
File$ = OpenFileRequester("Choose file(s)", "C:\", "MS Word Documents (*.doc)|*.doc", 0,#PB_Requester_MultiSelection)
WebGadget(1, 0,0, 1000, 1000, "File://"+File$) ;maybe "File://" tells browser not to look for connection
Repeat
Event = WaitWindowEvent()
Debug event
If Event=#PB_EventRepaint
Delay(3000)
SetGadgetText(1,NextSelectedFileName())
EndIf
Until Event = #PB_EventCloseWindow ;THIS (by going to End) will close WinWord, Debugger/Quit will not
EndIf
EndIf
FreeGadget(1)
End
;Note: (Per Freak) on the first run, the file might take a little time before displaying,
;because the webgadget needs to load the MS-word file display thingy first.
;Subsequent displays should be faster, then.
*************************************************************
The key point here is "simply" Repaint, which (simply) refers to a mixture of my naive understanding of the issues with the ideosyncracies of Microsoft's Webbrowser.
In some way, though, I think, this and the Web Browser threads are related to a thread (maybe mis)titled "Message 275 (1792 on similar projects)":
viewtopic.php?t=10802&highlight=messages
I thank you recent posters for confirming that the problem was not, solely, with my feeble mind; and again, I thank the respondents, especialy fweil,to my earlier questions.