Tag Info

New answers tagged

1

The key thing to realise about the Windows API is that you have to hide it. The sequence of steps for creating a window, creating and adding child controls, handling messages and handling command routing is seriously messy. You cannot put lipstick on the pig. You have to hide it. So you need to code to a framework. The are lots around, but I understand ...


3

You'll want to redraw the whole thing. Keeping track of which parts are still the same as the unsized image is going to be computationally more difficult as simply redrawing the whole lot, especially considering that in general usage you're going to have a dialog full of controls, not full of whitespace. Even in the case of text, the text displayed will be ...


2

You might take many years to code a significant GUI application without using any toolkit (but life is short, so are you sure it is worth the effort?). Currently, Linux GUI applications are using the X11 server and protocol. (In a few years, that might change, because Wayland might replace X11 in the future). Notice that X11 is complex (for technical and ...


1

For scenarios like this, you should be using either BackgroundWorker or Task. Example code for BackgroundWorker usage: var bw = new BackgroundWorker(); bw.DoWork += LongRunningBackgroundWork; bw.RunWorkerCompleted += LongRunningBackgroundWorkCompleted; bw.RunWorkerAsync(); void LongRunningBackgroundWork(object sender, DoWorkEventArgs e) { // Perform ...



Top 50 recent answers are included