Here's a typing error that I found in the documentation when looking at the doc for "ControlSendKeys":
"To send keyboard characters that are comprised of a regular keystroke in combination with a SHIFT, CTRL, or ALT, crete a compound "
"crete" should be "create".
Note: Maybe this thread should be used to post all documentation bugs so that they are consolidated.
Typing errors in documentation file
Another one that caused me to spend a day on my script...
MouseClickElement():
"If the function succeeds, the return value is zero, otherwise the return value is an error code. "
In my case, when the function succeeds, it returns 1, and when it fails, it returns 0.
I have noted that there are many inconsistencies in the return codes for various functions. Just a suggestion for the next version, it would be easier for developers to compare the return code to a pre-defined constant.
Here's a Python code to show what I mean:
rc = Ranorex.MouseClickElement(eMyElement)
if (rc == Ranorex.RC_OK):
print "Success"
else:
print "Fail"
MouseClickElement():
"If the function succeeds, the return value is zero, otherwise the return value is an error code. "
In my case, when the function succeeds, it returns 1, and when it fails, it returns 0.
I have noted that there are many inconsistencies in the return codes for various functions. Just a suggestion for the next version, it would be easier for developers to compare the return code to a pre-defined constant.
Here's a Python code to show what I mean:
rc = Ranorex.MouseClickElement(eMyElement)
if (rc == Ranorex.RC_OK):
print "Success"
else:
print "Fail"
Thank you for this important info, we checked the call chain of the mouse functions and found a bug. It can happen, that the functions MouseMoveToElement and MouseClickElement return a false value.
We corrected the bug for the next version V1.1.0.
We have a lot of user and we want to be compatible with earlier versions.
Jenö
We corrected the bug for the next version V1.1.0.
Good idea, but unfortunately we cannot support this in the next release.tkondal wrote:Just a suggestion for the next version, it would be easier for developers to compare the return code to a pre-defined constant.
We have a lot of user and we want to be compatible with earlier versions.
Jenö
Ranorex 1.1 Doc Typo
I noticed in the documentation for 1.1 that there is a "File List" item with "RanorexPython.cpp" in it; is this supposed to be there?
Also, the entry for "Menu Functions" has a ".n" appended to it.
Also, the entry for "Menu Functions" has a ".n" appended to it.
TreeViewGetSelectedItem
In the doc for Ranorex.TreeViewGetSelectedItem, it says:
The handle of the next item if successful,...
I'm guessing this should be :
The handle of the selected item if successful,...
The handle of the next item if successful,...
I'm guessing this should be :
The handle of the selected item if successful,...
Thanks for this info...
Gabor
Ranorex Team
You can find the corrected docu in the next release...In the doc for Ranorex.TreeViewGetSelectedItem, it says:
The handle of the next item if successful,...
I'm guessing this should be :
The handle of the selected item if successful,...
The whole documentation will be generated automatically. This file will be appended.I noticed in the documentation for 1.1 that there is a "File List" item with "RanorexPython.cpp" in it; is this supposed to be there?
This is a type error, we will fix it for the next release.Also, the entry for "Menu Functions" has a ".n" appended to it.
Gabor
Ranorex Team
RanorexPython.ApplicationGetFirst
RanorexPython.ApplicationGetFirst
The documentation is misleading, the return type should be handle if successful, and 0 if not.
The documentation is misleading, the return type should be handle if successful, and 0 if not.
Thank you for this info, we have corrected the documentation for the next release.
Please read also the post:
http://www.ranorex.com/forum/applicatio ... -t147.html
Jenö
Ranorex Team
Please read also the post:
http://www.ranorex.com/forum/applicatio ... -t147.html
Jenö
Ranorex Team