BTW, your bump reminded me that I meant to mention that, yes, I do see this happen too…

For example, it happens with the “Play” and “Options” clickable items in InterXeptor 3D. It only started happing after the recent update that made the transparent parts of a costume no longer recognised as part of the costume (so they no longer register as being ‘touched’ by mouse-pointer, for example).

To see what I mean, start up InterXeptor, and click on the “Options” item. What should happen now is that the “Done” item comes onto the screen, while the other two items (“Options” and “Play”) disappear off to the left completely. However, they don't quite make it all the way off - they get stuck at the left edge (as you would expect for a sprite that ‘ended’ at their rightmost letter - but they don't end there, since they have an extra transparent border which used to ensure they went all the way off-screen…)



It is possible to create sprites that still have a transparent border to allow going off-screen, but you have to import them from an external graphics package with the transparent part included, so that Scratch will consider it to have dimensions that include the transparent border.

I also see it happen with the flare effect sprites in my 3d demo projects - e.g. this one. (It's not that noticeable, but if you look carefully you'll see they get ‘stuck’ at the edges of the screen. -Fortunately, the large background sprites have enough extra transparency around the originally imported images that they pretty much survive.)

Bump!

Bump!

Support, I want this so much.

Bump!

BUMP
BUMP
BUMP
BUMP

Or maybe pen movement could be uncoupled from sprite movement at the stage's edge. Then we could at least draw cool stuff that goes beyond 360 x 480 without lots of glitches.

BUMP

BUMP

Failord wrote:

···
And finally, a “recover sprite” option in the sprite info area, next to all the checkboxes. This would execute these scripts:

go to x: (0) y: (0)
show
go to front
set size to (100) %
stop [all v]

···

Like that, but how about instead have it say “reset sprite” (as that seems to be more in line with the blocks). Additionally, I would make it slightly different:

go to x: (0) y: (0)
point in direction (90 v)
show
go to front
clear graphic effects //not just set size
stop [other scripts in this sprite v] :: stack // I believe “stop all” would stop ALL sprites’ scripts, not just the aforementioned sprite

Anyway, I like the concept! This would help scratchers of all experience levels a lot (+1)!

Cyoce wrote:

Failord wrote:

···
And finally, a “recover sprite” option in the sprite info area, next to all the checkboxes. This would execute these scripts:

go to x: (0) y: (0)
show
go to front
set size to (100) %
stop [all v]

···

Like that, but how about instead have it say “reset sprite” (as that seems to be more in line with the blocks). Additionally, I would make it slightly different:

go to x: (0) y: (0)
point in direction (90 v)
show
go to front
clear graphic effects //not just set size
stop [other scripts in this sprite v] :: stack // I believe “stop all” would stop ALL sprites’ scripts, not just the aforementioned sprite

Anyway, I like the concept! This would help scratchers of all experience levels a lot (+1)!

I forgot about clearing graphic effects, so I'll add that. The size block stays because it's not counted as a graphic effect. I think it should still be “stop all” and not “all scripts this sprite” because that stops other sprites from covering it and broadcasts that might make it disappear.

BUMP

support

We're talking about this and are going to investigate what's going on. Thanks for the information and discussion! We'll update this thread later.

grokblah wrote:

We're talking about this and are going to investigate what's going on. Thanks for the information and discussion! We'll update this thread later.

Yay!

grokblah wrote:

We're talking about this and are going to investigate what's going on. Thanks for the information and discussion! We'll update this thread later.

YES!!!

grokblah wrote:

We're talking about this and are going to investigate what's going on. Thanks for the information and discussion! We'll update this thread later.

I'm not sure there's so much to investigate, really… it's simply a ‘fix’ that was made to ensure transparent regions are not included in the ‘hit’ testing of vector costumes.

I haven't checked to be sure, but this would be my guess:
https://github.com/LLK/scratch-flash/commit/85574ae7c72856743c5d321e5ec36654aeb7a563

It's arguable that having a transparent rect included in the hit region of a costume isn't really quite expected behaviour. However, many of us made use of that as a way to get sprites to disappear off-screen. Now the behaviour has changed, it's broken projects which use that ‘trick’ (some more than others).

I guess the question is whether you prefer to ‘break’ a number of previous projects (mainly in a way that makes them visually less appealing), or would rather revert to a somewhat unexpected, if slightly useful, behaviour…

TheLogFather wrote:

I guess the question is whether you prefer to ‘break’ a number of previous projects (mainly in a way that makes them visually less appealing), or would rather revert to a somewhat unexpected, if slightly useful, behaviour…

To make something perfectly clear… a project I was working on (that glitched and died so I can't even display its tortured husk) was entirely slaughtered by this. The cutscene couldn't progress until the sprites were out of the screen, so the project would just stop there.

Support!

Failord wrote:

TheLogFather wrote:

I guess the question is whether you prefer to ‘break’ a number of previous projects (mainly in a way that makes them visually less appealing), or would rather revert to a somewhat unexpected, if slightly useful, behaviour…

To make something perfectly clear… a project I was working on (that glitched and died so I can't even display its tortured husk) was entirely slaughtered by this. The cutscene couldn't progress until the sprites were out of the screen, so the project would just stop there.

Yeah, if it's so bad as to make a whole project completely useless, then I think they urgently need to fix this.