473,396 Members | 1,998 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,396 software developers and data experts.

Designer stuck in loop

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?
> AdvancedSoftwareDesigns.Windows.Forms.dll!Advanced SoftwareDesigns.Windows.Forms.FlexGrid._flex_Paint (Object sender = {ProductVision.Windows.Forms.FlexGrid}, System.Windows.Forms.PaintEventArgs e = {ClipRectangle = {System.Drawing.Rectangle}}) Line 441 Basic
System.Windows.Forms.dll!
System.Windows.Forms.Control.OnPaint(System.Window s.Forms.PaintEventArgs
e) + 0x57 bytes
C1.Win.C1FlexGrid.2.dll!
C1.Win.C1FlexGrid.Util.BaseControls.ScrollableCont rol.OnPaint(System.Windows.Forms.PaintEventArgs
e = {ClipRectangle = {X=0,Y=223,Width=262,Height=67}}) + 0x36 bytes
C1.Win.C1FlexGrid.2.dll!
C1.Win.C1FlexGrid.C1FlexGridBase.OnPaint(System.Wi ndows.Forms.PaintEventArgs
e = {ClipRectangle = {X=0,Y=223,Width=262,Height=67}}) + 0x35 bytes
System.Windows.Forms.dll!
System.Windows.Forms.Control.PaintWithErrorHandlin g(System.Windows.Forms.PaintEventArgs
e = {ClipRectangle = {X=0,Y=223,Width=262,Height=67}}, short layer,
bool disposeEventArgs = false) + 0x5b bytes
System.Windows.Forms.dll!System.Windows.Forms.Cont rol.WmPaint(ref
System.Windows.Forms.Message m) + 0x20b bytes
System.Windows.Forms.dll!System.Windows.Forms.Cont rol.WndProc(ref
System.Windows.Forms.Message m) + 0x2e7 bytes
C1.Win.C1FlexGrid.2.dll!
C1.Win.C1FlexGrid.Util.BaseControls.ScrollableCont rol.WndProc(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.ControlNativeWindow.O nMessage(ref
System.Windows.Forms.Message m) + 0xd bytes
System.Design.dll!
System.Windows.Forms.Design.ControlDesigner.Design erWindowTarget.DefWndProc(ref
System.Windows.Forms.Message m) + 0xb bytes
System.Design.dll!
System.Windows.Forms.Design.ControlDesigner.WndPro c(ref
System.Windows.Forms.Message m = {msg=0xf (WM_PAINT) hwnd=0xd08b6
wparam=0x0 lparam=0x0 result=0x0}) + 0xcca bytes
System.Design.dll!
System.Windows.Forms.Design.ControlDesigner.Design erWindowTarget.OnMessage(ref
System.Windows.Forms.Message m) + 0x46 bytes
System.Windows.Forms.dll!
System.Windows.Forms.Control.ControlNativeWindow.W ndProc(ref
System.Windows.Forms.Message m) + 0xd6 bytes
System.Windows.Forms.dll!
System.Windows.Forms.NativeWindow.DebuggableCallba ck(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!System.Windows.Forms.Cont rol.Update() +
0x6b bytes
System.Design.dll!
System.Windows.Forms.Design.Behavior.BehaviorServi ce.AdornerWindow.InvalidateAdornerWindow(System.Dr awing.Region
region) + 0x62 bytes
System.Design.dll!
System.Windows.Forms.Design.ToolStripItemBehavior. ClearInsertionMark(System.Windows.Forms.ToolStripI tem
item) + 0x1fd bytes
System.Design.dll!
System.Windows.Forms.Design.ToolStripItemBehavior. OnMouseLeave(System.Windows.Forms.Design.Behavior. Glyph
g) + 0x4d bytes
System.Design.dll!
System.Windows.Forms.Design.Behavior.BehaviorServi ce.InvokeMouseEnterLeave(System.Windows.Forms.Desi gn.Behavior.Glyph
leaveGlyph, System.Windows.Forms.Design.Behavior.Glyph enterGlyph =
{System.Windows.Forms.Design.ToolStripItemGlyph}) + 0x4e bytes
System.Design.dll!
System.Windows.Forms.Design.Behavior.BehaviorServi ce.PropagateHitTest(System.Drawing.Point
pt) + 0xaa bytes
System.Design.dll!
System.Windows.Forms.Design.Behavior.BehaviorServi ce.AdornerWindow.WndProcProxy(ref
System.Windows.Forms.Message m = {msg=0x200 (WM_MOUSEMOVE)
hwnd=0xa0a80 wparam=0x0 lparam=0x2d101d3 result=0x0}, int x, int y) +
0x32 bytes
System.Design.dll!
System.Windows.Forms.Design.Behavior.BehaviorServi ce.AdornerWindow.MouseHook.ProcessMouseMessage(Sys tem.IntPtr
hWnd, int msg, int x, int y) + 0x172 bytes
System.Design.dll!
System.Windows.Forms.Design.Behavior.BehaviorServi ce.AdornerWindow.MouseHook.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.NativeWindow.DefWndProc(ref
System.Windows.Forms.Message m = {msg=0x112 (WM_SYSCOMMAND)
hwnd=0xa0a80 wparam=0xf087 lparam=0x116fee9 result=0x0}) + 0x94 bytes
System.Windows.Forms.dll!System.Windows.Forms.Cont rol.DefWndProc(ref
System.Windows.Forms.Message m) + 0xc bytes
System.Windows.Forms.dll!System.Windows.Forms.Cont rol.WndProc(ref
System.Windows.Forms.Message m) + 0x38c bytes
System.Windows.Forms.dll!
System.Windows.Forms.ScrollableControl.WndProc(ref
System.Windows.Forms.Message m) + 0x45 bytes
System.Design.dll!
System.Windows.Forms.Design.DesignerFrame.OverlayC ontrol.WndProc(ref
System.Windows.Forms.Message m = {msg=0x112 (WM_SYSCOMMAND)
hwnd=0xa0a80 wparam=0xf087 lparam=0x116fee9 result=0x0}) + 0x26 bytes
System.Windows.Forms.dll!
System.Windows.Forms.Control.ControlNativeWindow.O nMessage(ref
System.Windows.Forms.Message m) + 0xd bytes
System.Windows.Forms.dll!
System.Windows.Forms.Control.ControlNativeWindow.W ndProc(ref
System.Windows.Forms.Message m) + 0xd6 bytes
System.Windows.Forms.dll!
System.Windows.Forms.NativeWindow.DebuggableCallba ck(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.NativeWindow.DefWndProc(ref
System.Windows.Forms.Message m = {msg=0xa1 (WM_NCLBUTTONDOWN)
hwnd=0xa0a80 wparam=0x7 lparam=0x116fee9 result=0x0}) + 0x94 bytes
System.Windows.Forms.dll!System.Windows.Forms.Cont rol.DefWndProc(ref
System.Windows.Forms.Message m) + 0xc bytes
System.Windows.Forms.dll!System.Windows.Forms.Cont rol.WndProc(ref
System.Windows.Forms.Message m) + 0x87a bytes
System.Windows.Forms.dll!
System.Windows.Forms.ScrollableControl.WndProc(ref
System.Windows.Forms.Message m) + 0x45 bytes
System.Design.dll!
System.Windows.Forms.Design.DesignerFrame.OverlayC ontrol.WndProc(ref
System.Windows.Forms.Message m = {msg=0xa1 (WM_NCLBUTTONDOWN)
hwnd=0xa0a80 wparam=0x7 lparam=0x116fee9 result=0x0}) + 0x26 bytes
System.Windows.Forms.dll!
System.Windows.Forms.Control.ControlNativeWindow.O nMessage(ref
System.Windows.Forms.Message m) + 0xd bytes
System.Windows.Forms.dll!
System.Windows.Forms.Control.ControlNativeWindow.W ndProc(ref
System.Windows.Forms.Message m) + 0xd6 bytes
System.Windows.Forms.dll!
System.Windows.Forms.NativeWindow.DebuggableCallba ck(System.IntPtr
hWnd, int msg = 161, System.IntPtr wparam, System.IntPtr lparam) +
0x75 bytes

Jul 3 '07 #1
11 1783
On Jul 3, 10:07 am, Tom C <tom_cla...@asdsoftware.comwrote:
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?
AdvancedSoftwareDesigns.Windows.Forms.dll!Advanced SoftwareDesigns.Windows.F*orms.FlexGrid._flex_Pain t(Object sender = {ProductVision.Windows.Forms.FlexGrid}, System.Windows.Forms.PaintEventArgs e = {ClipRectangle = {System.Drawing.Rectangle}}) Line 441 Basic

System.Windows.Forms.dll!
System.Windows.Forms.Control.OnPaint(System.Window s.Forms.PaintEventArgs
e) + 0x57 bytes
C1.Win.C1FlexGrid.2.dll!
C1.Win.C1FlexGrid.Util.BaseControls.ScrollableCont rol.OnPaint(System.Window*s.Forms.PaintEventArgs
e = {ClipRectangle = {X=0,Y=223,Width=262,Height=67}}) + 0x36bytes
C1.Win.C1FlexGrid.2.dll!
C1.Win.C1FlexGrid.C1FlexGridBase.OnPaint(System.Wi ndows.Forms.PaintEventArg*s
e = {ClipRectangle = {X=0,Y=223,Width=262,Height=67}}) + 0x35bytes
System.Windows.Forms.dll!
System.Windows.Forms.Control.PaintWithErrorHandlin g(System.Windows.Forms.Pa*intEventArgs
e = {ClipRectangle = {X=0,Y=223,Width=262,Height=67}}, short layer,
bool disposeEventArgs = false) + 0x5b bytes
System.Windows.Forms.dll!System.Windows.Forms.Cont rol.WmPaint(ref
System.Windows.Forms.Message m) + 0x20b bytes
System.Windows.Forms.dll!System.Windows.Forms.Cont rol.WndProc(ref
System.Windows.Forms.Message m) + 0x2e7 bytes
C1.Win.C1FlexGrid.2.dll!
C1.Win.C1FlexGrid.Util.BaseControls.ScrollableCont rol.WndProc(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.ControlNativeWindow.O nMessage(ref
System.Windows.Forms.Message m) + 0xd bytes
System.Design.dll!
System.Windows.Forms.Design.ControlDesigner.Design erWindowTarget.DefWndProc*(ref
System.Windows.Forms.Message m) + 0xb bytes
System.Design.dll!
System.Windows.Forms.Design.ControlDesigner.WndPro c(ref
System.Windows.Forms.Message m = {msg=0xf (WM_PAINT) hwnd=0xd08b6
wparam=0x0 lparam=0x0 result=0x0}) + 0xcca bytes
System.Design.dll!
System.Windows.Forms.Design.ControlDesigner.Design erWindowTarget.OnMessage(*ref
System.Windows.Forms.Message m) + 0x46 bytes
System.Windows.Forms.dll!
System.Windows.Forms.Control.ControlNativeWindow.W ndProc(ref
System.Windows.Forms.Message m) + 0xd6 bytes
System.Windows.Forms.dll!
System.Windows.Forms.NativeWindow.DebuggableCallba ck(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!System.Windows.Forms.Cont rol.Update() +
0x6b bytes
System.Design.dll!
System.Windows.Forms.Design.Behavior.BehaviorServi ce.AdornerWindow.Invalida*teAdornerWindow(System.D rawing.Region
region) + 0x62 bytes
System.Design.dll!
System.Windows.Forms.Design.ToolStripItemBehavior. ClearInsertionMark(System*.Windows.Forms.ToolStrip Item
item) + 0x1fd bytes
System.Design.dll!
System.Windows.Forms.Design.ToolStripItemBehavior. OnMouseLeave(System.Windo*ws.Forms.Design.Behavior .Glyph
g) + 0x4d bytes
System.Design.dll!
System.Windows.Forms.Design.Behavior.BehaviorServi ce.InvokeMouseEnterLeave(*System.Windows.Forms.Des ign.Behavior.Glyph
leaveGlyph, System.Windows.Forms.Design.Behavior.Glyph enterGlyph =
{System.Windows.Forms.Design.ToolStripItemGlyph}) + 0x4e bytes
System.Design.dll!
System.Windows.Forms.Design.Behavior.BehaviorServi ce.PropagateHitTest(Syste*m.Drawing.Point
pt) + 0xaa bytes
System.Design.dll!
System.Windows.Forms.Design.Behavior.BehaviorServi ce.AdornerWindow.WndProcP*roxy(ref
System.Windows.Forms.Message m = {msg=0x200 (WM_MOUSEMOVE)
hwnd=0xa0a80 wparam=0x0 lparam=0x2d101d3 result=0x0}, int x, int y) +
0x32 bytes
System.Design.dll!
System.Windows.Forms.Design.Behavior.BehaviorServi ce.AdornerWindow.MouseHoo*k.ProcessMouseMessage(Sy stem.IntPtr
hWnd, int msg, int x, int y) + 0x172 bytes
System.Design.dll!
System.Windows.Forms.Design.Behavior.BehaviorServi ce.AdornerWindow.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.NativeWindow.DefWndProc(ref
System.Windows.Forms.Message m = {msg=0x112 (WM_SYSCOMMAND)
hwnd=0xa0a80 wparam=0xf087 lparam=0x116fee9 result=0x0}) + 0x94 bytes
System.Windows.Forms.dll!System.Windows.Forms.Cont rol.DefWndProc(ref
System.Windows.Forms.Message m) + 0xc bytes
System.Windows.Forms.dll!System.Windows.Forms.Cont rol.WndProc(ref
System.Windows.Forms.Message m) + 0x38c bytes
System.Windows.Forms.dll!
System.Windows.Forms.ScrollableControl.WndProc(ref
System.Windows.Forms.Message m) + 0x45 bytes
System.Design.dll!
System.Windows.Forms.Design.DesignerFrame.OverlayC ontrol.WndProc(ref
System.Windows.Forms.Message m = {msg=0x112 (WM_SYSCOMMAND)
hwnd=0xa0a80 wparam=0xf087 lparam=0x116fee9 result=0x0}) + 0x26 bytes
System.Windows.Forms.dll!
System.Windows.Forms.Control.ControlNativeWindow.O nMessage(ref
System.Windows.Forms.Message m) + 0xd bytes
System.Windows.Forms.dll!
System.Windows.Forms.Control.ControlNativeWindow.W ndProc(ref
System.Windows.Forms.Message m) + 0xd6 bytes
System.Windows.Forms.dll!
System.Windows.Forms.NativeWindow.DebuggableCallba ck(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.NativeWindow.DefWndProc(ref
System.Windows.Forms.Message m = {msg=0xa1 (WM_NCLBUTTONDOWN)
hwnd=0xa0a80 wparam=0x7 lparam=0x116fee9 result=0x0}) + 0x94 bytes
System.Windows.Forms.dll!System.Windows.Forms.Cont rol.DefWndProc(ref
System.Windows.Forms.Message m) + 0xc bytes
System.Windows.Forms.dll!System.Windows.Forms.Cont rol.WndProc(ref
System.Windows.Forms.Message m) + 0x87a bytes
System.Windows.Forms.dll!
System.Windows.Forms.ScrollableControl.WndProc(ref
System.Windows.Forms.Message m) + 0x45 bytes
System.Design.dll!
System.Windows.Forms.Design.DesignerFrame.OverlayC ontrol.WndProc(ref
System.Windows.Forms.Message m = {msg=0xa1 (WM_NCLBUTTONDOWN)
hwnd=0xa0a80 wparam=0x7 lparam=0x116fee9 result=0x0}) + 0x26 bytes
System.Windows.Forms.dll!
System.Windows.Forms.Control.ControlNativeWindow.O nMessage(ref
System.Windows.Forms.Message m) + 0xd bytes
System.Windows.Forms.dll!
System.Windows.Forms.Control.ControlNativeWindow.W ndProc(ref
System.Windows.Forms.Message m) + 0xd6 bytes
System.Windows.Forms.dll!
System.Windows.Forms.NativeWindow.DebuggableCallba ck(System.IntPtr
hWnd, int msg = 161, System.IntPtr wparam, System.IntPtr lparam) +
0x75 bytes
That would be mdi parent of course...

Jul 3 '07 #2
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

Jul 3 '07 #3
On Jul 3, 10:52 am, "mark.mil...@binaryswitch.com"
<mark.mil...@binaryswitch.comwrote:
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

Jul 3 '07 #4
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

Jul 3 '07 #5
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

Jul 3 '07 #6
On Jul 3, 11:16 am, "mark.mil...@binaryswitch.com"
<mark.mil...@binaryswitch.comwrote:
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

Jul 3 '07 #7
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

Jul 3 '07 #8
On Jul 3, 12:10 pm, "Mark S. Milley, MCAD (BinarySwitch)"
<mark.mil...@binaryswitch.comwrote:
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.

Jul 3 '07 #9
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********@asdsoftware.comwrote in message
news:11**********************@g4g2000hsf.googlegro ups.com...
On Jul 3, 12:10 pm, "Mark S. Milley, MCAD (BinarySwitch)"
<mark.mil...@binaryswitch.comwrote:
>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.

Jul 3 '07 #10
Tom C wrote:
>
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.

Have you bound one or more of the C1FlexGrid Controls to a Database
using the "DataSource" property in the Design Window? If so, try
releasing this and see what happens.

Also, I think you wrote that you haven't generated any code as yet, so
try removing the "ToolStrip" control that shows in the CallStack, I've
had a problem with this failing to initialize in the past.

(Just my 2-cents worth!)

ShaneO

There are 10 kinds of people - Those who understand Binary and those who
don't.
Jul 4 '07 #11
On Jul 4, 1:47 am, ShaneO <spc...@optusnet.com.auwrote:
Tom C wrote:
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.

Have you bound one or more of the C1FlexGrid Controls to a Database
using the "DataSource" property in the Design Window? If so, try
releasing this and see what happens.

Also, I think you wrote that you haven't generated any code as yet, so
try removing the "ToolStrip" control that shows in the CallStack, I've
had a problem with this failing to initialize in the past.

(Just my 2-cents worth!)

ShaneO

There are 10 kinds of people - Those who understand Binary and those who
don't.
Problem solved. Turned out to be some bad references that must have
been causing a conflict.

Jul 5 '07 #12

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

34
by: Fred | last post by:
Hi, I'm currently checking out Python as an alternative to VB.Net to moving from VB, but can't find a GUI designer that is as good as VB. I tried wxDesigner and wxGlade, but neither lets me...
12
by: reynoldscraigr | last post by:
Hi All, hope someone can see what wrong here I have the following function function RemoveMenuFromHoldArray(menuName) { var i = 0; for (i=0;i<=MenusToHoldOpen.length-1;i++) { if...
0
by: Ward Bekker | last post by:
Hi, I am researching if it is possible to incorporate the web forms designer that is used by visual studio in another application. Hosting the WIN forms designer is already possible (see...
4
by: Dave Taylor | last post by:
I've been using the dataset designer in Visual Studio to create typed datasets for my application by dragging over tables from the Server Explorer and dropping them into the designer. The problem...
3
by: Crazy Cat | last post by:
Hi, I'm developing an application that is basically a VB.NET front end to a SQL Server Express 2005 database -- right now I'm using VB.NET 2005 Express until my MSDN subscription gets delivered...
1
by: dev | last post by:
Hi everyone, Is there a way to bind a control (TextBox) to an untyped public DataSet on a WinForm and have its columns appear in the designer under "databindings"? For example, in pseudo-code: ...
0
by: sloan | last post by:
My Environment: VS2005 VS2005 SP1 Installed 3.0 Framework installed SilverLight 1.0 SDK Installed I've gotten back into actually coding up some SilverLight demos/projects.
2
by: hexusnexus | last post by:
I wrote a simple algorithm and it keeps getting stuck in a loop. I guess I'm just to tired to figure it out: compcount= suitrank= trump=2 l,lt=0,0 while l<4: while lt<4:
1
by: Cainnech | last post by:
Hi guys, I'm a bit stuck in an infinite loop. What I'm trying to do in the code below is to compare two arrays and if there's an item in array ALGEMEEN that is not in array ITEMS, I want to add it...
0
by: Charles Arthur | last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
0
by: ryjfgjl | last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
0
by: emmanuelkatto | last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud. Please let me know. Thanks! Emmanuel
0
BarryA
by: BarryA | last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
1
by: nemocccc | last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
0
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
0
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
0
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers,...
0
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.