I have a neat template I designed that takes care of most of my application. It has a main splitscreen control and two nested splitscreen objects, one of which contains a nested splitscreen. All of the exposed splitscreen panels themselves contain a panel object. One of the panels loads a subform depending upon where the user is in the app. Some of the panels have gradients that are applied when their element is painted.
This thing flickers a little when first loaded, but then quites down. I added ONE more splitscreen (plus 2 nested panels) and now the thing flickers for a good second every time I resize the app or load the new form.
Has anyone run into an upper limit on graphics in windows forms applications, or a discussion on this topic? Seems a little strange that vb.net is worse than asp.net with graphical problems, considering IE is sitting on top of the same libraries windows forms is sitting on, and has to call those to create an html display...
This thing flickers a little when first loaded, but then quites down. I added ONE more splitscreen (plus 2 nested panels) and now the thing flickers for a good second every time I resize the app or load the new form.
Has anyone run into an upper limit on graphics in windows forms applications, or a discussion on this topic? Seems a little strange that vb.net is worse than asp.net with graphical problems, considering IE is sitting on top of the same libraries windows forms is sitting on, and has to call those to create an html display...