The Maxleft behavior might not be a bug. Most of my projects are like suites, and allow the user to open several MDI forms in a "top-level" form.

Ignoring MaxLeft after load allows the user to move the form to the left to see whats underneath!

A better solution would be for the fox team (anyone listening) to add a variable opacity/translucency propert for the form so that the user could look through the form to see whats underneath. All the futuristic movies I've seen ("Final Fantasy" was one), showed consoles with translucent overlays. I also saw one product on TECH-TV that allowed the user to tweak the form's transparency so that what was underneath could be revealed!

It was cool - but the holographic consoles in "Final Fantasy" are the the best I've ever seen.


>>The max properties also seem to affect autocenter. Have you noticed this?
>
>Yes, it is correct because MaxLeft and MaxTop is a limit of the form position.
>
>But MaxLeft is used only when the form is created;
>after it is ignored ( one of the bugs i found on this subject )
>
>Put two buttons B1,B2 with :
>

>B1.click
>thisform.Autocenter = .T. && <=== this ignore MaxLeft
>
>B2.click
>thisform.MaxLeft = m.thisform.MaxLeft && <== this fire C internal code
>
>

>
>The VFPT implement it for this master task:
>

>thisform.MaxLeft = sysm(0)- 40 && force the form into the desktop area
>* and put next line in moved event
>thisform.MaxLeft = m.thisform.MaxLeft
>
>* but this can to be done with the next line into the Moved event
>thisform.Left = MIN(m.thisform.Left,sysm(0)- 40)
>

>
>Then, because MaxLeft and MaxTop are passive properties, they are useless.
>
>Fabio