As I understand, in order to export a module's interface (e.g. create a C header file with the interface), one needs to assign the module a unique ObjectID (a number between 30,000 to 32,767).
However, in a large design (which I'm doing right now), the process becomes very cumbersome and lengthy, as I have to go to each module and assign the unique number (making sure it is is unique). It is also a very slow process (especially with large designs).
I believe it should be simpler to just have a check box in the Build tab of the module's properties, where one can just indicate that he/she wants to export the module interface. The system (e.g. AW designer) should assign ObjectID automatically and manage it internally. This will save a lot of time and work.
10:18am
Hello Yair,
You can automatically assign an Object ID to a module by right clicking on the module and navigating to 'ObjectIDs > Assign'. Audio Weaver will automatically assign a valid unused ObjectID to the module. Hope this helps!
Thanks,
Kevin
11:48am
Thanks Kevin, this looks like a much better way of doing things.
A question: Assume I have a module that I have assigned its object ID automatically (or a sub system where few of the modules were assigned object ID automatically): What Happen when I make a copy of the module or sub-system? Will the system automatically re-assign a new available ID to the copies, or will it complain that the given ID was already in use?
12:16pm
Currently you will need to manually clear the assigned custom object ID in the Copy and the then Assign a new custom ID.
This may change in future releases.