Testy email. ________________________________ From: Raffaele Fragapane [[email protected]] Sent: 01 April 2015 05:28 AM To: [email protected] Subject: Re: ICE Custom ICE Data type not exposing in compound?
You might also need to add something to the compound xml or an event, I have very hazy memories of work-arounds and stuff, but that was for multiple ports bundled into port groups (incidentally something that JUST came up at work, again, today). On Wed, Apr 1, 2015 at 1:30 PM, Steven Caron <[email protected]<mailto:[email protected]>> wrote: The node behaves as you would expect when you add more port instances and when it isn't inside a compound. The port is defined last, I will try and move it around, but the node is so simple I would just be putting it first. The Syflex node I referenced has the force ports in the middle. Might be onto something there My current (not completely tested) work around is to change the port definition to support an array instead of instances and put a build array node in between the custom node and the exposed port. Bummer... Steven *written with my thumbs On Mar 31, 2015 4:45 PM, "Raffaele Fragapane" <[email protected]<mailto:[email protected]>> wrote: Does it work if it's outside a compound? I have had some issues with dynamically adding ports to groups, some of them pretty bug smelling, but all of them, including one with custom data types, disappear if the group with dynamic ports is the last one in the definition. You could also try and give that a shot, but it's more of a head in the sand workaround than a fix for anything. -- Our users will know fear and cower before our software! Ship it! Ship it and let them flee like the dogs they are! <table width="100%" border="0" cellspacing="0" cellpadding="0" style="width:100%;"> <tr> <td align="left" style="text-align:justify;"><font face="arial,sans-serif" size="1" color="#999999"><span style="font-size:11px;">This communication is intended for the addressee only. It is confidential. If you have received this communication in error, please notify us immediately and destroy the original message. You may not copy or disseminate this communication without the permission of the University. Only authorised signatories are competent to enter into agreements on behalf of the University and recipients are thus advised that the content of this message may not be legally binding on the University and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of The University of the Witwatersrand, Johannesburg. All agreements between the University and outsiders are subject to South African Law unless the University agrees in writing to the contrary. </span></font></td> </tr> </table
