WinFBE (64 and 32) 1.9.0 and 1.9.9 - Form's Property

[SeaVipe]

With 2 or more forms open in the visual designer, changing many of the properties for a form, then changing tabs to another form will match the property to the previous forms setting and set the form's need-to-be-saved flag (shows an asterisk beside the second forms name). Makes no difference whether or not the first form was saved.
I tried this with multiple forms open. All open forms where changed as I clicked on the next forms tab in Design not Code mode. (No change if the tab is set to Code only when it's set to Design.)
Some changes aren't accepted as there may be an existing setting preventing that from occurring.
Similar results with WinFBE 1.9.0.

[Paul Squires]

Hi Clive,

I see the problem. The save asterisk "*" appears because there is a bug when switching forms whereby when the new form gets focus, WinFBE will attempt to position the property listbox to the same named property that you were working on in the previous form. Nothing wrong with that....but, it also brings forward the previous Property VALUE as well. So, say for example, you selected "Enabled" to "False" and then immediately switched to another form, then that form's "Enabled" property would also switch to "False".

I have this narrowed down to properties that are based on combobox choices. It appears to be related based on the sequence of how the listbox is loaded and the firing of the CBN_SELCHANGE notification for the combobox properties.

I am investigating and hope to have a solid fix soon.

[Paul Squires]

It's funny how the brain works. No sooner than I had posted the above message, it popped in my head where the problem may lie. Sure enough, removing code from the Toolbox form that dealt with the form becoming ACTIVE/INACTIVE solved the problem.