Discuss Scratch

cookieclickerer33
Scratcher
1000+ posts

(Get [list] separated by [text])

This block would act like the
(list :: list)
For these examples, assume “list” contains a, b, and c
Reporter, but it would let you seperate each item with different text that isn’t just a space for example
(Get [list v] separated by [-]::list)
Would return “a-b-c”
(Get [list v] separated by [space]::list)//pretend it’s the space character
Would return a b c as it is right now. But if “list” was 1, 2, and 3. Instead of returning “123” like clicking the list block would do, it would return “1 2 3”

(Get [list v] separated by []::list)
Would return abc
You could even do some really intresting stuff with newline
(Get [list v] separated by [newline]::list)//pretend it’s the newline character

As newline actually works in return functions it would report this:
A
B
C
As a bubble! (I’ve tried this and it works)

Lmk your thoughts on this!


cookieclickerer33
Scratcher
1000+ posts

(Get [list] separated by [text])

Boing
IndexErrorException
Scratcher
500+ posts

(Get [list] separated by [text])

Major support. I have had to implement this on a few occasions and it's an annoying algorithm to make. Also it makes quite a few junk variables and more.

JavaScript already has string.split method so it should be quite easy for the ST to implement this, of course this doesn't mean anything as they haven't implemented the exponent reporter after over a decade of people asking.
cookieclickerer33
Scratcher
1000+ posts

(Get [list] separated by [text])

IndexErrorException wrote:

Major support. I have had to implement this on a few occasions and it's an annoying algorithm to make. Also it makes quite a few junk variables and more.

JavaScript already has string.split method so it should be quite easy for the ST to implement this, of course this doesn't mean anything as they haven't implemented the exponent reporter after over a decade of people asking.
about the exponent reporter

paddle2see wrote:

Exactly. Every cheap calculator has this function while Scratch does not. We have hyperbolic logarithms but we don't have a simple raise-to-the-power function. It's a stunning oversight that I have been bemoaning since the dawn of the Scratch age.
source: https://scratch.mit.edu/discuss/topic/2860/?page=30#post-7519263

theres a high chance its being worked on

this would be super useful in basically every context that uses lists, this would also get rid of the weird feature where if all the items are 1 character it reports it as a text string without seperators. this can mess up ALOT of things. having the ability to do this even if all the items are diffrent, and being able to return them seperated with all the items being 1 character makes for a ton of usibility

TLDR: every single context that lists can be used in is improoved by having this block

im mainly looking at the newline use as i made an entire extension adding first class lists that uses newline to display them

Last edited by cookieclickerer33 (Oct. 28, 2023 15:09:00)

cookieclickerer33
Scratcher
1000+ posts

(Get [list] separated by [text])

I recently found you can rename and delete lists via the dropdowns. So I don’t even see much of a reason to keep the list reporter arround

The list blocks would be shown by defalt and clicking on any of the dropdowns would let you create a new list (or they could keep the current system just without the list reporter) or they could just keep them both I don’t see an issue with that
medians
Scratcher
1000+ posts

(Get [list] separated by [text])

Actually.. there's a thing about the space thing.

Basically, if all of the items are one character long and it recognizes each thing as a character.
So if you did:
add [1] to [list v]

It would recognize that as a string/character.
But if you did ((1) + (0)) instead, it would separate them:

Last edited by medians (Oct. 30, 2023 13:39:33)

cookieclickerer33
Scratcher
1000+ posts

(Get [list] separated by [text])

Well I wouldn’t know because lists are completely different in snap
medians
Scratcher
1000+ posts

(Get [list] separated by [text])

cookieclickerer33 wrote:

Well I wouldn’t know because lists are completely different in snap
Yea I get that, it's kinda weird but interesting LOL.
Also, this behavior occurs in Scratch 3.0 as well. And topic 53 is related to this, basically the bug was that it didn't happen since that didn't match Scratch 1.4.
https://scratch.mit.edu/discuss/topic/53/
Though, the ((1) + (0)) thing didn't happen in 1.4.
Anyway, I came up with this workaround (if you want just the workaround, pay attention to the part below the show blocks in the custom block):
https://scratch.mit.edu/projects/916274009/
It's a bit difficult LOL.
cookieclickerer33
Scratcher
1000+ posts

(Get [list] separated by [text])

That is actually kinda useful because it lets us combine lists into 1 text without going Thu each list item individually (also the workaround requires you to do this but still does some things are impossible)
cookieclickerer33
Scratcher
1000+ posts

(Get [list] separated by [text])

bump
cookieclickerer33
Scratcher
1000+ posts

(Get [list] separated by [text])

Bump: as an update I made a first class list extension with the newline idea!!!!!!!
https://scratch.mit.edu/discuss/topic/721310/
-Expo
Scratcher
1000+ posts

(Get [list] separated by [text])

Support. This would be really helpful for people working scratch with lists. I kinda wish this was already implemented
Thiago_le_meilleur
Scratcher
1000+ posts

(Get [list] separated by [text])

Support !
This should be useful for some projects.
hydrofungus
Scratcher
1000+ posts

(Get [list] separated by [text])

gamer2957201 wrote:

when [understand v] key pressed
No blocksoam nuh uh

And no unhelpful post necropost
EDawg2011
Scratcher
1000+ posts

(Get [list] separated by [text])

hydrofungus wrote:

No blocksoam nuh uh

And no unhelpful post necropost
It isn't a necropost. The topic hasn't been resolved yet.
cookieclickerer33
Scratcher
1000+ posts

(Get [list] separated by [text])

EDawg2011 wrote:

hydrofungus wrote:

No blocksoam nuh uh

And no unhelpful post necropost
It isn't a necropost. The topic hasn't been resolved yet.
it was unconstructive so its not okay

Powered by DjangoBB