Designer stuck in loop

[Tom C]

We have a window named FormApplication which just happens to be our
mid parent window. When I open it in the designer, it is stuck in a
loop redisplaying a c1flexgrid. maxing out our cpu's. By attaching to
the process from another visual studio, I can get it to break on some
user code with this huge callstack, most of which is native. So are we
instantiating something in design mode that we should not be? Does
this mean anything to anyone? Is there any way to track dow the cause
of this?

> AdvancedSoftwar eDesigns.Window s.Forms.dll!Adv ancedSoftwareDe signs.Windows.F orms.FlexGrid._ flex_Paint(Obje ct sender = {ProductVision. Windows.Forms.F lexGrid}, System.Windows. Forms.PaintEven tArgs e = {ClipRectangle = {System.Drawing .Rectangle}}) Line 441 Basic

System.Windows. Forms.dll!
System.Windows. Forms.Control.O nPaint(System.W indows.Forms.Pa intEventArgs
e) + 0x57 bytes
C1.Win.C1FlexGr id.2.dll!
C1.Win.C1FlexGr id.Util.BaseCon trols.Scrollabl eControl.OnPain t(System.Window s.Forms.PaintEv entArgs
e = {ClipRectangle = {X=0,Y=223,Widt h=262,Height=67 }}) + 0x36 bytes
C1.Win.C1FlexGr id.2.dll!
C1.Win.C1FlexGr id.C1FlexGridBa se.OnPaint(Syst em.Windows.Form s.PaintEventArg s
e = {ClipRectangle = {X=0,Y=223,Widt h=262,Height=67 }}) + 0x35 bytes
System.Windows. Forms.dll!
System.Windows. Forms.Control.P aintWithErrorHa ndling(System.W indows.Forms.Pa intEventArgs
e = {ClipRectangle = {X=0,Y=223,Widt h=262,Height=67 }}, short layer,
bool disposeEventArg s = false) + 0x5b bytes
System.Windows. Forms.dll!Syste m.Windows.Forms .Control.WmPain t(ref
System.Windows. Forms.Message m) + 0x20b bytes
System.Windows. Forms.dll!Syste m.Windows.Forms .Control.WndPro c(ref
System.Windows. Forms.Message m) + 0x2e7 bytes
C1.Win.C1FlexGr id.2.dll!
C1.Win.C1FlexGr id.Util.BaseCon trols.Scrollabl eControl.WndPro c(ref
System.Windows. Forms.Message m = {msg=0xf (WM_PAINT) hwnd=0xd08b6
wparam=0x0 lparam=0x0 result=0x0}) + 0x1ef bytes
System.Windows. Forms.dll!
System.Windows. Forms.Control.C ontrolNativeWin dow.OnMessage(r ef
System.Windows. Forms.Message m) + 0xd bytes
System.Design.d ll!
System.Windows. Forms.Design.Co ntrolDesigner.D esignerWindowTa rget.DefWndProc (ref
System.Windows. Forms.Message m) + 0xb bytes
System.Design.d ll!
System.Windows. Forms.Design.Co ntrolDesigner.W ndProc(ref
System.Windows. Forms.Message m = {msg=0xf (WM_PAINT) hwnd=0xd08b6
wparam=0x0 lparam=0x0 result=0x0}) + 0xcca bytes
System.Design.d ll!
System.Windows. Forms.Design.Co ntrolDesigner.D esignerWindowTa rget.OnMessage( ref
System.Windows. Forms.Message m) + 0x46 bytes
System.Windows. Forms.dll!
System.Windows. Forms.Control.C ontrolNativeWin dow.WndProc(ref
System.Windows. Forms.Message m) + 0xd6 bytes
System.Windows. Forms.dll!
System.Windows. Forms.NativeWin dow.DebuggableC allback(System. IntPtr
hWnd, int msg = 15, System.IntPtr wparam, System.IntPtr lparam) + 0x75
bytes
[Native to Managed Transition]
[Managed to Native Transition]
System.Windows. Forms.dll!Syste m.Windows.Forms .Control.Update () +
0x6b bytes
System.Design.d ll!
System.Windows. Forms.Design.Be havior.Behavior Service.Adorner Window.Invalida teAdornerWindow (System.Drawing .Region
region) + 0x62 bytes
System.Design.d ll!
System.Windows. Forms.Design.To olStripItemBeha vior.ClearInser tionMark(System .Windows.Forms. ToolStripItem
item) + 0x1fd bytes
System.Design.d ll!
System.Windows. Forms.Design.To olStripItemBeha vior.OnMouseLea ve(System.Windo ws.Forms.Design .Behavior.Glyph
g) + 0x4d bytes
System.Design.d ll!
System.Windows. Forms.Design.Be havior.Behavior Service.InvokeM ouseEnterLeave( System.Windows. Forms.Design.Be havior.Glyph
leaveGlyph, System.Windows. Forms.Design.Be havior.Glyph enterGlyph =
{System.Windows .Forms.Design.T oolStripItemGly ph}) + 0x4e bytes
System.Design.d ll!
System.Windows. Forms.Design.Be havior.Behavior Service.Propaga teHitTest(Syste m.Drawing.Point
pt) + 0xaa bytes
System.Design.d ll!
System.Windows. Forms.Design.Be havior.Behavior Service.Adorner Window.WndProcP roxy(ref
System.Windows. Forms.Message m = {msg=0x200 (WM_MOUSEMOVE)
hwnd=0xa0a80 wparam=0x0 lparam=0x2d101d 3 result=0x0}, int x, int y) +
0x32 bytes
System.Design.d ll!
System.Windows. Forms.Design.Be havior.Behavior Service.Adorner Window.MouseHoo k.ProcessMouseM essage(System.I ntPtr
hWnd, int msg, int x, int y) + 0x172 bytes
System.Design.d ll!
System.Windows. Forms.Design.Be havior.Behavior Service.Adorner Window.MouseHoo k.MouseHookProc (int
nCode = 0, System.IntPtr wparam = 512, System.IntPtr lparam = 1241372)
+ 0x5f bytes
[Native to Managed Transition]
System.Windows. Forms.dll!
System.Windows. Forms.NativeWin dow.DefWndProc( ref
System.Windows. Forms.Message m = {msg=0x112 (WM_SYSCOMMAND)
hwnd=0xa0a80 wparam=0xf087 lparam=0x116fee 9 result=0x0}) + 0x94 bytes
System.Windows. Forms.dll!Syste m.Windows.Forms .Control.DefWnd Proc(ref
System.Windows. Forms.Message m) + 0xc bytes
System.Windows. Forms.dll!Syste m.Windows.Forms .Control.WndPro c(ref
System.Windows. Forms.Message m) + 0x38c bytes
System.Windows. Forms.dll!
System.Windows. Forms.Scrollabl eControl.WndPro c(ref
System.Windows. Forms.Message m) + 0x45 bytes
System.Design.d ll!
System.Windows. Forms.Design.De signerFrame.Ove rlayControl.Wnd Proc(ref
System.Windows. Forms.Message m = {msg=0x112 (WM_SYSCOMMAND)
hwnd=0xa0a80 wparam=0xf087 lparam=0x116fee 9 result=0x0}) + 0x26 bytes
System.Windows. Forms.dll!
System.Windows. Forms.Control.C ontrolNativeWin dow.OnMessage(r ef
System.Windows. Forms.Message m) + 0xd bytes
System.Windows. Forms.dll!
System.Windows. Forms.Control.C ontrolNativeWin dow.WndProc(ref
System.Windows. Forms.Message m) + 0xd6 bytes
System.Windows. Forms.dll!
System.Windows. Forms.NativeWin dow.DebuggableC allback(System. IntPtr
hWnd, int msg = 274, System.IntPtr wparam, System.IntPtr lparam) +
0x75 bytes
[Native to Managed Transition]
[Managed to Native Transition]
System.Windows. Forms.dll!
System.Windows. Forms.NativeWin dow.DefWndProc( ref
System.Windows. Forms.Message m = {msg=0xa1 (WM_NCLBUTTONDO WN)
hwnd=0xa0a80 wparam=0x7 lparam=0x116fee 9 result=0x0}) + 0x94 bytes
System.Windows. Forms.dll!Syste m.Windows.Forms .Control.DefWnd Proc(ref
System.Windows. Forms.Message m) + 0xc bytes
System.Windows. Forms.dll!Syste m.Windows.Forms .Control.WndPro c(ref
System.Windows. Forms.Message m) + 0x87a bytes
System.Windows. Forms.dll!
System.Windows. Forms.Scrollabl eControl.WndPro c(ref
System.Windows. Forms.Message m) + 0x45 bytes
System.Design.d ll!
System.Windows. Forms.Design.De signerFrame.Ove rlayControl.Wnd Proc(ref
System.Windows. Forms.Message m = {msg=0xa1 (WM_NCLBUTTONDO WN)
hwnd=0xa0a80 wparam=0x7 lparam=0x116fee 9 result=0x0}) + 0x26 bytes
System.Windows. Forms.dll!
System.Windows. Forms.Control.C ontrolNativeWin dow.OnMessage(r ef
System.Windows. Forms.Message m) + 0xd bytes
System.Windows. Forms.dll!
System.Windows. Forms.Control.C ontrolNativeWin dow.WndProc(ref
System.Windows. Forms.Message m) + 0xd6 bytes
System.Windows. Forms.dll!
System.Windows. Forms.NativeWin dow.DebuggableC allback(System. IntPtr
hWnd, int msg = 161, System.IntPtr wparam, System.IntPtr lparam) +
0x75 bytes

[Tom C]

On Jul 3, 10:07 am, Tom C <tom_cla...@asd software.comwro te:

We have a window named FormApplication which just happens to be our
mid parent window. When I open it in the designer, it is stuck in a
loop redisplaying a c1flexgrid. maxing out our cpu's. By attaching to
the process from another visual studio, I can get it to break on some
user code with this huge callstack, most of which is native. So are we
instantiating something in design mode that we should not be? Does
this mean anything to anyone? Is there any way to track dow the cause
of this?

AdvancedSoftwar eDesigns.Window s.Forms.dll!Adv ancedSoftwareDe signs.Windows.F *orms.FlexGrid. _flex_Paint(Obj ect sender = {ProductVision. Windows.Forms.F lexGrid}, System.Windows. Forms.PaintEven tArgs e = {ClipRectangle = {System.Drawing .Rectangle}}) Line 441 Basic

System.Windows. Forms.dll!
System.Windows. Forms.Control.O nPaint(System.W indows.Forms.Pa intEventArgs
e) + 0x57 bytes
C1.Win.C1FlexGr id.2.dll!
C1.Win.C1FlexGr id.Util.BaseCon trols.Scrollabl eControl.OnPain t(System.Window *s.Forms.PaintE ventArgs
e = {ClipRectangle = {X=0,Y=223,Widt h=262,Height=67 }}) + 0x36bytes
C1.Win.C1FlexGr id.2.dll!
C1.Win.C1FlexGr id.C1FlexGridBa se.OnPaint(Syst em.Windows.Form s.PaintEventArg *s
e = {ClipRectangle = {X=0,Y=223,Widt h=262,Height=67 }}) + 0x35bytes
System.Windows. Forms.dll!
System.Windows. Forms.Control.P aintWithErrorHa ndling(System.W indows.Forms.Pa *intEventArgs
e = {ClipRectangle = {X=0,Y=223,Widt h=262,Height=67 }}, short layer,
bool disposeEventArg s = false) + 0x5b bytes
System.Windows. Forms.dll!Syste m.Windows.Forms .Control.WmPain t(ref
System.Windows. Forms.Message m) + 0x20b bytes
System.Windows. Forms.dll!Syste m.Windows.Forms .Control.WndPro c(ref
System.Windows. Forms.Message m) + 0x2e7 bytes
C1.Win.C1FlexGr id.2.dll!
C1.Win.C1FlexGr id.Util.BaseCon trols.Scrollabl eControl.WndPro c(ref
System.Windows. Forms.Message m = {msg=0xf (WM_PAINT) hwnd=0xd08b6
wparam=0x0 lparam=0x0 result=0x0}) + 0x1ef bytes
System.Windows. Forms.dll!
System.Windows. Forms.Control.C ontrolNativeWin dow.OnMessage(r ef
System.Windows. Forms.Message m) + 0xd bytes
System.Design.d ll!
System.Windows. Forms.Design.Co ntrolDesigner.D esignerWindowTa rget.DefWndProc *(ref
System.Windows. Forms.Message m) + 0xb bytes
System.Design.d ll!
System.Windows. Forms.Design.Co ntrolDesigner.W ndProc(ref
System.Windows. Forms.Message m = {msg=0xf (WM_PAINT) hwnd=0xd08b6
wparam=0x0 lparam=0x0 result=0x0}) + 0xcca bytes
System.Design.d ll!
System.Windows. Forms.Design.Co ntrolDesigner.D esignerWindowTa rget.OnMessage( *ref
System.Windows. Forms.Message m) + 0x46 bytes
System.Windows. Forms.dll!
System.Windows. Forms.Control.C ontrolNativeWin dow.WndProc(ref
System.Windows. Forms.Message m) + 0xd6 bytes
System.Windows. Forms.dll!
System.Windows. Forms.NativeWin dow.DebuggableC allback(System. IntPtr
hWnd, int msg = 15, System.IntPtr wparam, System.IntPtr lparam) + 0x75
bytes
[Native to Managed Transition]
[Managed to Native Transition]
System.Windows. Forms.dll!Syste m.Windows.Forms .Control.Update () +
0x6b bytes
System.Design.d ll!
System.Windows. Forms.Design.Be havior.Behavior Service.Adorner Window.Invalida *teAdornerWindo w(System.Drawin g.Region
region) + 0x62 bytes
System.Design.d ll!
System.Windows. Forms.Design.To olStripItemBeha vior.ClearInser tionMark(System *.Windows.Forms .ToolStripItem
item) + 0x1fd bytes
System.Design.d ll!
System.Windows. Forms.Design.To olStripItemBeha vior.OnMouseLea ve(System.Windo *ws.Forms.Desig n.Behavior.Glyp h
g) + 0x4d bytes
System.Design.d ll!
System.Windows. Forms.Design.Be havior.Behavior Service.InvokeM ouseEnterLeave( *System.Windows .Forms.Design.B ehavior.Glyph
leaveGlyph, System.Windows. Forms.Design.Be havior.Glyph enterGlyph =
{System.Windows .Forms.Design.T oolStripItemGly ph}) + 0x4e bytes
System.Design.d ll!
System.Windows. Forms.Design.Be havior.Behavior Service.Propaga teHitTest(Syste *m.Drawing.Poin t
pt) + 0xaa bytes
System.Design.d ll!
System.Windows. Forms.Design.Be havior.Behavior Service.Adorner Window.WndProcP *roxy(ref
System.Windows. Forms.Message m = {msg=0x200 (WM_MOUSEMOVE)
hwnd=0xa0a80 wparam=0x0 lparam=0x2d101d 3 result=0x0}, int x, int y) +
0x32 bytes
System.Design.d ll!
System.Windows. Forms.Design.Be havior.Behavior Service.Adorner Window.MouseHoo *k.ProcessMouse Message(System. IntPtr
hWnd, int msg, int x, int y) + 0x172 bytes
System.Design.d ll!
System.Windows. Forms.Design.Be havior.Behavior Service.Adorner Window.MouseHoo *k.MouseHookPro c(int
nCode = 0, System.IntPtr wparam = 512, System.IntPtr lparam = 1241372)
+ 0x5f bytes
[Native to Managed Transition]
System.Windows. Forms.dll!
System.Windows. Forms.NativeWin dow.DefWndProc( ref
System.Windows. Forms.Message m = {msg=0x112 (WM_SYSCOMMAND)
hwnd=0xa0a80 wparam=0xf087 lparam=0x116fee 9 result=0x0}) + 0x94 bytes
System.Windows. Forms.dll!Syste m.Windows.Forms .Control.DefWnd Proc(ref
System.Windows. Forms.Message m) + 0xc bytes
System.Windows. Forms.dll!Syste m.Windows.Forms .Control.WndPro c(ref
System.Windows. Forms.Message m) + 0x38c bytes
System.Windows. Forms.dll!
System.Windows. Forms.Scrollabl eControl.WndPro c(ref
System.Windows. Forms.Message m) + 0x45 bytes
System.Design.d ll!
System.Windows. Forms.Design.De signerFrame.Ove rlayControl.Wnd Proc(ref
System.Windows. Forms.Message m = {msg=0x112 (WM_SYSCOMMAND)
hwnd=0xa0a80 wparam=0xf087 lparam=0x116fee 9 result=0x0}) + 0x26 bytes
System.Windows. Forms.dll!
System.Windows. Forms.Control.C ontrolNativeWin dow.OnMessage(r ef
System.Windows. Forms.Message m) + 0xd bytes
System.Windows. Forms.dll!
System.Windows. Forms.Control.C ontrolNativeWin dow.WndProc(ref
System.Windows. Forms.Message m) + 0xd6 bytes
System.Windows. Forms.dll!
System.Windows. Forms.NativeWin dow.DebuggableC allback(System. IntPtr
hWnd, int msg = 274, System.IntPtr wparam, System.IntPtr lparam) +
0x75 bytes
[Native to Managed Transition]
[Managed to Native Transition]
System.Windows. Forms.dll!
System.Windows. Forms.NativeWin dow.DefWndProc( ref
System.Windows. Forms.Message m = {msg=0xa1 (WM_NCLBUTTONDO WN)
hwnd=0xa0a80 wparam=0x7 lparam=0x116fee 9 result=0x0}) + 0x94 bytes
System.Windows. Forms.dll!Syste m.Windows.Forms .Control.DefWnd Proc(ref
System.Windows. Forms.Message m) + 0xc bytes
System.Windows. Forms.dll!Syste m.Windows.Forms .Control.WndPro c(ref
System.Windows. Forms.Message m) + 0x87a bytes
System.Windows. Forms.dll!
System.Windows. Forms.Scrollabl eControl.WndPro c(ref
System.Windows. Forms.Message m) + 0x45 bytes
System.Design.d ll!
System.Windows. Forms.Design.De signerFrame.Ove rlayControl.Wnd Proc(ref
System.Windows. Forms.Message m = {msg=0xa1 (WM_NCLBUTTONDO WN)
hwnd=0xa0a80 wparam=0x7 lparam=0x116fee 9 result=0x0}) + 0x26 bytes
System.Windows. Forms.dll!
System.Windows. Forms.Control.C ontrolNativeWin dow.OnMessage(r ef
System.Windows. Forms.Message m) + 0xd bytes
System.Windows. Forms.dll!
System.Windows. Forms.Control.C ontrolNativeWin dow.WndProc(ref
System.Windows. Forms.Message m) + 0xd6 bytes
System.Windows. Forms.dll!
System.Windows. Forms.NativeWin dow.DebuggableC allback(System. IntPtr
hWnd, int msg = 161, System.IntPtr wparam, System.IntPtr lparam) +
0x75 bytes

That would be mdi parent of course...

[mark.milley]

Hi Tom -

Do you have anything specified in the form's constructor? This code
will be run when the form is loaded in the designer. If so, that may
be the cause of your loops.

Cheers,

-Mark

[Tom C]

On Jul 3, 10:52 am, "mark.mil...@bi naryswitch.com"
<mark.mil...@bi naryswitch.comw rote:

Hi Tom -

Do you have anything specified in the form's constructor? This code
will be run when the form is loaded in the designer. If so, that may
be the cause of your loops.

Cheers,

-Mark

Mark,

The window itself doesn't even have constructor sub other than what
happens in the designer written code. We do have a couple of instance
variables that are declared and instantiated such as an arraylist and
booleans.

Thanks,

Tom

[mark.milley]

Do you have any custom controls on the form which may be attempting to
run code in their constructors or OnLoad event handlers?

Thanks,

-Mark

[mark.milley]

Actually, when we're talking about custom controls, they are
essentially running inside of the designer; so any code that responds
to mouse movement, etc, may be running as well.

Thanks,

-Mark

[Tom C]

On Jul 3, 11:16 am, "mark.mil...@bi naryswitch.com"
<mark.mil...@bi naryswitch.comw rote:

Actually, when we're talking about custom controls, they are
essentially running inside of the designer; so any code that responds
to mouse movement, etc, may be running as well.

Thanks,

-Mark

I just have no idea how to find it, if there is offending code
executing. We have 1 custom class on the window, a c1flexgrid, with 4
instances. Now this class is inherited by the window project from yet
another library that inherits from c1 but both of these contstructors
do little more than assign some boolean values. We have numerous
instances of this same control on other windows and it causes
absolutely no problems elsewhere.

I have a debug session running against the designer and it just runs
until I do a break all and then f10 and it steps into some user code
in our flexgrid library code and our flexgrid windows code but I don't
seen any calls other than native code so don't know any other way to
examine this.

Any ideas how I can find the offending code short of a lashing?

Tom

[Mark S. Milley, MCAD (BinarySwitch)]

It's kind of hard to determine when I'm not looking at it...

Naturally, you can start asking yourself question such as:

What is different about this form and the ones the control is working
on?
Does this control support having multiple versions on one form/is
there any reason why it might not allow that?

....and if all else fails, you can start commenting out blocks of code
until you get it to work, and narrow down the problem that way...but
man, that's a brutal way to proceed.

When you do find the problem, there are code samples online (albeit,
buggy ones) that will return a boolean value indicating whether or not
you're in the designer. (I'm surprised there's nothing in the
framework for this by now.) You could wrap the code in that function,
or, ideally, rework your solution to avoid whatever pitfall you came
across.

I had a similar problem recently with an inherited form that behaved
irratically inside the designer. I chose to rework the solution,
because the aforementioned function only works due to a bug that will
hopefully be resolved soon.

Good luck, Tom,

-Mark

[Tom C]

On Jul 3, 12:10 pm, "Mark S. Milley, MCAD (BinarySwitch)"
<mark.mil...@bi naryswitch.comw rote:

It's kind of hard to determine when I'm not looking at it...

Naturally, you can start asking yourself question such as:

What is different about this form and the ones the control is working
on?
Does this control support having multiple versions on one form/is
there any reason why it might not allow that?

...and if all else fails, you can start commenting out blocks of code
until you get it to work, and narrow down the problem that way...but
man, that's a brutal way to proceed.

When you do find the problem, there are code samples online (albeit,
buggy ones) that will return a boolean value indicating whether or not
you're in the designer. (I'm surprised there's nothing in the
framework for this by now.) You could wrap the code in that function,
or, ideally, rework your solution to avoid whatever pitfall you came
across.

I had a similar problem recently with an inherited form that behaved
irratically inside the designer. I chose to rework the solution,
because the aforementioned function only works due to a bug that will
hopefully be resolved soon.

Good luck, Tom,

-Mark

I've asked myself several questions, some of them not very polite, but
I keep getting the same dumb answers (from myself). If anyone has any
other suggestions, I am all ears.

[jeff]

create a backup of the form...
open it ...
delete the grids from the form.
add them back one by one - closing / opening form in between each
re-link any code to the control.

i know this is drastic, but it will either bring the problem to the surface
or simply make the problem disappear. just be sure to backup your current
form.

"Tom C" <to********@asd software.comwro te in message
news:11******** **************@ g4g2000hsf.goog legroups.com...

On Jul 3, 12:10 pm, "Mark S. Milley, MCAD (BinarySwitch)"
<mark.mil...@bi naryswitch.comw rote:

>It's kind of hard to determine when I'm not looking at it...

Naturally, you can start asking yourself question such as:

What is different about this form and the ones the control is working
on?
Does this control support having multiple versions on one form/is
there any reason why it might not allow that?

...and if all else fails, you can start commenting out blocks of code
until you get it to work, and narrow down the problem that way...but
man, that's a brutal way to proceed.

When you do find the problem, there are code samples online (albeit,
buggy ones) that will return a boolean value indicating whether or not
you're in the designer. (I'm surprised there's nothing in the
framework for this by now.) You could wrap the code in that function,
or, ideally, rework your solution to avoid whatever pitfall you came
across.

I had a similar problem recently with an inherited form that behaved
irratically inside the designer. I chose to rework the solution,
because the aforementioned function only works due to a bug that will
hopefully be resolved soon.

Good luck, Tom,

-Mark

I've asked myself several questions, some of them not very polite, but
I keep getting the same dumb answers (from myself). If anyone has any
other suggestions, I am all ears.