>>I guess you could call it "docking", but having it take up the entire width of the screen isn't my idea of "dockable".
>
>I have the command window docked on the bottom of the screen and the properties window on the right edge. It works well for me.
>
>>What would be cool is if it presented a button like the tabs on the project manager do when they're docked. Then you could drop it down when necessary.
>
>Hmmm, maybe, but I think that would get annoying, somethign Apple would do :-)

It might, but you'd have a choice as to how its set up.

>>BTW, that the _SCREEN has its own property sheet is a nice touch. I haven't fiddled to much with it, but if those settings were automatically translated and stored with the project, that would be handy too. I don't know if this is the case, however.
>
>I don't think anything like that exists. What would be cool, is if in the combo of the properties sheet, you chould choose between _screen and _vfp properties.

It does make me wonder why they'd bother with a property sheet for the screen. It's not exactly something that folks do a lot of fiddling with. If, however, it was part of the project, it would help reduce some code overhead. For me, I use AddProperty() and AddObject() with the _SCREEN to store what previously would have been global variables, since there's no way (even via CLEAR ALL) that they can be accidentally released. You have to do so implicitedly.

Agree about the _VFP system variable.