07-08-2017, 10:43 AM
Would it be practical to add a pass-through function to classes to allow access to SDK functions that don't have an explicit interface in the CORE header, as a simple alternative to building a hybrid project to access a few simple functions?
For example, hdicoreDocument.h offers activate() const while the underlying AIDocumentList.h has (*Activate)( AIDocumentHandle document, ASBoolean bSetFocus ); I'd like to use CORE to get the relevant DocumentHandle(s) and, for example, Activate with bSetFocus set to false, access the dictionary, the modified state, file path, or other document criteria without bringing that window frontmost (don't want to frighten users with screens suddenly flashing). I would imagine that our IDE's autocomplete would help show a list of available options as well as the Adobe SDK itself so a simple boilerplate disclaimer may suffice for documentation.
For example, hdicoreDocument.h offers activate() const while the underlying AIDocumentList.h has (*Activate)( AIDocumentHandle document, ASBoolean bSetFocus ); I'd like to use CORE to get the relevant DocumentHandle(s) and, for example, Activate with bSetFocus set to false, access the dictionary, the modified state, file path, or other document criteria without bringing that window frontmost (don't want to frighten users with screens suddenly flashing). I would imagine that our IDE's autocomplete would help show a list of available options as well as the Adobe SDK itself so a simple boilerplate disclaimer may suffice for documentation.