Is there a way to turn off "automatically declare stage instances" on a per-symbol basis?

Question

This would be an incredibly useful feature, and would eliminate 99% of those "1152: A conflict exists with inherited definition... in namespace public".
Generally, this option is off for my main flash document, but in individual "lesson" swfs that I load into it, most of the content in those are not class-backed, so I leave "automatically declare stage instances" on at the document level (currently the only level to specify this option) for those lesson swfs.
However, in one of those "lesson" swfs, there are two library symbols that I would like to have the same base class.  They have the same child instances with the same names, just with different sizes (e.g. one is a main idea with two fields, the other is the same thing, but the fields are bigger).  When I set both of these to use the "MainIdea" class as thier "base class" (defined in an external SWC, but not relevant here), I get the confict error, because Flash tries to generate it's own class for each object (inheriting from the base class I specified), but that base class already has those identifiers defined.
So, ideally, I would like to be able to stop flash from trying to atomatically declare stage instances on those particular symbols that specify a base class.  In fact, it makes sense to me that for any symbol that's given an explicit base class, Flash Authoring should either never try to automatically declare stage instances (since the presense of a base class would imply the presense of pre-defined instance variables) or should give the developer the option at the symbol-level, so that this conflict would not occur.  Even when it does occur, it should be a warning rather than an error, since Flash Authoring could simply not re-define the variable if it already exists in the base class.
A potential work around, which doesn't even work and which defeats the purpose of using a single shared base class for multiple symbols, is to actually define a unique class file for each symbol (which both inherit from the base class), so that Flash doesn't try to automatically declare stage instances for it, but Flash still tries to automatically generate stage instances.
Final recommendation: I really think Flash would be much better off if the "automatically declare stage instances" option would resolve the conflicts itself by simply not declaring already-declared properties for symbols that use a defined class or base class.  Instead, it should just show a warning saying "I tried to automatically define a property for this stage instance, but it's base class already defined it, and that's ok!"

Answer 1

Have a look at this YouTube movie, explaining how to replace the simple action by a oneliner standard action to prevent the playhead of being released:
http://www.youtube.com/watch?v=M3nKi-DB6Fw&feature=plcp   sorry, but I cannot use the link button (to have a meaningful text) in Chrome.
If you prefer readng:
http://blog.lilybiri.com/why-choose-standard-over-simple-action
Lilybiri