AutomaticComponentToolkit
AutomaticComponentToolkit copied to clipboard
Autodesk
A toolkit to automatically generate software components: abstract API, implementation stubs and language bindings
It would be great to have a way to globalize error codes across different components. This would make it very powerful for developing distributed applications and plugin concept, and could...
Component injection works only with slight custom editing of the headers and passing raw Refs around, but this is not a good long-term solution. We have no good concept for...
Given a journal file that has been output we would like to be able to attempt to replay it. This would be a small program that will read a given...
I have an ACT function called Point which adds a point to a stream. The point is a class and has an x, y, z. The journal that is output...
I accidentally created a method definition with two result values and ACT did not warn me and not fail creating code (just interpreted the XML wrong). I think there should...
If there is an out optionalclass value, the code generator creates a base result variable: IBase * pBaseHandlerInstance(nullptr); This leads to a compile error of the implementation. The class should...
The default stub C++ base class implementation stores error strings in a list but does not account for querying it twice via ACT.
The error strings of the IDL are not automatically written into the code which makes standard exceptions a bit dull.
**Problem:** NodeJS bindings do not implement inheritance **Source:** https://github.com/3MFConsortium/lib3mf/issues/188. E.g. for [lib3mf.xml]:(https://github.com/3MFConsortium/lib3mf/blob/master/AutomaticComponentToolkit/lib3mf.xml) Node bindings don't inherit from parent classes, so for example `CObjectIterator` only has its own methods (`GetCurrentObject`), and...
Documentation for elements in ACT IDL is currently specified like so: ```XML ``` Having the description as an attribute makes perfect sense, but when writing an IDL file it makes...
