I was about to make this topic! With the same name even...
I haven't had the families bug happen to me actually. Doesn't construct already prompt you to add the variables to the object when adding an object to a family without using the family manager? (It does for me.)
The bug might be caused by 1. adding variables to an object. then, 2. adding the object to a family with variables. I'm guessing this may be the case, as I have never had a problem with family variables, even when adding extra pv's to an object already part of a family with variables. I'll test this when I get home.
I feel that certain things should be labeled as unstable in construct 1.0. Possibly just an added sentence to the plug-in description or tool-tip or whatever. Namely, things that are buggy as hell and nigh unusable. Transitions fall into this category, and possibly the layout object also. Anything that's half complete, or incompatible with other things, or causes crashes that are deemed to difficult to fix, or not worth fixing, should be left labeled with "USE AT YOUR OWN RISK: UNSTABLE." By all means, if the bug is discovered to be easy to fix, then fix it and lose the message.
Getting rid of the plug-in or feature completely is a bad idea, as it would break existing .caps, and more importantly, give construct one less feature, even if it be buggy. Sometimes, even a buggy feature can fill needs of one person. They may use it in just the right way that all's well and fine for them. As such, I feel the unstable label is the best way to go about warning users about the stability of a plug-in or feature.
[size=150:1sh98rv6]Davio's 2 Show-stopping bugs[/size:1sh98rv6]
1. Crashes on layout change.
Bug is (I think) related to keyboard input, or sound. Limiter enabled checkbox in Xaudio2 may be at fault. Sounds across layouts are also suspects. Freeing cache and stopping sounds before layout change seems to have an effect on bug. Crashing also may be due to layout switching in general. Hard to pinpoint exactly, as there are many factors. Investigation needed.
2. Clicking on multi-subevented and/or grouped event structures, or actions within them
This sometimes results in the wrong event being selected. (eg. an action or event within a collapsed group or sub-event becomes selected when clicking on the parent event, or an action in the parent event.).
Sometimes, upon clicking on an action within a complex hierarchy or events, the entire hierarchy of events is selected. This is especially dangerous when one makes heavy use of control+drag to copy actions.(i.e, me.) This can lead to the click and drag facepalm, a situation in which a group of literally hundreds of events is selected and cloned when all one wanted to do is clone a simple set width action with control+drag. I even ran into an instance of this bug where my entire 1500+ event sheet was duplicated.
This bug wouldn't be so bad if it was rare. It happens a lot. Every click I make is carefully placed as to not upset the event sheet gods.