• 0

Nested Groupboxes, .NET 1.1 SP1


Question

It seems in the latest release of the framework, any groupbox (with visual styles applied) that is within another groupbox has its text all screwed up. Does anyone know why and/or how to fix this? It used to work fine, but now the text settings are ignored.

post-47-1094868994.png

Link to comment
Share on other sites

9 answers to this question

Recommended Posts

  • 0
i think you might be going a bit overboard with the nested group box..if the window is already for 'settings' is there reallly any reason to group them all together again ?

Yes, they are necessary. Fine, take away the "Settings" groupbox. I still need them nested for the forecast display/scroll wheel. And elsewhere throughout the program where things need to be subdivided.

Link to comment
Share on other sites

  • 0

Well, honestly... I think the groupboxes are the wrong thing to use in this case anyway (they're rarely the right solution to an organization problem). That dialog is efficient, but only programmers care about efficiency. Most users would probably find that dialog cluttered and confusing.

As for nested groupboxes... it's probably a bug in the Framework, and one that I'm not surprised would be overlooked. They're really not meant to be used that way, and I doubt there are very many programmers who would choose to nest them like that.

Link to comment
Share on other sites

  • 0

Im going to agree with dannysmurf, looks like a bug ms introduced in sp1, cause i don't have sp1 here and my groupboxes look fine.

Also, have you though about doing the old vb6 trick, groupbox in a picture box with the dock set to fill?

Also, have you thought about changing your dialog into a set of tabs, they might have lots of white space, but it's neater than a whole big bunch of groupboxes.

Link to comment
Share on other sites

  • 0

Yeah I am in the middle of migrating to tabs but the main part of the program also organizes with nested groupboxes (e.g. Date of forecast -> Daytime forecast/Nighttime forecast)

It worked fine in 1.1 non SP1, it only started when I put on SP1 so it's obviously been introduced then. I'm surprised (but annoyed) they broke it.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.