COM Dictionary property Item is not writable

[MHz]

Here is an issue if using Com with a Dictionary object. In brief summary, a Dictionary object can store any data type. Similar as to a collection, it store Keys and Items. These Key and Items can be Added, Read, Written and removed.

The Item property supports Read and Write while the Key property is Write only. The issue is with the Write ability of both Item and Key properties. This could be regarded as a Bug of AutoIt Com, or a feature that has not been implemented yet. So I will add it here for review.

Some basic examples

VBScript write to the Item property

Dim oDict
Set oDict =  CreateObject("Scripting.Dictionary")
If IsObject(oDict) Then
    oDict.Add "One", "Same"
    oDict.Item ("One") = "Changed" 'write
    MsgBox oDict.Item ("One")
End If

AutoIt write to the Item property

Global $oDict
$oDict =  ObjCreate('Scripting.Dictionary')
If IsObj($oDict) Then
    $oDict.Add ('One', 'Same')
    $oDict.Item ('One') = 'Changed' ;write
    MsgBox(0, '', $oDict.Item ('One') )
EndIf

VBScript works with the write while AutoIt does not. "Changed" should be the result shown in the MsgBox of both. Neither ot the above examples give error and seems like the " = 'Changed' " is completely ignored by AutoIt.

Trying to write to a Key property will only produce an error with AutoIt.

Any reason why Write (sometimes refered as to Set) to a Dictionary property is not achievable with AutoIt Com? Or perhaps any other property write without prior check if possible?

Edit:

Changed to valid comment character in VBScript example.

Edited August 10, 2006 by MHz

[MHz]

*Bump*

Time for another review for help on this.

[DaleHohm]

*Bump*

Time for another review for help on this.

I played around with this for a bit when you first posted it. I see nothing wrong with it and tossing in .value onto the objects didn't change anything (as it did with another COM problem recently worked). Assuming it works in VBS, then I'd suggest moving this to a bug and see if Sven can take a look at it.

Dale

[MHz]

Thankyou Dale for your time spared to look at this issue, along with anyone else who did. I have posted this issue in the Bug Forum here so it can move forward to hopefully being fixed.