Hi Jason,
I faced the same problem on normal (Javascript) ThingShape's, ThingTemplates when they added the limitation on 6.5.
What I came out was to add a ThingShape to all the things which it's the only one that subscribes to ThingStart event, and that ThingShape subscription it's the one which does the "constructor" function. The idea it's to call a "Init_"+Shape/Template name on each implemented / inherited, and then you just need to implement that one whenever you want to initialize something on the corresponding ThingShape/ThingTemplate. It's not the most efficient way, but without multiple subscriptions to the same thing/event from the same Thing, this it's the best we can get. It's a shame they limited it, still I don't understand why, and I had though conversations with R&D about it...
Here it's the code of my ThingStart Subscription ( you can do it with a Try/Catch or with a check !=undefined on the Service Name ):
// -- Initialize Implemented Shapes
var implementedShapes = me.GetImplementedShapes();
var nImplementedShapes = implementedShapes.rows.length;
for (var i=0;i<nImplementedShapes;i++) {
var shape = implementedShapes.rows;
if (shape.name!=="myThingShapeName") {
try {
me["Init_"+shape.name]();
} catch(err) {
}
}
}
// -- Initialize ThingTemplate/Shape Hierarchy Top-Down
var methodsToCall = [];
methodsToCall.push("Init_"+me.name);
var parentName = me.thingTemplate;
methodsToCall.push("Init_"+parentName);
var parent = ThingTemplates[parentName];
while (parentName) {
parentName = parent.GetBaseThingTemplate();
if (!parentName) {
break;
}
methodsToCall.push("Init_"+parentName);
parent = ThingTemplates[parentName];
}
while (methodsToCall.length) {
try {
me[methodsToCall.pop()]();
} catch(err) {
}
}
