[L2Ork-dev] Bug in route

[Ivica Bukvic]

All this makes perfect sense. The reason why I was asking is because I
remember introducing a patch that is not currently a part of the regular PD
but was proposed to change the way how select and route specifically deal
with data types and I cannot recall whether this is a part of the change.
So in other words I'm not sure if this was originally a regression or an
architectural choice to make things more streamlined. The challenge's that
in PD there are way too many objects that are overloaded with
functionalities that seem like an afterthought rather than I genuinely
separate object. The fact that the route can be used both as a route and a
selector to me is something that is not and optimal approach. It is all too
eminent of the idea that if something has been done long enough the wrong
way it will be eventually seen as the right way which is not what I think
is true at all. In other words I'm not so much questioning your patch as
much as I'm questioning what has caused the inconsistency in the first
place.

At any rate, let me search for that old patch and try to find out whether
the things you have fixed are essentially reverting the patch in question
and furthermore to study the rationale behind the change introduced by the
patch.
On Oct 8, 2013 3:20 PM, "Albert Graef" <aggraef at gmail.com> wrote:

> On Tue, Oct 8, 2013 at 5:08 PM, Ivica Ico Bukvic <ico.bukvic at gmail.com>
> wrote:
> > Are all the other conditions still valid (as in other modes)? pd-l2ork's
> > route differs on a number of counts from vanilla route, although its
> > operation should remain consistent (apart from additional options).
>
> I tried all the examples in route-help.pd and its subpatches, and with
> my changes they all work as described in those help patches. This
> covers all the different uses. Don't take my word for it; try it for
> yourself. :) Specifically, have a look at the type_mode subpatch, this
> covers the cases where pd-l2ork currently does the wrong thing. If you
> click on the [89( and [float 7( messages in the type_mode subpatch, it
> should bang the second outlet of [route] (which it does) and also
> output the number in the corresponding number box (which it doesn't).
> A similar issue arises with the [symbol pie( message and the symbol
> selector. These issues are fixed by my proposed changeset.
>
> If you still don't believe me, just look at the code itself. Your code
> clearly does the wrong thing, it will always output a bang in response
> to a float or a symbol.
>
> Note that this isn't just some esoteric corner case. It's a real bug
> which actually breaks one of my patches that works fine with vanilla
> Pd and previously used to run fine with pd-l2ork, too.
>
> Albert
>
> --
> Dr. Albert Gr"af
> Dept. of Music-Informatics, University of Mainz, Germany
> Email:  aggraef at gmail.com
> WWW:    https://plus.google.com/111193356966611167754
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> http://disis.music.vt.edu/listinfo/l2ork-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20131008/95f2505c/attachment-0001.html>