Opened 15 years ago
Closed 15 years ago
#1137 closed Feature Request (Completed)
Change RegEnumKey/RegEnumVal error return to be more sensible.
| Reported by: | xelotiac@… | Owned by: | Valik |
|---|---|---|---|
| Milestone: | 3.3.1.2 | Component: | AutoIt |
| Version: | Severity: | None | |
| Keywords: | Cc: |
Description
Hello,
I hope it will not be 'is a feature, not a bug' ;)
Both functions, RegEnumKey / RegEnumVal, delivers if there is no valid key or no more key available german sentence like 'Das System kann die angegebene Datei nicht finden' Or 'Es sind keine Daten mehr verfügbar'. So I have to use always additional string function to check the return value of it. The string info is more exact than the available error codes (differents between 'not exist' and 'not anymore exists'. How about a Return Value like and add this different as a new error cde.
Thanks for reading,
Sebastian
Attachments (0)
Change History (8)
comment:1 Changed 15 years ago by Valik
- Summary changed from RegEnumKey / RegEnumVal Return Value to Change RegEnumKey/RegEnumVal error return to be more sensible.
- Type changed from Bug to Feature Request
- Version 3.3.0.0 deleted
comment:2 Changed 15 years ago by Jpm
Today you already get 2 different @error 1 and -1.
In case more information is needed I add @extended setting equal to Windows return code which usely will be 2 and 103
comment:3 Changed 15 years ago by Valik
The return value contains a text string describing the error. This is WRONG. The return value should be an empty string.
comment:4 Changed 15 years ago by Jpm
- Milestone set to 3.3.1.2
- Owner set to Jpm
- Resolution set to Completed
- Status changed from new to closed
Added in version: 3.3.1.2
comment:5 Changed 15 years ago by Valik
- Milestone 3.3.1.2 deleted
- Resolution Completed deleted
- Status changed from closed to reopened
This is not completed in a satisfactory way. In fact the change completely ignores the problem I have with the function which is that it returns an error string on failure. The changes to @extended are superfluous and unnecessary.
In short revision 5141 needs completely reverted.
comment:6 Changed 15 years ago by Jpm
- Milestone set to 3.3.1.2
- Resolution set to Fixed
- Status changed from reopened to closed
comment:7 Changed 15 years ago by Valik
- Milestone 3.3.1.2 deleted
- Resolution Fixed deleted
- Status changed from closed to reopened
Err, please actually read why I reopened this ticket.
comment:8 Changed 15 years ago by Valik
- Milestone set to 3.3.1.2
- Owner changed from Jpm to Valik
- Resolution set to Completed
- Status changed from reopened to closed
Changed in version: 3.3.1.2
Guidelines for posting comments:
- You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
- In-depth discussions should take place on the forum.
For more information see the full version of the ticket guidelines here.
I don't think this is a bug, but I do think the behavior should be changed. Adjusting ticket to reflect a feature request.