Opened 12 years ago
Closed 12 years ago
#2690 closed Feature Request (Fixed)
Win..... Return Value Proposal.
| Reported by: | mlipok | Owned by: | guinness |
|---|---|---|---|
| Milestone: | 3.3.11.6 | Component: | Documentation |
| Version: | Severity: | None | |
| Keywords: | Cc: |
Description
in WinGetTitle
if no title match.
vWinClose
WinMove
if window is not found.
in WinGetState
if the window is not found.
in WinGetProcess
just "-1."
in WinGetHandle
if no window matches the criteria.
in WinGetCaretPos
just "Sets the @error flag to 1."
in WinExists
otherwise.
Please consider standardizing descriptions.
Attachments (0)
Change History (5)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
In fact the best harmonization need AutoIt code change not just the doc,
to set @error in such case.
That was not the initial AutoIt philosophy of returning error on Builtin. Only when the successful return value cannot be differentiate, the @error was set.
comment:3 by , 12 years ago
| Summary: | Win..... Retrurn Value Proposal. → Win..... Return Value Proposal. |
|---|
comment:4 by , 12 years ago
jpm
I understood your statement.
However, perhaps my post was an understood differently than I wanted.
I'll be back over the weekend to this topic.
comment:5 by , 12 years ago
| Milestone: | → 3.3.11.6 |
|---|---|
| Owner: | set to |
| Resolution: | → Fixed |
| Status: | new → closed |
Fixed by revision [10136] in version: 3.3.11.6

sorry for too short a description.
Please note that in the description of the function of Win ...., see "Return Value" for the case of "Failure" for the same event are various descriptions (I do not mean different values and only way to describe).
As an example of a good / full, description, give
"if no window Matches the criteria"
but extended
"if no window Matches the criteria (Title and Text)"
I think it will harmonize documentation and facilitate understanding, especially for those who do not necessarily speak English well.