Hi Guys,
Here is the scenario, i'm using NetAdvantage_NET_20082_CLR20_Bundle.
I have 2 simple forms, on each one i have added UltraToolBarsManager and set the FormDisplayStyle to RoundedSizeable.
From the main form i'm doing ShowDialog() to the second one.
public partial class Form1 : Form { public Form1() { InitializeComponent(); } private void ultraButton1_Click(object sender, EventArgs e) { (new Dialog()).ShowDialog(); } }
Things are as simple as above - i've created a clean project and implemented the above.
When the Dialog form is shown the main form (maxmized) SHAKES! (??! :-() ).
I can't seem to get rid of this....
I though this is something in my code - but on a totally clean project and on more than one computer - this keeps happaning...
PLEASE HELP :(
Thanx,
Gili
Gili,
My guess is that something with the ToolbarsManager is causing this, since the RoundedSizable style requires that the manager performs some complex manipulations on the owning form/window. Do you have the latest service release installed? I know that there were several fixes done in the past related to this behavior and form sizing.
-Matt
Hi Matt,
Check this out: Normal 0 false false false EN-US X-NONE HE MicrosoftInternetExplorer4 http://forums.infragistics.com/forums/t/16479.aspx
I've upgraded to version 8.3 which is still part of our license with you and this was solved.
But now I'm experiencing something else - i user the bellow code line in my project:
WindowState = FormWindowState.Minimized
And the form seems not to be maximized correctly, it is maximized but the borders do not correspond with the screen borders.
Again: i'm using ultratoolbars manager to set the formdisplaystyle to roundedsizeable.
Is there a build in way in infragistics controls to tell the form to maximize it self?
Is there a workaround for this.
I think you guys should publish these bugs in a more organized manner, i'm spending so much time figuring out what causes this weird behavioures. I've been searching my code for 2 mounth for something that might have caused this - this is after i already got a reply from Mike not understanding what i'm talking about.
-Gili