IDE Crash when double-clicking an IDE tab

[Robert Eaton]

Don't think I've seen this reported yet. This has been bugging me for a while and finally found it!

1- Start a new project (everything default).
2- Add a second form. (Form 2 is now visible)
3- Double-click the IDE tab on Form 2 to take you to the code page for Form 2.
4- Now double-click the IDE tab for Form 1.
For me, this crashes the FF IDE every time. Apparently I double-click the tabs at times when it's not required.

FF 3.09
Win XP

[Cho Sing Kum]

I tried the sequence several times and the IDE did not crash. Not even once.

The cause may be something else.

[Brian Chirgwin]

I've tried this too. Doesn't crash for me either.

[Douglas McDonald]

Doesn't crash for me ether. ver 3.09 win7 x64

Doug

[Robert Eaton]

I think I have a better handle on it now.
I believe it has something to do with clicking while a FF form is in the process of redrawing. Harder to do on a faster machine. (I use a little Toshiba netbook most of the time.) So doing a reboot and with nothing else running, it doesn't crash here either.

However, if I add a bunch of controls to a form (which slows down the redraw), the problem comes back. (I originally discovered this in a project that had a lot of controls.)

I'll check this out on one of my faster machines (that are running Vista) and if crashes there, I'll post a sample project later.

Thanks,
Bob

[Robert Eaton]

With the attached project I can get my Vista Laptop to crash. (Dell XPS 1530 with 4 gigs of ram.)

But, it usually takes takes a while, double-clicking back and forth between the tabs, before it finally locks up.

The project is simply two forms, with a bunch of controls on one of them.

[Cho Sing Kum]

I can replicate the crash.

Ensure that Form1 is in form view (this is important).
Then click on Form2 tab to make it the active tab.
Now save the project and exit.

Open the project.
Double click on Form1 tab (must be double-click).
Crash.

I notice that the FireFly Workspace (on the right of screen shot)
is blank at the time of crash.

[Paul Squires]

Yup, you're right. Double-click crash...... I'll check into it today and get a fix.

[Paul Squires]

This was a hard bug to track down. Doubleclicking causes four Windows messages to be created. In addition, my special tab control created notification messages as well for the single and doubleclick. The problem seemed to be that the PropertyList would get confused as to what Form/Control was active between the time of the various messages.

I added code to repopulate the PropertyList prior to the final doubleclick notification being processed and that seems to have corrected the problem.