Gang,

Not too sure if anyone has picked-up on this or not (based on discussion) over the past few weeks, but I've been slowly moving away from the Microsoft Forms naming convention and more towards the .NET naming scheme for Object Properties and Methods (where applicable). Having said that, I'm just wrapping-up Kixforms TNG and I'm stuck on an issue that I would like to get some feedback on. Specifically, the mechanism for setting the MouseCursor (or MouseIcon or MousePointer) ...

1) Strategy one is to have a property called MousePointer that gets or sets a numeric value indicating which icon to use (0 is the default arrow and 11 is the hourglass), for example:

code:
$Form.MousePointer = 11 ; Hourglass
 
; do something ...
 
$Form.MousePointer = 0 ; Arrow
To use a custom icon (.ICO or .CUR file), another property called MouseIcon is used to specify the path of the file, and the value of MousePointer is then set to 99 (user-defined), example:

code:
$Form.MouseIcon = ".\fraggers.ico"
 
$Form.MousePointer = 99 ; Custom jobbie
 
; do something ...
 
$Form.MousePointer = 0 ; Back to default arrow
2) Strategy two is to have just one variant (morphic) property called Cursor (.NET style) and provide the ability to get or set this value to a number (0 to 11) and/or set it to a string specifying a custom .ICO or .CUR file, for example:

code:
$Form.Cursor = 11 ; Hourglass
 
; do something ...
 
$Form.Cursor = 0 ; default
-and/or-

code:
$Form.Cursor = ".\fraggers.ico"
 
; do something ...
 
$Form.Cursor = 0 ; back to default
Thoughts anyone ? Is one strategy more intuitive than the other, is the second strategy to conviluted ?

-Shawn

[ 06. August 2002, 17:07: Message edited by: Shawn ]