Hi,
I tried to post this to bugtracker, but there was an error, so am posting here:
Hi,
I've read api-doc for ad_proc and callbacks, and see callbacks invoked in some package.info files. Yet, these are insufficient to understand how to create an implementation, or to assess if it worth the time in learning about them ie to know if they will be useful with the suite of packages I'm writing. In particular:
1. api-doc for ad_proc and callbacks don't mention the defined apm triggers in apm_supported_callback_types. It would be handy if these are referenced via @see somewhere in api-doc that is at an appropriate location, and to havemore @see cases for interlinking related info.
2. Does the apm provide any extra info not otherwise available via a proc in an tcl/*-init.tcl on startup?
If so, PLEASE HIGHLIGHT these cases, as they may be extra useful for package developers.
For example, does after-instantiate have the package_id available? If so, how to access via the callback?
Either refer to an existing case as example, or provide one. It is 10,000 times easier, less time consuming, and less of a learning curve to be able to copy/adapt instead of understand the abstract jargon created for this context or borrowed from multiple other contexts.
3. Are there any callback type triggers for parameter value changes?
This may be valuable for a suite of packages with extended services that share the same subsite.
thank you,
cheers,
Ben