Forum Discussion

cvanvlack's avatar
cvanvlack
Occasional Contributor
5 months ago
Solved

What is the correct format for WaitWPFObject in Python?

Here is the name mapping when I use the object spy I am running the application and getting the process with  process <SPAN class="token operator">=</SPAN> TestedApps<SPAN class="token pun...
  • cvanvlack's avatar
    cvanvlack
    4 months ago

    This was SUPER helpful. Thank you very much!!

    Here is what I learned after using this example. 

    1. Basically, whatever arguments you can get to work for the WPFObject Method, you need to use the exact same arguments for the WaitWPFObject Method.

    2. I had misread the API and thought the WndCaption was optional. So I passed the ClassName, but left off the WndCaption so the function overloaded to assume I was passing in the Name.

    So when I was using 

    p = Sys.Process("VirtekIrisClient")
    o = p.WaitWPFObject("HwndSource: ShellView",timeout_ms)

    It wouldn't work. When I used

    p = Sys.Process("VirtekIrisClient")
    o = p.WaitWPFObject("HwndSource: ShellView","Virtek Iris",timeout_ms)

    It worked.

cvanvlack's avatar
cvanvlack
Occasional Contributor

Thanks for the response! I have absolutely no idea what happened with those code blocks as that's not what I had put there... I'll try to edit the original message to try to fix it.

cvanvlack's avatar
cvanvlack
Occasional Contributor
5 months ago

The code blocks keep adding that stupid span object. Here's the actual code.
p = TestedApps.Virtek_Applications_ServerManager.Run(count, ignore_running, timeout_ms)
o = p.WaitWPFObject('WPFObject("HwndSource: ShellView", "Virtek Iris")', timeout_ms)
o.Exists

  • cvanvlack's avatar
    cvanvlack
    Occasional Contributor
    5 months ago

    I can confirm that


    p = TestedApps.Virtek_Applications_ServerManager.Run(count, ignore_running, timeout_ms)
    o = p.WaitWPFObject("WPFObject", "HwndSource: ShellView", timeout_ms)
    o.Exists

    Also did not work

      • cvanvlack's avatar
        cvanvlack
        Occasional Contributor
        4 months ago

        Thank you for providing that link. I had come across it as well. 

        The problem is that there are multiple different objects that are referred to and it's almost impossible to figure out which one is meant (hence why I put the screenshot of the Object Spy).

        For instance, Addressing Objects in WPF Applications shows the following API formats:

        WPFObject(NativeName)

        WPFObject(NETClassName, Caption, [Index])

        whereas WaitWPFObject Method uses 

        TestObj.WaitWPFObject(Name, Timeout)

        TestObj.WaitWPFObject(ClassName, WndCaption, Timeout)

        TestObj.WaitWPFObject(ClassName, WndCaption, Index, Timeout)

        Is NativeName equivalent to Name? Is NETClassName equivalent to ClassName?

        From my screenshot, there is a Name field which is why, in the code I supplied, I tried using Name = 'WPFObject("HwndSource: ShellView", "Virtek Iris")'.

        From my screenshot, I don't see any other class objects other than WndClass, but that has me suspicious because it looks like there is some kind of uniqueID attached, which will cause problems when we open multiple windows.

        It looks like there are extra .NET parameters

        But using 
        o = Sys.Process("VirtekIrisClient").WaitWPFObject("HwndSource", "HwndSource: ShellView", timeout_ms)

        Or 

        o = Sys.Process("VirtekIrisClient").WaitWPFObject("System.Windows.Interop.HwndSource", "HwndSource: ShellView", timeout_ms)

        also doesn't work. 

        I'm not sure where to go with this considering being able to verify that windows are opened or closed is a pretty critical requirement for a test automation software and, according to Checking Whether an Object Exists, 

        Get the desired object using the appropriate WaitNNN method. For example:

        In desktop applications, use WaitProcess, WaitWindow, WaitWinFormsObject and so on.

        But I can't seem to get them to work...