Why are mgrResetWorkspace(), xltDecReset(), xltEncReset() and findInfo() private functions ?
findInfo() is very useful to obtain a pointer to the callbacks or to the userData.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
IMHO, the main reason for keeping findInfo() private is because it depends on internals which could change in new versions of the RTK.
For example, I have added an option which makes the RTK thread-safe which completely replaces the workspace manager and therefore all related structures and routines, including findInfo().
Like you, I needed to obtain a pointer to userData, but the way to go is (again IMHO) to add a smlGetUserData() function rather than allowing access to internals - actually I added this as one of my very first mods of the RTK two years ago. I never needed smlGetCallBacks().
The mentioned additions and changes to the RTK should be on the way to be added to the CVS...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Why are mgrResetWorkspace(), xltDecReset(), xltEncReset() and findInfo() private functions ?
findInfo() is very useful to obtain a pointer to the callbacks or to the userData.
IMHO, the main reason for keeping findInfo() private is because it depends on internals which could change in new versions of the RTK.
For example, I have added an option which makes the RTK thread-safe which completely replaces the workspace manager and therefore all related structures and routines, including findInfo().
Like you, I needed to obtain a pointer to userData, but the way to go is (again IMHO) to add a smlGetUserData() function rather than allowing access to internals - actually I added this as one of my very first mods of the RTK two years ago. I never needed smlGetCallBacks().
The mentioned additions and changes to the RTK should be on the way to be added to the CVS...