Opened 11 years ago
Closed 11 years ago
#2664 closed Feature Request (Rejected)
_GUICtrlListView_GetItemText - proposal
Reported by: | mlipok | Owned by: | |
---|---|---|---|
Milestone: | Component: | Documentation | |
Version: | Severity: | None | |
Keywords: | Cc: |
Description
Add description something like this:
"If item or subitem not exist then function will return an empty string"
Attachments (0)
Change History (6)
comment:1 Changed 11 years ago by mlipok
comment:2 Changed 11 years ago by Melba23
As an item/subitem could quite easily contain an empty string, I do not think that this is a reasonable proposal - how would you distinguish between a valid empty return and one returned by a non-existent item/subitem?
Also looking at the function in detail I cannot see an easy way to determine whether a returned item/subitem value is from a valid element. So in this case I believe it must be incumbent on the coder to do the necessary parameter checking before calling the function - the UDF should not need to do this for itself.
M23
comment:3 Changed 11 years ago by mlipok
Thanks for your comments.
You have right UDF should not need do this.
but...
It would be good to do a note in HelpFile about it.
Because how you say:
"So in this case I believe it must be incumbent on the coder to do the necessary parameter checking before calling the function"
But he (coder) want to know about this incumbent.
comment:4 Changed 11 years ago by Melba23
The same remark could be made for any number of UDF functions. Either we add error-checking code to each and every UDF function - or we rely on the coder to check parameters before calling those which do not have a specific error return. I would class parameter limit checking as standard coding practice and not something that should be remarked upon for every function.
M23
comment:5 Changed 11 years ago by mlipok
Thanks for the clarification.
If no one else has any other comments you can close this ticket.
comment:6 Changed 11 years ago by guinness
- Resolution set to Rejected
- Status changed from new to closed
I have no comment to what has already been said.
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'm sorry too stingy description.
In one of the scripts I had a situation in which I used the index non-existent, which caused some complications.
I noticed that this function does not return any errors in the @error and @extended so I thought that the documentation could use at least a relevant mention of.
Please give favorable consideration to my proposal.