Hi!
Dominic, if you write a patch, then do it on a little more general basis.
Allow ports to have freely choosable names.
But I think about the port names starting at one and then just going up has
a good reason: Who knows what the chosen client-names will be. It was nice to
name them foo and bar and whatever. But someone could do it like: foo, bar,
foo, whatever, bar... Some additional checking would be required. More
information would have to be stored: How many ports did I give away for this
client already?
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Ecasound-list mailing list
Ecasound-list@email-addr-hidden
https://lists.sourceforge.net/lists/listinfo/ecasound-list
Received on Mon Sep 8 12:15:02 2008
This archive was generated by hypermail 2.1.8 : Mon Sep 08 2008 - 12:15:02 EEST