Page 1 of 1

Invalidating WPF tree

Posted: Sun Jan 22, 2012 12:43 pm
by omerkarpas
Hi,

We are experiencing a problem while working with a control containing WPF tree (on Windows7). After pressing "Apply" button (see ScreenBeforeChangesAndApply screenshot) we can't access the same tree elements (see SpyAfterApply screenshot). It looks like the Spy (the same happens in the C# code with Ranorex Studio) shows "old" tree control and not the updated one. I also don't understand what`s the meaning of {Disconnected Item} of any check box in the tree. We tried to run it several times and it`s constantly happens after "Apply", we did tried to close the spy and reopen it, but still have got the same results. Please assist us with this issue, how can we overcome it and access the tree nodes?

Thanks,
Omer.

Re: Invalidating WPF tree

Posted: Mon Jan 23, 2012 12:31 pm
by Support Team
Hi,
omerkarpas wrote:Please assist us with this issue, how can we overcome it and access the tree nodes?
After you've clicked the apply button on your application, did you try to refresh the element tree of Spy? Did you try to track one of these elements?

Regards,
Peter
Ranorex Team

Re: Invalidating WPF tree

Posted: Mon Jan 23, 2012 1:41 pm
by omerkarpas
Of course, we refresh the Spy every time we tried to access the tree elements. We have been working with Ranorex for several month, so we are familiar well with the basics.

Re: Invalidating WPF tree

Posted: Mon Jan 23, 2012 6:01 pm
by Support Team
Could you also post Ranorex snapshots of the form before and after pressing the "Apply" button? See this section in the Ranorex User Guide on how to create Ranorex snapshots.
omerkarpas wrote:Of course, we refresh the Spy every time we tried to access the tree elements.
So even after a refresh of the element tree in Spy or after tracking the dialog anew, the elements corresponding to the tree are not updated?

Is this the standard WPF tree control or a specialized one?
Ranorex uses UIAutomation (UIA) to recognize controls within WPF applications and if the elements are not update at all, I can only imagine that this control has a special UIA implementation that is somehow broken.

Regards,
Alex
Ranorex Team