<br><br><div class="gmail_quote">On Thu, May 22, 2008 at 7:38 AM, Pau Arumí <<a href="mailto:parumi@iua.upf.edu">parumi@iua.upf.edu</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On dc, 2008-05-21 at 12:19 -0300, Francisco Tufró wrote:<br>
> Great, is done.<br>
<br>
Excellent! commit 11394.<br>
<div class="Ih2E3d"><br>
> A question:<br>
> what about the callback interface for cascading events?<br>
> should we add that feature now or later??<br>
<br>
</div>Later (=when some MIDI use case asks for it).<br>
The same for "Publishers" (publishers are proxy entities that publishes<br>
ports/controls to the processing composite interface.<br>
<br>
> Well, what's next?<br>
<br>
1. Make the IsConnected and IsConnectedTo interface to the base class</blockquote><div>I've done this, but i'm not sure if i did what you wanted. Do you want me to move mLinks from the template class to the base?, i've only added the isconnected and isconnected to to the base classes. See the patch.<br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
2. Integrate with Processing base class and make it usable from the<br>
Network interface (and thus from NetworkEditor)</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
For 2, consider if it is worth "merge" the Typed*Control base class with<br>
the current control base class. Or otherwise, keep them separated.<br>
It would be useful to start with a list of implications on both<br>
decisions.</blockquote><div><br>I'll take a deeper look into the Processing and Network classes to answer this.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<font color="#888888"><br>
Pau<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
<br>
<br>
> Francisco<br>
><br>
> On Wed, May 21, 2008 at 5:19 AM, Pau Arumí <<a href="mailto:parumi@iua.upf.edu">parumi@iua.upf.edu</a>> wrote:<br>
> On dt, 2008-05-20 at 20:02 -0300, Francisco Tufró wrote:<br>
> > Hi, i have almost finished the Link test.<br>
> > I have this question:<br>
> > How do i (or what do i do to) handle errors with these<br>
> functions, in<br>
> > the first what should i do? make the function bool and<br>
> return true if<br>
> > it was connected?? or throw something with a special error<br>
> class that<br>
> > i ignore?<br>
><br>
><br>
> Let's take the restrictive and easier path: just assert in the<br>
> error<br>
> case. Like we do in Ports. I say it's easier because we avoid<br>
> dealing<br>
> with exception handling.<br>
> OutPort.hxx line 175<br>
><br>
> And (doxygen) document this behavior, and explaining that<br>
> before calling<br>
> Link the user must check the likability with IsLinkable<br>
><br>
> See ports unit tests for an example of how to test that an<br>
> assert is<br>
> triggered.<br>
><br>
> Pau<br>
><br>
><br>
><br>
> ><br>
> > void BaseTypedOutControl::Link(BaseTypedInControl&<br>
> in)<br>
> > {<br>
> > if(IsLinkable(in)){<br>
> > DoTypedLink(in);<br>
> > }<br>
> > /* Throw error with else! ? */<br>
> > }<br>
> ><br>
> > and:<br>
> ><br>
> > template<class TypedControlData><br>
> > void<br>
> ><br>
> TypedOutControl<TypedControlData>::DoTypedLink(BaseTypedInControl& in)<br>
> > {<br>
> > AddLink(dynamic_cast< ProperTypedInControl& >(in));<br>
> > }<br>
> ><br>
> > by the way i send the patch so you have the full code.<br>
> > bye!<br>
> > Francisco<br>
> ><br>
><br>
> > _______________________________________________<br>
> > Clam-devel mailing list<br>
> > <a href="mailto:Clam-devel@llistes.projectes.lafarga.org">Clam-devel@llistes.projectes.lafarga.org</a><br>
> ><br>
> <a href="https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel" target="_blank">https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel</a><br>
><br>
><br>
> _______________________________________________<br>
> Clam-devel mailing list<br>
> <a href="mailto:Clam-devel@llistes.projectes.lafarga.org">Clam-devel@llistes.projectes.lafarga.org</a><br>
> <a href="https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel" target="_blank">https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel</a><br>
><br>
> _______________________________________________<br>
> Clam-devel mailing list<br>
> <a href="mailto:Clam-devel@llistes.projectes.lafarga.org">Clam-devel@llistes.projectes.lafarga.org</a><br>
> <a href="https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel" target="_blank">https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel</a><br>
<br>
<br>
_______________________________________________<br>
Clam-devel mailing list<br>
<a href="mailto:Clam-devel@llistes.projectes.lafarga.org">Clam-devel@llistes.projectes.lafarga.org</a><br>
<a href="https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel" target="_blank">https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel</a><br>
</div></div></blockquote></div><br>