alwaysBuffer not set...

[Richard Gaskin]

Wouter wrote:

>> > I noticed in the latest DL of MetaCard, the alwaysBuffer of most IDE
>> > stacks is not set. While this was not necessary in previous versions of
>> > the engine, it is now used to disable the 'flashing' effect around
>> > windowsXP look and feel.
>> >
>> > I recommend setting the alwaysBuffer of all IDE stacks to true.
>>
>> I agree that it should be the default setting, and can add a preference
>> for that. But with modern systems being how they are I would go further
>> to request that it be changed in the engine.
> 
> Why going to that extend? It is only 1 line of code? Sounds like overkill.
> The default alwaysbuffer of the templatestack is false, both in MC and RR.
> But in RR they set this property of the templatestack in the "New 
> Mainstack" case of the menupick handler
> Why not add this 1 line (or more if more properties ought to be set) to 
> the "New Stack" menupick handler of the "file" button?

Re-reading Chipp's post more carefully, he's referring only to IDE 
stacks, and yes, the IDE stacks should have their alwaysBuffer set to 
true.

Can anyone think of a reason not to?  Unless someone tells me not to I'm 
inclined to do it for the next release.


As for doing that for all new stacks, I would happily add it as a 
preference (and will do so after this next build is released), but I'm 
disinclined to make non-optional changes that contradict how the engine 
works.

Admittedly I'm a bit of a Transcript purist, but I feel one of the most 
useful aspects of the MC IDE is that it keeps you close to engine 
behaviors, minimizing differences between development and runtime, and 
keeping any additional libraries fully optional and under the 
developer's control.

If we were to start down the slippery slope of altering behaviors from 
how they work in the engine and requiring specific additional scripts to 
get the behaviors we expect, we not only complicate our work but also 
miss the opportunity to improve the engine itself.

If we feel a default behavior is incorrect or suboptimal, it seems a 
good opportunity to address it at the source in the engine itself.

I can think of no reason to have the alwaysBuffer set to false (though 
there might be so we should retain the property as an option), and agree 
that having it on by default would be far better than its current 
default behavior.  Shall we post it to Bugzilla and see if it gets any 
votes?

-- 
  Richard Gaskin
  Fourth World Media Corporation
  ___________________________________________________________
  Ambassador at FourthWorld.com       http://www.FourthWorld.com