Unexpected Behavior with ControlCommand SelectString

[ijourneaux]

I have done a number of AutoIt based projects. and this the first time I have experienced this. I have a combobox with a number of choices.Of particular interest are two related choices "Base Moisture" and "Base Moisture Actuator" 

A call to ControlCommand to set "Base Moisture" results in "Base Moisture Actuator" being selected. In the ComboBox, "Base Moisture Actuator" is the first item in the list "Base Moisture" is the 10th or 12th item in the list. 

$InfostoreTitle = "InfoStore"
SelectSensor("Base Moisture")
SelectSensor("Base Moisture Actuators")

Exit

Func SelectSensor( $sSensorStr)
$test = ControlCommand($InfostoreTitle, "", "[CLASS:ThunderRT6ComboBox; INSTANCE:2]", "SelectString", $sSensorStr)
msgbox(0, "test", $test)
EndFunc

Any thoughts what might be causing this behavior?

 

[abberration]

This may not be the issue, but I found this bit of information in the AutoIt help file:

  Quote

You should note that underlined menu items actually contain a & character to indicate the underlining. Thus, the menu item File would actually require the text "&File", and Convert would require "Con&vert"

That was from WinMenuSelectItem. Have you tried this function instead of ControlCommand?

[jchd]

Have you tried issuing first a "FindString" command (requires an exact match, I hope it means up to EOL) then "SetCurrentSelection" with the occurence number returned by the previous call?

[ijourneaux]

  Quote

Have you tried issuing first a "FindString" command (requires an exact match, I hope it means up to EOL) then "SetCurrentSelection" with the occurence number returned by the previous call? 

 I have not tried that but it is worth a shot. It doesn't explain the odd behavior of ControlCommand  but if it gets me past the problem, I am all for it.

[jchd]

It looks like the string comparison in "SelectString" is like StringInStr(<ComboValue>, $str) and stops early on first (partial) match. If the term "exact match" is true, that shouldn't be the case for "FindString", hopefully.

Crossing fingers...

[ijourneaux]

Thank you jchd! Your recommendation worked. If this isn't a bug, then there probably needs to be an option to control the behavior of SetCurrentSelection. Regardless, I appreciate the help!

Ian

[jchd]

I don't believe it's something AutoIt can do anything against: only Windows has control over what it actually does when a control is sent the command "FindString". But maybe I'm completely wrong thinking this way: I easily confess no experience nor even basic knowledge on GUIs and their elements.

Yet I'm glad it worked that way.

[ijourneaux]

You are absolutely correct. The combobox Findstring command "Returns the index of the first item in the ComboBox that starts with the specified string" .  If that is what is being used by SetCurrentSelection, we are getting what is expected.

There is an other option for the comboxbox "FindStringExact". It would be nice if SetCurrentSelection could select between the two.