04-26-2016, 09:49 AM
There's no problem with various objects sharing callbacks, we do that in lots of places in our projects.
The method you're looking for is hdi::core:lugin::currentTool()
And, as the notes for the hdi::core::Tool::aiToolHandle() method state, you needn't worry about those internal data accessors (the vast majority of the time). The goal of CORE is to provide classes that wrap around Illustrator's objects/data/etc. and expose their functionality, and needing to access those internals runs counter to the goal. If something can be done with that internal data that is "typical", then that functionality should already be present in CORE or added if it isn't.
The method you're looking for is hdi::core:lugin::currentTool()
And, as the notes for the hdi::core::Tool::aiToolHandle() method state, you needn't worry about those internal data accessors (the vast majority of the time). The goal of CORE is to provide classes that wrap around Illustrator's objects/data/etc. and expose their functionality, and needing to access those internals runs counter to the goal. If something can be done with that internal data that is "typical", then that functionality should already be present in CORE or added if it isn't.