HTML-Fan wrote:

It would make no sense that

define my block :: cap
broadcast [stop v]
when I receive [stop v]
stop [all v]

is a hat block since the broadcast block practically starts a multitasking thingy.

I don't know what that means, sorry.

lapisi wrote:

hedgehog_blue wrote:

lapisi wrote:

Mine doesn't do that… I have no idea why it would be different between us. I might report a bug so we can find out what way this is supposed to work. Can you state your exact browser/operating system for the bug report?

I can't get it to act the way it does for you; I tried all of the following devices and it only stopped the custom block on all of them:
My browser / operating system: MacOS Macintosh X 10.11.6, Chrome 83.0.4103.116
My browser / operating system: ChromeOS 13020.87.0, Chrome 83.0.4103.119
My browser / operating system: IPadOS 12.1.4, Safari 12.0

My browser / operating system: Windows NT 10.0, Chrome 84.0.4147.89, No Flash version detected

EDIT: I tried it again and it only stopped the custom block, idk how this is happening

EDIT: This is weird, I tried it again and it stopped the whole script…

Okay, so it seems like your behavior is very inconsistent, so I'm very close to assuming it's supposed to only stop the custom block because everybody else always sees it that way. You can report the bug, because it seems like an issue exclusive to you for now.

And if that's correct it means that this suggestion won't be possible due to being able to stop a custom block with stop [this script v] before it runs a stop [all v] block at the end, making it not be a hat block, despite ending with one.

bump

lapisi wrote:

bump

Bumping won't help; we're never going to find out if this suggestion is possible if we don't find out the correct behavior for the stop this script thing.

No support. If you want custom cap blocks then that should be an option, but custom blocks should never automatically become cap blocks. That would be confusing.

hedgehog_blue wrote:

lapisi wrote:

bump

Bumping won't help; we're never going to find out if this suggestion is possible if we don't find out the correct behavior for the stop this script thing.

ok I tested it again and it finally settled on stopping just the custom block, idk what happened the other times

hedgehog_blue wrote:

--Explosion-- wrote:

Oh, I think I understand… Support! This would be much more intuitive! Perhaps only do this is the cap blocks were actually at the end of the custom block with no if statements around them though, right?

This won't work, because of a case like this:

define . . .
if <[1] = [1]> then
stop [this script v] //stops the custom block before it gets to stop all
end
stop [all v]

This custom block is not a cap block, despite ending with a cap block.

actually it would detect the cap block at the end and still make it a cap block because it wouldn't need to detect if the ending cap block is used because if it isn't then that would mean the script already stopped

lapisi wrote:

hedgehog_blue wrote:

lapisi wrote:

Mine doesn't do that… I have no idea why it would be different between us. I might report a bug so we can find out what way this is supposed to work. Can you state your exact browser/operating system for the bug report?

I can't get it to act the way it does for you; I tried all of the following devices and it only stopped the custom block on all of them:
My browser / operating system: MacOS Macintosh X 10.11.6, Chrome 83.0.4103.116
My browser / operating system: ChromeOS 13020.87.0, Chrome 83.0.4103.119
My browser / operating system: IPadOS 12.1.4, Safari 12.0

My browser / operating system: Windows NT 10.0, Chrome 84.0.4147.89, No Flash version detected

EDIT: I tried it again and it only stopped the custom block, idk how this is happening

EDIT: This is weird, I tried it again and it stopped the whole script…

Trying it too, just to see what's happening:
It's always stopping the custom block.
My browser / operating system: Windows NT 10.0, Firefox 79.0, No Flash version detected

Also, no support for reasons already stated in recent posts.

mybearworld wrote:

~snip~
Trying it too, just to see what's happening:
It's always stopping the custom block.
My browser / operating system: Windows NT 10.0, Firefox 79.0, No Flash version detected

Also, no support for reasons already stated in recent posts.

read this:

lapisi wrote:

hedgehog_blue wrote:

lapisi wrote:

bump

Bumping won't help; we're never going to find out if this suggestion is possible if we don't find out the correct behavior for the stop this script thing.

ok I tested it again and it finally settled on stopping just the custom block, idk what happened the other times

also other than that it is a good reason to not support so I won't argue with that

EDIT: any posts beyond this point are from after the update

lapisi wrote:

hedgehog_blue wrote:

~snip~
Trying it too, just to see what's happening:
It's always stopping the custom block.
My browser / operating system: Windows NT 10.0, Firefox 79.0, No Flash version detected

Also, no support for reasons already stated in recent posts.

Sorry for going slightly off topic, but why does it say that I wrote that? That was somebody else's post.


Anyways, it sounds like the new solution is just to have the user specify that a block is a cap block. I don't see any problems with it other than it isn't too important of a feature, so it would be nice if it were added at some point. And it's good that the bug fixed for you, I was worried my projects would be broken.

hedgehog_blue wrote:

lapisi wrote:

hedgehog_blue wrote:

~snip~
Trying it too, just to see what's happening:
It's always stopping the custom block.
My browser / operating system: Windows NT 10.0, Firefox 79.0, No Flash version detected

Also, no support for reasons already stated in recent posts.

Sorry for going slightly off topic, but why does it say that I wrote that? That was somebody else's post.


Anyways, it sounds like the new solution is just to have the user specify that a block is a cap block. I don't see any problems with it other than it isn't too important of a feature, so it would be nice if it were added at some point. And it's good that the bug fixed for you, I was worried my projects would be broken.

oh oops I was snipping a lot of quotes and wasn't really paying attention to what I was snipping, sorry about that.

EDIT: ok I fixed it now

Bring
Up
This
Topic

sorry, this isn't my suggestion anymore, this doesn't solve the original issue, feel free to continue discussing, but I won't be posting here anymore