Web Browser control speed&threading
-
I have a few questions over speed and threading of the .NET 2.0 web browser control... 1) Which of the following is the "faster" methodology for capturing events HTML events? a) setting up custom scripting methods (window.external with an ObjectForScripting and ScriptMethods) b) nabbing HTML elements and setting events to them (.GetElementById() and then adding an event to it) To me it seems that the more diversity as it can be called from any object by evoking the window.external script object, but if nabbing HTML elements is "quicker" by only monitoring one element instead of waiting on a method call it might be best.?. 2) Also do you think it'll be safe to interact with the web browser control cross thread? or should I make some type of external method in the owner class to interact with the web browser control to be called from the 2nd thread? (I think I should do the later, but it might not be safe at all.?.)
-Spacix All your skynet questions[^] belong to solved