A named inlet bringing up an error where it didn't before

#1

So this error is seemingly happening for no reason... I have had this patch for quite a while and never had any errors, now all of a sudden the compiler has issues without it, although it has been running without a hitch for several months now.

What it is, i have a switch case to choose between inlets and outlets based on an int select number. Here is the console log of the error

What i find so odd is that this code works! i worked last time i used it on saturday with no issues, the inlet is called inlet_i4.

Here is the once working but now not, code fragment
And the object itself
chain selection.axo (1.3 KB)

Any help is much appreciated as i really have no idea whats happening here, doesn't make any sense, also means i cant run my patch D:

To add to the confusion, this same object runs without any issues inside a different patch

#2

I downloaded and it loads correctly. Are you sure that's the object generating the error?
If that's the case, are you using it as an embedded object? Maybe you inadvertitely added a space to the inlet name (it happens)

#3

Are you sure that's the object generating the error?

Yep, its the only object in my patch with an inlet up to 4, also the only object with a switch case

are you using it as an embedded object?

Yea i always tend to do this with my own objects

Maybe you inadvertitely added a space to the inlet name

Yes 100%. I've also tried changing the inlet name to something unrelated, yet when i run it still shows the same error in the console for inlet_i4, even though there isn't anything called inlet_i4 in my patch now, and the one that was is called something different, it still points to this....
For anyone else i think this is the biggest oddity here, i completely remove that object and i get the same error messages, still getting it when i remove all custom objects so only the factory ones are left.

#4

Here is the patch with no custom objects but still getting the error, if you wanna join in the confusion party, its in full swing right now patch no custom.axp (13.9 KB)

#5

impossible to say, how you got into this situation, but your object does not have an inlet called i4 , so thats why it doesn't compile.
perhaps you deleted the inlet because you weren't using it.

Screen Shot 2017-03-27 at 19.57.24.png1424x982 108 KB

#6

My apologies i think i described the end improperly, i uploaded the patch without all my objects to see if it would compile for other people, i shall upload the proper project now, and it is here Main Project Patch.axp (22.5 KB)

Out of interest could you compile and run the previous patch ok ? as i said earlier when i tried i still got the case4:inlet_i4; error

#7

as i said, your patcher/object is wrong, it doesnt have i4 defined (see my screenshot) , so thats why it doesn't compile. sure if I add inlet_i4 it compiles fine.

perhaps your confused, because you see 4 inlets? but these are starting labelled i0 to i3 , i4 would be a 5th (value) inlet.

#8

issue came from removing an inlet on the mux and, and that inlet in the code happened to be the default option for the switch in the mux object

#9

No the error you first posted comes from instanceLFO::mux 1 , look at the stack trace

#10

Yes just found the error. thank you so much! although it was more of me being bit of an idiot!