in some recent wiki edits, some descriptions for error return codes were added. However, it seems that they all refer to Open, which looks like a copy/paste error. For example:
The error code returned by ##**Close**## can be checked using ##[[KeyPgErr|Err]]## in the next line. The function version of ##**Open**## returns directly the error code as a 32 bit ##[[KeyPgLong|Long]]##.
maybe the list of function compatible with ERR() could simply be included in the ERR() page. Then the other side telling at each concerned function pages that they work with ERR() could wait.
The typical source of need for this information is to be able to be confirmed that FileExists is not bound to ERR() even if FileCopy() is. A list in the Err() page would provide the info anyway.
dkl wrote:in some recent wiki edits, some descriptions for error return codes were added. However, it seems that they all refer to Open, which looks like a copy/paste error.
It was I who made that mistake.
It is normal that I correct.
Another thing: ImageCreate() doesn't return an error code of course, because it returns the image pointer or NULL. (but it still sets the error code for Err())
dkl wrote:ImageCreate() doesn't return an error code of course, because it returns the image pointer or NULL. (but it still sets the error code for Err())
KeyPgImagecreate → fxm [ImageCreate() doesn't return an error code of course, because it returns the image pointer or NULL.] KeyPgErr → fxm [ImageCreate() doesn't return an error code of course, because it returns the image pointer or NULL.]