Not sure if this is an issue of Ranorex or of the implementation of the DevExpress TreeList.
I have a treelist that contains data of currencies from around the world. For example: 105,78ман. In this example the , is a decimal point not a number grouping.
When I view the treelist item from RanorexSpy I get "105.78". If I view a similar item in a text box (not a tree list item) from RanorexSpy I get back what I would expect (I.e. "211560,00ман").
Is this an issue with the way DevExpress is returning the data back through MSAA or a way that Ranorex sees the data?
See attached screen shot for the invalid cell data and the valid data.
I have also attached a RanorexSpy snapshot.
Issue reading currency data from a DevExpress TreeListEx
Issue reading currency data from a DevExpress TreeListEx
You do not have the required permissions to view the files attached to this post.
If this or any response has helped you, please reply to the thread stating that it worked so other people with a similar issue will know how you fixed your issue!
Ciege...
Ciege...
Re: Issue reading currency data from a DevExpress TreeListEx
Just to add a bit more information.
The data returned from a DevExpress grid is as expected. It does return the proper data that is displayed in a grid cell.
So it seems that just the data that is returned from a tree list cell is incorrect.
The data returned from a DevExpress grid is as expected. It does return the proper data that is displayed in a grid cell.
So it seems that just the data that is returned from a tree list cell is incorrect.
If this or any response has helped you, please reply to the thread stating that it worked so other people with a similar issue will know how you fixed your issue!
Ciege...
Ciege...
Re: Issue reading currency data from a DevExpress TreeListEx
OK, so I solved this by using InvokeRemotely on the tree node and returning the .GetDisplayText of the tree node.
So I am now able to get the data that I need to continue.
So I am now able to get the data that I need to continue.
If this or any response has helped you, please reply to the thread stating that it worked so other people with a similar issue will know how you fixed your issue!
Ciege...
Ciege...