Hi Richard et al...
I agree with Richard, in fact, his often well-thought expression of MetaCard's strict compliance to the vanilla is the primary reason why I'm 'attempting' to switch to MC (I'm sure a first, going back to MC from one who has started with RR:-)
I believe the alwaysBuffer should be set true for the IDE to display properly (else it's a bug in the IDE?). I also agree, we should not 'pre-modify' any default behaviors of the engine. That is, IMHO, why the default for stacks should be 'true' for alwaysbuffer AND set by the engine, not the IDE.
Rev has indeed already moved quite a ways down the slippery slope. I've spend a few hours lately converting my altPlugins for use in MC, and have already discovered a couple of such anomolies-- things I never knew Rev did until trying them in the MC IDE.
Of course, it's super easy to add a MC plugin (I have one) which can create a new stack and set the alwaysBuffer to true.
best to you all,
Chipp _______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
