[PD-dev] [ pure-data-Feature Requests-3525627 ] speed up the trigger-operations

[SourceForge.net]

Feature Requests item #3525627, was opened at 2012-05-10 13:42
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478073&aid=3525627&group_id=55736

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: speed up the trigger-operations

Initial Comment:
Hey,
I am just curious, is it possible to change the trigger-object to a pure-"graphic-enhancement"-object that could be called "sorted cables" or something.
It's just because the trigger-object is so slow in relation to what it does most of the time: sorting cables.
It even is faster to connect an outlet to a cold inlet and after that to a [bang] banging the hot inlet instead of using [t b f]. I know it's not much, but it becomes relevant when filling an array with eg. 100000 entries (...what was pd max integer??) . Even more if we assume that the arrays content has to be computed before, using trigger again. So there is a potential to save X times 100000 operations per array-calculation.
That's a little too much just for some grathical issue, especially if everything is hidden inside an abstraction in the end (or beneath a GUI) .
In general wasting cpu-time inhibits the creation of big patches or making them run on lots of hardware, doesn't it?
Bye

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478073&aid=3525627&group_id=55736