>>It may not be just the cursor class.
>>
>>We try to avoid using TOP, LEFT, HEIGHT, and WIDTH on any classes that are not theoretically visual, even if they happen to have those properties exposed. We don't put assign or access methods on those properties if we do dare to use them... this is something you probably already know about...
>>
>>We also don't define properties with those names on classes that *don't* appear to have those properties. They may not be exposed, but there's still probably some common behavior associated with those theoretically common native properties that's screwed up. Somebody cheated somewhere <g>.
>>
>>>L<
>
>Somebody cheated somewhere <g>.
>
>That was my impression too ;-)

When I tweaked the class browser code to include dataenvironment of a form, I used the regular code which outputs all non-default PEMs, just the same as it does for other classes, and guess what - it found .width and .height for cursors. I.e. these properties do exist in the scx file. Here's what I found in the first one I looked at:

Top = 20
Left = 10
Height = 90
Width = 106
Alias = "events"
BufferModeOverride = 0
Database = cpdb.dbc
CursorSource = "events"
Name = "curEvents"

That's the content of the properties memo in the scx.

So, yes, someone cheated :).