I understand that the warp speed block was removed and replaced by the “run without screen refresh” option in custom blocks, but custom blocks do not belong in certain places. It doesn't make sense to make a block to only perform an action once without refresh. The warp speed block works better in this case. I think both options should be available, mainly so I do not clutter up the custom blocks palette with blocks I only use once.

New users seeing a block used in someone's project that they can't find in their palette would be even more confusing than the warp speed block itself.

I was disappointed when I saw that the warp speed block wasn't in my palette.

Same.

i agree. the “run without screen refresh” is so hidden that even experienced users who would like to use that function can't find it. “warp speed” also makes a whole lot more sense as to its function.

I agree. When I saw the “run without screen refresh” I had no idea what it ment. “Warp” makes a lot more sense

How about “force turbo speed” or something with the word “turbo”, to match with the shift-click-green-flag option? Though technically I think there's a small difference, the result (for the most part) is the same.

Much more intuitive for beginners. Support.

I dunno guys, unless you watch “Star Trek”, or are into Sci Fi, “warp” is not a term that you are likely to understand.

Screen refresh is not the easiest concept to grasp either, but it is at least more accurate / descriptive.

I'm not talking about the block label, I want the actually C shaped warp speed block back. I don't really care what it is labeled, I just find it a much better way of running without screen refresh in some cases.

Lightnin
I dunno guys, unless you watch “Star Trek”, or are into Sci Fi, “warp” is not a term that you are likely to understand.

Right, I'd prefer Infinite Improbability.

MathWizz
I'm not talking about the block label, I want the actually C shaped warp speed block back. I don't really care what it is labeled, I just find it a much better way of running without screen refresh in some cases.

Exactly. Not only does the current workaround make it harder than necessary to make blocks execute without screen refresh, but it also gives terrible programming habits to Scratchers (creating a function for very few blocks and a singe use).

LS97
it also gives terrible programming habits to Scratchers (creating a function for very few blocks and a singe use).

1) I can think of very few cases in which I've wanted “very few blocks” to be run atomically.
2) Creating a function you only use once is not necessarily bad: if it serves a different purpose, put it in a different function.

nXIII

LS97
it also gives terrible programming habits to Scratchers (creating a function for very few blocks and a singe use).

1) I can think of very few cases in which I've wanted “very few blocks” to be run atomically.
2) Creating a function you only use once is not necessarily bad: if it serves a different purpose, put it in a different function.

1) Loops containing 2 or 3 blocks. Loads.
2) But usually it won't be the case, especially for painting lines on the screen.

If you have that many tiny loops, shouldn't abstract it to a block anyway? There's almost certainly common code in there.

Painting lines is a different function than, e.g., painting circles or doing computations on those lines. Is that what you're talking about?

nXIII
If you have that many tiny loops, shouldn't abstract it to a block anyway? There's almost certainly common code in there.

Not necessarily. In the demo for my vector graphics project, I had to write an atomic procedure to update the scene, which should be just done in my demo script. It adds clutter.

nXIII
Painting lines is a different function than, e.g., painting circles or doing computations on those lines. Is that what you're talking about?

Yeah, I meant that.

I think we need a c-block that runs sections of code within a single frame, like a custom block with “no screen refresh” enabled. It would allow for blocks such as “repeat ()” and “repeat until <>” to be used more freely within 1sprite1script projects, where you generally are uinable to use them because of the delay caused by their repetitions.

The block would be very similar to the old all at once block.

The block could like like this:

run without screen refresh {} :: control

see more block design ideas

As I've said, blocks like “forever” and “repeat until <>” cannot be used within 1sprite1script projects because they have been programmed with a delay between iterations. Whilst this is helpful for newer, inexperienced Scratchers I think more advanced Scratchers should have the ability to cut out this delay, which is fatal to some projects.

Please let me know if you support.

define doSomeAction //run without screen refresh
...

Although it would be convenient to not always have to make a custom block for it…