Adobe sort of "hacked" support for large canvases. They did not actually change the PDF spec to support document sizes any larger than roughly 19-feet across – they simply apply a scaler to everything in the document to simulate it being 190-feet across. As such, yes, one decimal point of precision is lost.
hdi_core abstracts the whole issue such that using our functions/methods to move an object "10pts" really only moves it 1pt but the Illustrator UI reports a 10pts delta (as it should due to the scaler).
The CurrentDocument:: scale() method simply reports 1x for "normal canvas" mode or 10x for "large canvas" mode. We thought it prudent to provide the method regardless of the fact hdi_core abstracts away the whole issue through the various SDK calls it wraps (i.e. we do not yet wrap every single SDK call in existence, so a consumer of our lib can still utilize some unwrapped call with the proper scaler if needed).
Adobe used to have a feature to explicitly enable large canvas mode in a normal-sized document, hence the notifier. They later removed it in favor of automatically enabling large canvas mode only when a document is created.
hdi_core abstracts the whole issue such that using our functions/methods to move an object "10pts" really only moves it 1pt but the Illustrator UI reports a 10pts delta (as it should due to the scaler).
The CurrentDocument:: scale() method simply reports 1x for "normal canvas" mode or 10x for "large canvas" mode. We thought it prudent to provide the method regardless of the fact hdi_core abstracts away the whole issue through the various SDK calls it wraps (i.e. we do not yet wrap every single SDK call in existence, so a consumer of our lib can still utilize some unwrapped call with the proper scaler if needed).
Adobe used to have a feature to explicitly enable large canvas mode in a normal-sized document, hence the notifier. They later removed it in favor of automatically enabling large canvas mode only when a document is created.