Click here to Skip to main content
15,742,464 members

Comments by webmaster442 (Top 16 by date)

webmaster442 30-Oct-17 19:01pm View    
By using the Dispatcher Invoke, you basicly eliminate the background thread, because when you call a dispatcher invoke, it executes the code on the UI rendering thread, instead of a background thread.

Also OnPaint is a blocking event, because it occures every time when the Window is painted.

The "easiest" way to overcome your problem is to redesign it. Why would you render all 1000 chars, when only a portion of them will be visible ?
webmaster442 29-Feb-16 12:33pm View    
On the build options uncheck the "Prefer 32 bit" checkbox. Place the 64bit dll next to the app, and theoretically you're done.
webmaster442 3-Jan-16 15:16pm View    
I don't see why you want to stick with one Textblock. Use two. It's much easier.
webmaster442 31-Dec-15 9:03am View    
Then it's your PDF readers issue. The Webbrowser control can't display PDF natively, it calls an aciveX contol. Maybe the system blocks your activeX control for whatever reason. Maybe your Visual Studio is running as Administrator. In this case as an Administrator maybe it allows the execution.
But like I sad previously forget the built in webrowser.
webmaster442 21-Dec-15 14:53pm View    
Exactly what you mean by creating automatically?