Tunescope being strange

why does this work

but not this


when put into the

block? it seems like they report the exact same list...

I suspect the issue is with TuneScope not being able to handle a linked list, such as resulting from an _ in front of _ operation.

For reference, see this topic.

The simplest solution is preprocessing the input of Play tracks using the id of _ block.

Technical detail

id of_ will always report a dynamic array; both linked list and dynamic array are implementations of Snap!’s list data type; the difference shouldn’t matter to you or me as users, but sometimes it does - in this case: due to a construction error within Tunescope.

About one year ago I ran into several issues with Tunescope, and as a result I made several improvements to Tunescope - you may want to try them.

how do I unlink a list
EDIT: I can use the ID block

Yeah, tunescope is a huge mess, which makes me sad, since I love the idea of tunescope, I just don't like it's implementation (which made me create my own modification to improve upon almost everything in it, though I don't know if I knew about this linked lists bug. Also, a few of my improvements were actually implemented into the official library, but not all of them).

My version of Tunescope (see post #1 for a link) contains both improved original Tunescope blocks, and additions, IIRC each of my blocks has an online help text.

Glad I could help!

@bh can @ego-lay_atman-bay's extension be whitelisted?

What do you mean by this?

if you click on his blocks using the extension format you need to enable js for them to work because his extension url isnt whitelisted in snp.

Ah, I get it.

It might not be likely, since if someone's URL was whitelisted, there could be a possibility that they could make another extension that could run malicious code without asking the user, and a lot of the extensions come from organizations or other Berkeley sites; however, I really do trust ego-lay_atman-bay, and I know he won't do anything of the sorts, so I too propose his extension gets whitelisted.

IMO the real solution is @glenbull improving the official library.

Actually, TuneScope was developed by students at some college.

It was: University of Virginia, to be precise. Glen Bull is a professor there.

We've been trying to get to this for a while now. As noted elsewhere on this thread, the library was actually created by a group of computer science students working at The University of Virginia. Those students have since graduated, and we haven't been able to find another group with both the aptitude and the interest to take on the project. Additionally, we've been swamped with other projects that limit our own resources. Ideally, I would love to see an update pushed out sometime soon, but realistically we're in a bit of a holding pattern at the moment.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.