Hello all,
So, I am using symbol2list and list2symbol.

I am currently running up against what I think is an odd problem. I am taking a list and converting it to a symbol using list2symbol. Then, I am taking that symbol and converting it to the individual elements from the long symbol that is ALL of the elements from the list.

This is creating an unacceptable amount of lag in the program. Essentially my patch has in it:

| list a b c d e f g h i etc(
|
|list2symbol|
|
|symbol2list| using a zero-symbol as the delimiter.

As I said this creates a terrible drag on the system. Any ideas why?

Also, I am reconverting the symbol into a list to count the number of characters in the "symbol." Is there an object that does that so that I can skip this step?

Got it. It would seem to be an easy fix?

Did you see the "real" problem with symbol2list?

The patch seems to be working, but the annoying error shows

@raynovich If you only want to use one argument you could use something like that instead of [select]. It should support both symbol and float via right inlet (untested):

select+.pd

As to your symbol2list question, i would build it in vanilla, maybe i later find the time to build it...

There also seems to be an updated one that someone built that might improve the patch. When doing something like that, does one delete the "old" version and replace it with the new one? Or what?

@raynovich Surely you are free to do what you want on your own system.

To keep things clean, you can build your own library add it to search paths and in case of name conflicts can reference them in the patch as [mylibrary/objectname].

Oh of course just trying to get "good practice" feedback.

@raynovich Best place for your own library would probably be a directory within the regular externals directory

I am not being clear in my question. Sorry.

If one replaces a "standard" object from another "popular" library, should one delete the other object? Or should one change the name of YOUR object to be modified? Or should one keep both but make yours the "primary" object?

I hope this makes sense.

For instance, if I find or make a "better" symbol2list object, I should delete the old object and put the better one in the zexy folder. If I do that, though, if I send the path to another then I have to send my own zexy folder, which seems problematic.

@raynovich The thing is, when you update a library via menu "Find externals...." the updated object could be overwritten.

I would just use another name for my own object. That way there are also no conflicts if i share my patch with others.

To use the same name without deleting the original object from the library, you can make your own library in another directory and reference it with [mylibrary/objectname].

So in short, i would not overwrite existing libraries.

Got it. I did come up with another way to do it that seems a bit more elegant.

Using regex with getting the 3rd variable from the second outlet gets the same information.

And no error.

I probable could clean up this patch, anyway. But for now, it is working.