Thanks,
I don't use the enable/disable property as to identify the object.i do use what you suggest but, the button in the first screen is disabled and for the next few screens it's enable.so i used simple code line for testing it's status as follows:
//Check the buttons caption in the first install screen
if(Aliases["MSIEXEC"]["BaseScreen"]["btnBack"]["WaitProperty"]("WndCaption", DDT["CurrentDriver"]["Value"]("CheckPoint"),5000))
Log["Message"]("PASS " + DDT["CurrentDriver"]["Value"]("Component") + " Checkpoint",Aliases["MSIEXEC"]["BaseScreen"]["btnBack"]["WndCaption"])
else
Log["Message"]("FAIL " + DDT["CurrentDriver"]["Value"]("Component") + " Checkpoint",Aliases["MSIEXEC"]["BaseScreen"]["btnBack"]["WndCaption"])
//Log a Picture of the object
Log["Picture"](Aliases["MSIEXEC"]["BaseScreen"]["btnBack"],"Picture of the object")
//Check if the value of the Enable property of the button is True or False
if(Aliases["MSIEXEC"]["BaseScreen"]["btnBack"]["WaitProperty"]("Enable","False"),500)
Log["Message"]("The BACK button status is DISABLE")
else
Log["Warning"]("The BACK button status is ENABLE")
is that the right way?is there a better way.i must say that i can see the time it takes TC to verify this enable value during runtime.
thanks