Perhaps I just am horrible at searching, but I can't seem to find any docs on the full CorelDraw API. For example, if I record a macro to export an AI file, I see calls to ActiveDocument and ExportFilter:
Dim expflt As ExportFilter
Set expflt = ActiveDocument.ExportEx("ExportTest001.ai", cdrAI, cdrAllPages, expopt)
Yes, I can not find one entry in the API docs linked from this area:
https://community.coreldraw.com/sdk/api/draw/23.5
I can't find ANY info at all about an object named ActiveDocument and the info provided for ExportFilter is woefully incomplete:
https://community.coreldraw.com/sdk/api/draw/23.5/c/exportfilter
I see nothing that documents all the various properties that the macro recorder seems to know about:
With expflt .Version = 10 ' FilterAILib.aiVersionCS6 .TextAsCurves = False .PreserveTransparency = True .ConvertSpotColors = False .SimulateOutlines = False .SimulateFills = False .IncludePlacedImages = True .IncludePreview = True .EmbedColorProfile = True .Finish End With
With expflt
.Version = 10 ' FilterAILib.aiVersionCS6
.TextAsCurves = False
.PreserveTransparency = True
.ConvertSpotColors = False
.SimulateOutlines = False
.SimulateFills = False
.IncludePlacedImages = True
.IncludePreview = True
.EmbedColorProfile = True
.Finish
End With
Am I missing something? Or is this really all there is?
J^2
While both of those are definitely useful, they're still not actual API Docs. And while I agree having scripting is nice, as with any professionally developed application I would pay for, I expect that if you offer a feature, you will fully support it. If you are going to provide an API, you have to document it. That's just good development practice in general...
I guess I will have to wait and see how the Mac version grows. Maybe they'll get really savvy and provide a proper Python API...
I don't think they are doing Python for the MAC Version, I thought it was all JavaScript and it has a long way to go before it is usable.
Sadly, I know. I would love to be able to run all our production apps natively. Alas, without the ability to integrate our current toolset to the degree we can in Corel, it's kind useless to us.
<sigh>
As for why they went with JS instead of Python, I have no idea what thought process was going on there.