Really annoying bug!! - [FAO Tim - I can't login to support!]

Does anyone else get the following error when using Eyefinder v1.3?

If I put any controls onto the form.. Edit the events.. Then close the form.

When I come back to it the header control on the right jumps to the left? And all the events on the form are no longer handled... ie..

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click

The bit highlighted RED disappears. Its not so bad when there's one.. But I have some forms with quite a few events on and its becoming a nightmare to re-enter the handles after every time I open the form for editting?

Thanks Rob

I can't believe no one else has has this error too?

Do that mean that either no one uses the Eyefinder? or there's something wrong with just my computer?

I've just had something very similar happen to me yesterday, I lost all events (although there was no header expanding).

The form was using Eyefinder (5 panes with a property grid in each), but also SandDock (with 4 dockable windows, all tabbed together on the left side, one of which contained the Eyefinder nav described and SandGrids in the 3 others) ... plus of course other standard controls in the dockable windows. Nothing else on the form though, the right part is for dynamic run time tabbed documents.

After it happened, I diff'ed VS my previous version in source control and EVERY line of the form "control.event += new handler" (C# format) was gone from .Designer.cs -- Load, Close, MouseMove, ... SandGrid Click and SelectionChanged, SandDock ActiveTabbedDocumentChanged,... EACH AND EVERY handler in all categories for all controls.

No clue what really causes that (I did a bunch of changes then ran my app and noticed nothing was working, so I can't tell precisely which action caused it), but it's a huuuuge pain.

Versions used:
Eyefinder 1.3.0.1
SandDock 2.4.3.1
SandGrid 1.1.1.1

Yves

It just happened again, this has got to be fixed, it's a MAJOR pain.
I touched an Eyefinder in a SandDock docking window and BOOM all events on the main form are gone again.

Yves

I tried to get a reproducible case for you Tim, but I couldn't make it happen on demand.
BUT... during my various experiments, I encountered a case where the entire nav failed to serialize itself to CodeDom, I got errors on each and every property of it (I wish I had screenshotted that) and I had to trash the form entirely.

I'm thinking there is a pretty damn rare bug where the serialization gets hosed... sorry I couldn't find an easy repro :/

Yves

This is nothing to do with any of our components. There is nothing a component could possibly do that would result in event bindings being lost. Components don't have that level of integration with your code.

VS just sometimes does things like this, it's happened to me too.

Hello all...

Thanks for finally getting back to us Tim.. This has been a pain in the butt for me since getting this component... It appears that what happens is the main header control (In my example screenshot - the one that's disappeared) it is being set to the back of the controls in terms of its order.

If you right click on the "hidden" header control and select "Bring to front" I've found it fixes the problem. Once you've had the problem on a form once and done this. It doesn't appear to happen again.. So it appears that is something to do with how the control determines which header control is at the front that the problem lies...

(p.s. I get the problem happen the most when I am switching between the code view for a form and designer view)

Thanks Rob