Forum Discussion

OV's avatar
OV
Frequent Contributor
8 years ago

How to make script run time quicker

Hi,   I have this function I wrote and each time the script need to do the checks in this function it takes loads of time. The function is looking for a home button, the home button looks the same...
OV's avatar
OV
Frequent Contributor
8 years ago

Are you still talking about the if condition to check if 

Home button is visible?

 

I did added 

 

Sys.Refresh()
Aliases.RefreshMappingInfo()

 

And still the value of VisibleOnScreen and \Visible if False.

karthick7's avatar
karthick7
Contributor
8 years ago

please tell what properties used to find that object?

  • OV's avatar
    OV
    Frequent Contributor
    8 years ago

    if(HomeButton.Exists && HomeButton.Enabled) and seems like it doesn't work because now i'm coming from totally different screen and it thinks the HomeButton exists it looks like there's no escape but to use the Visible or VisibleOnScreen to make sure the HomeButton truly appears on the screen. how can we do that?

     

    I've used var HomeButton = BreadScrumpTree.FindChild("ClrFullClassName","System.Windows.Controls.Button", 8);

     

    Thanks

  • OV's avatar
    OV
    Frequent Contributor
    8 years ago

    The problem here is that every time i'm coming to a similar screen but from different component so tc will concatenate the object i'm coming from to the home button. for example:

     

    if i'm coming from datasources tc will create the following home button string:

    Aliases.QuickDesign_ConfigurationManager.BreadsScrumpTree.DataSourcesControl.Border.DataSourceHomeButton.Visible

    if i'm coming from functionaltc will create the following:

    Aliases.QuickDesign_ConfigurationManager.BreadsScrumpTree.FunctionalItemsControl.Border.FunctionalItemsHomeButton._NewEnum

     

    Thant's why it's a bit mess, it's the same HomeButton but a totally different object

     

    That's why in my original script i had to wait for the VisibleOnScreen property to be tru for each pattern and that waisted time because tc had to wait for that property

     

    Aliases.QuickDesign_ConfigurationManager.BreadsScrumpTree.AutomationBindingsControl.WaitProperty("VisibleOnScreen", true, 1000))

  • OV's avatar
    OV
    Frequent Contributor
    8 years ago

    But I can't understand why the value of HomeButton is False in the runtime in the watch list while when i'm changing to the object browser it is true??? we must get that sorted first