Return to Bugs & Features · Post Text · Post File
| ID: | 106 |
|---|---|
| Status: | 5 - New |
| Priority: | 1 - Request for Enhancement, e.g. asking for a feature |
| Scope: | 3 - Applies to all machines and operating systems |
| Subsystem: | Unassigned |
| Summary: | Add context to all callbacks |
| Version: | Trunk |
| Created By: | alonbl |
| Assigned To: | Unassigned |
| Fix Version: | Unassigned |
| Update Notification: |
Trouble Report Files:
No files
Trouble Report Dialog:
| Name/Time/Date | Text |
|---|---|
| alonbl 02:00 May 22, 2010 | Continue bug#66. Another example is the mxmlSetErrorCallback() which has no context assigned. It would be much easier to use if there is ability to set some void* context. Also, I am not sure I understand why the error callback is thread specific. This kind of library usually needs no global context. First argument of every function may provide the necessary context. For the error callback, except of context it would be nice to get a details of the object that caused the error, or have a separate callback for errors during parsing. For example, if I parse 3 XML I want to present a different messages for each [without using globals]. Thanks |
| alonbl 02:06 May 22, 2010 | Also, return last callback from set, so can restore after use. |