Depending on what you're doing with the WebBrowser you can handle the Navigating event, which fires before the browser navigates. Then determine if you want to handle the drop by checking the URL. For example.
Depending on what you're doing with the WebBrowser, you can handle the Navigating event, which fires before the browser navigates. Then determine if you want to handle the drop by checking the URL. For example: private void browser1_Navigating(object sender, WebBrowserNavigatingEventArgs e) { if (e.Url.
IsFile) { // Prevent navigation e. Cancel = true; // Fire your other OnDrop code } } For this to work, you would want to leave AllowWebBrowserDrop set to true. If this works for your business case, great; otherwise you're probably stuck handling window messages directly, as mentioned, which isn't much fun.
This is not quite exactly what I want, but for my purposes it is good enough. – Luke Dec 16 '10 at 16:01.
Imo, this is likely to work for catching the drop event, but also likely to break the app as winforms only "fakes" the transparent backgrounds. It's also likely to preclude other important events. – Joel Coehoorn Dec 15 '10 at 21:34 1 maybe overwrite the WndProc and forward all events to the underlying WebBrowser, except for the Drop event could work.
– Uwe Keim Dec 15 '10 at 21:36.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.