- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
One and a half years later: I'm still trying to workaround all the crap mentioned above, but here's something else, i haven't yet found a solution for:
As described before, the ClientBrowserNodeResources deflagrate as soon as the last referencing BrowserNode will be deleted. So, the most likely workaround would be, to recreate them if necessary. So far so good.
But whereas the initial creation is satisfyingly fast, recreating them becomes slower and slower the more often they are recreated, rendering the whole thing unusable after a couple of cycles. It does not even help to close the current document and start all over again with a new document created from scratch. The only thing that helps restoring a satisfying performance is closing and restarting the application.
Idea: create a hidden browserpane which maintains nodes whose only purpose is to maintain the underlying browsernoderesources. Despite the fact, that this is really fumbled, it won't help with new documents that don't already have this hidden BrowserPane.
Maybe I should give windows.forms treeview another chance. This here is UNUSABLE!!!