Im having some trouble with this. So to get to it i have 16 "songitems" visible at once. In order to make sure the correct item is highlighted I have to do some math to find the index for said item. The highlighted portion is what is giving me problems. The patch currently only gets sent once so if [r nextpageitemtotal] is ever updated nothing happens or it only seams to finish once and that's it.

I need this to be triggered any time [r nextpageitemtotal] changes to then update the prepend object and in turn highlight the correct index if it is ever > 16.

I should mention if the banged index is less then 16 the new highligthed index should be 1-16

So if the banged index ends up == 17 the highlight index should be 1. If the banged index == 25 the highlighted index should be 9. If the banged index ends up == 32 the highlighted index should be 16. If the banged index == 48 the highlighted index should be 16 ect.

Any ideas how to fix this?

@RetroMaximus [mod] is your friend this time...... changed_index.pd
David.

Worked like a charm.

Everytime I post a question you guys have the answer or a great direction to look. My only problem is when corrections are made other things break. lol But I feel like im getting close.

Thanks you so much for your time and knowledge.

I have been dealing with these kind of errors and for the most part if i was to hold cntrl and click the error pd will open the patch that contains the error.

But I noticed sometimes things get overwritten and there is no way to know which inlet is throwing the error is there any way to modify pd to include a object number when a error is thrown in the console? That way I can open a txt file and track down the object by its number and get a better idea of what is wrong.

I keep getting

.. sorry, I couldn't find the source of that error.

inlet: expected 'float' but got 'list'

^^^^^^ this dosent really help me

But this might

inlet: expected 'float' but got 'list' in Overblast-Alpha.pd - obj# 100

Or maybe

inlet: expected 'float' but got 'list' in Overblast-Alpha.pd - obj# 1 , connection# 1

@RetroMaximus I don't know of a way to force Pd to find the error. In your screenshot it could be that clicking the very last in the list of identical errors...... and then pressing enter will find it?
If it is arriving continuously then you cannot do that, but you know that a [metro] is banging the message through, and you could stop the [metro] temporarily.
Clear the console, do something, and watch the console for the message coming again. That will give you a clue where it could be.
If you have the "zexy" library installed you can use [rawprint] to see more exact info on messages....... although [print] often gives enough info.

When you get that message it is sometimes that you have used a [list] object like [list prepend] and the outgoing message has been "tagged" as a list. You can use [list trim] afterwards to strip out the "list" tag..... but if the message starts with a float and has more elements it will remain a list so......?
When you find the error......if you just want one element from the list then use [$1( or [$2( etc. to send on the part you want...... or [unpack].
David

@RetroMaximus Maybe zip and upload your entire patch if you are still stuck on that error?
David.

I was stumbled on to where the errors stems from. Im not sure what im doing wrong tho.

I do have a github with the project currently but i do have to update it with the most recent fixes other then what im dealing with now. Im going to play around with this a bit more for a few hours see if i can figure it out and ill update the repository either way and post the link.

First i just noticed i should have removed the underscore from the [get_ind< [get_patt< [get_reps< and [get_state< messages in OBsPattItem.pd im still getting errors but things are changing.

sweet baby jesus i had the [f] connections swapped. The trigger: can only convert 's' to b or 'a' errors are gone. thats one bug off the list. wheeew!

Thank you once again

I just updated the repository with the latest version of the patch it is still a little broken but I feel like im making progress and getting a lot done now.

https://github.com/RetroMaximus/OverBlast-Alpha