Object no loger working

[Champak]

I had the following COM function working previously under xp and the old autoit

Func _IMAGETRANSPARENTCOLOR($FIMAGE = "", $FIMAGEOLDCOLOR = "", $FIMAGENEWCOLOR = "")
;#cs
If Not FileExists($FIMAGE) Then
  _CONSOLEWRITE("! Image: '" & $FIMAGE & "' not detected. - : - (Line = " & @ScriptLineNumber & ")")
  $FIMAGE = $IMAGE_GENERAL_ARRAY[0]
EndIf
$OIMAGECONVERT.LoadBitmap($FIMAGE)
$OIMAGECONVERT.ChangeColorDepth(0)
$OIMAGECONVERT.ReplaceColor($FIMAGEOLDCOLOR, $FIMAGENEWCOLOR, 1)
$OIMAGECONVERT.SaveBitmap($FIMAGE)
;#ce
EndFunc   ;==>_IMAGETRANSPARENTCOLOR

The instructions for the object are as follows and shows that I'm using it properly, and yes I verified the object is declared, registered, and compat with win7, and the full path and file is in the string,:

====================================================

object.LoadBitmap(File as string)

====================================================

But scite is now giving me the following error:

ScriptsInfiniti NavINavM.au3 (5030) : ==> Expected a "=" operator in assignment statement.:
$OIMAGECONVERT.LoadBitmap($FIMAGE)
$OIMAGECONVERT^ ERROR

Why am I now getting this error now? How can I fix this? Thanks.

Edited February 6, 2012 by Champak

[Xenobiologist]

Which version of Autoit?

[Champak]

v3.3.8.1

[Champak]

bump

[jaberwacky]

It's probably best if you post the entire script. Unless you don't intend to release the source. If that is the case then ignore this post.

[Champak]

I figured it out, but it doesnt make sense why it worked on the previous autoit.

I had it as (where each lies in the script):

1/ set image and call function that has the object

2/ set up object

3/ the function that is being called that has the object

I had to rearrange it to:

1/ set up object

2/ set image and call function that has the object

3/ the function that is being called that has the object

Granted, the way i have it now makes logical sense, but I just dont understand why it worked with the previous autoit and not now, and why it was giving that particular error.