Property Set *RESOLVED*

If, say for example, I am passing an imagelist to a property would I use:

VB Code:

Public Property Set ImageList(ByVal Value As Object)
    Set milsImageList = Value
End Property
 
Public Property Get ImageList() As Object
    Set ImageList = milsImageList
End Property

or

VB Code:

Public Property Set ImageList(ByVal Value As Variant)
    Set milsImageList = Value
End Property
 
Public Property Get ImageList() As Variant
    Set ImageList = milsImageList
End Property

Basically, Variant or Object as the passed parameter...?

Woka

If you know what you are setting/getting then you should declare it as what it is:

VB Code:

' Class declarations
 
Private m_TextBox As TextBox
 
Public Property Get NotePad As TextBox
 
' I can't ever remember if you need to use Set here or not
Set NotePad = m_TextBox
 
End Property
Public Property Set NotePad(TextBox As TextBox)
 
' ditto about using Set
Set m_TextBox = TextBox
 
End Property

Can't do...Can't decalare an imagelist as a varible in a public property in a DLL, VB won't allow it :(

Is ImageList just a property name? Aren't there any controls or class that has that name? Anyway, I only want to say that i was a bit confused with your sample code. You used Byval keyword for an Object type variable. To what I understand, Object type variables, even for some Variant subtypes, can only be passed ByRef-erence.

Dunno about that, but ByVal works fine...

Gush. I'm talking in a Marsian language!

Sorry bout that! Kinda tensed being a newbie.
:D

I think you would use Set, but for no other reason then it seems to be the industry standard when working with Objects and it more clearly defines that in fact you are working with Object(s) since they are the only thing that gets set. Although functionaly they are the same.

I always do use SET...:D
Do I pass the object in as a Variant, or as an Object varible???

Woka

Variants are universal. They can hold almost any var types.
Should I use variant param for objects, i always check if passed value is an object, eg

VB Code:

Public Property Set PropName(YourParam as Variant)
    If Not IsObject(YourParam) Then
        'Raise an error
    End If
    Set mPropName = YourParam
End Property

Unlike declaring [YourParam] as Object, VB will do the validating,eg

VB Code:

Public Property Set PropName(YourParam as Object)
    Set mPropName = YourParam
End Property

Either way, ok.
Something like that.

Hope I'm in the right lang now. :rolleyes:

Well since a variant can hold an object or other types of data and we know that the control is an object then object seems the lesser evil. Although I'm not sure it matters much. Also declaring it as an Object will force you to use set and follow the rules for an object more than a variant.

That's what I thought :D

Cheers for your replies...

Woka