>>I spent an hour trying to disable a command button. I set the Enabled property False - it
>>came back on, it put This.Enabled = .F. in the Init - it came back on, form's Activate - it
>>came back on, and Show - it came back on, and other places, and it wasn't until an hour into
>>it when I found some obscure code down in the framework doing something with Refresh().
>
>Bill Mason, I believe, told you earlier that you have to override certain buttons in the refresh().

I thought there was the framework hook somewhere, .OverrideZombieButton(tlKillDeadNow) or something...?

>>The feeling I get is that my knowledge and experience in VFP is negated because I now have
>>to learn new ways to do simple task all over again.
>>
>>The purpose of a framework should be to make my life easier, not more difficult.
>
>I understand your frustration. I go through the same thing everytime I join another developer's project. :)

What surprises me is how different system-level bugs attack different developing teams. I've seen extensive code in frameworks working around some horrible bug which would be a total showstopper... actually, in only one framework. Nobody else had that problem. Then another framework would have some other layer of code which works around some other problem, that nobody else had.

For instance, the current framework I'm using keeps reissuing Console Off. There's a reason for that - in some situations, error condition would reopen console output, and a rogue component would cause woutput() to scroll, because it not only reopens error channel (2), it opens stdout (1) for whichever reason. Which I understand - I've fought my set of phantoms at times, and I had to write framework code that nobody else needed, because nobody knew the trouble I saw.

So there's that bit of defense against Saharan polar bears in almost every framework - each one had some incongruent animals it had to fend off, that nobody else had to. Or maybe the others just found simpler workarounds. How many times have we read "oh so it's not just me" here? ;).