Discuss Scratch

pvz_pro
Scratcher
500+ posts

([ v] of [parent v])

bump on track
TheNonNameMouse
Scratcher
88 posts

([ v] of [parent v])

I don't know…what would be the importance of this block?
pvz_pro
Scratcher
500+ posts

([ v] of [parent v])

TheNonNameMouse wrote:

I don't know…what would be the importance of this block?
it's a new option for
([x position v] of [sprite v])
and the reasons i'm suggesting this are

1. workaround is a bit bad

2. this can be helpful for tower defense games



pvz_pro
Scratcher
500+ posts

([ v] of [parent v])

bumpgeist
pvz_pro
Scratcher
500+ posts

([ v] of [parent v])

bump out
pvz_pro
Scratcher
500+ posts

([ v] of [parent v])

bump after bump
pvz_pro
Scratcher
500+ posts

([ v] of [parent v])

can't let bump
pvz_pro
Scratcher
500+ posts

([ v] of [parent v])

bump, bump, bump, repeat
braxbroscratcher
Scratcher
1000+ posts

([ v] of [parent v])

Zekrom01 wrote:

pvz_pro wrote:

Sheep_maker wrote:

Zekrom01 wrote:

What are the options for the first dropdown?
I can't make a stance or opinion until you reply what they are
I'm pretty sure “parent” is just a new option of the second dropdown of this block:
([x position v] of [Sprite1 v])
right you are
You can use variables, but support for convenience reasons
Support as above.

Last edited by braxbroscratcher (April 20, 2016 00:04:10)

A-no-meep
Scratcher
100+ posts

([ v] of [parent v])

What happens if a non-clone runs this block?
theonlygusti
Scratcher
1000+ posts

([ v] of [parent v])

I support, this is a pretty cool idea and could be used creatively (although, I'll admit it it, I see no real reasons for it right now; maybe suggest some?)
pvz_pro
Scratcher
500+ posts

([ v] of [parent v])

A-no-meep wrote:

What happens if a non-clone runs this block?
not for the stage an it will return a trait of itself
ChildCritic
Scratcher
500+ posts

([ v] of [parent v])

Workaround.
No support.
EDIT: Reverse process here. I didn't think that through. I'll get something that works like that online soon.
EDIT 2: Reversed process. (actual workaround)

Last edited by ChildCritic (April 24, 2016 23:45:40)

ChildCritic
Scratcher
500+ posts

([ v] of [parent v])

Okay. Let's do this thoroughly.
This works if a clone's parent is a clone.
Just add before the cloning:
set [saveparent v] to (parent)//local
set [parent v] to (Clone number)//also local
create clone of [myself v]
set [parent v] to (saveparent)
This works if the parent is not a clone

THE COMMENT CHAIN ON THE SECON(EDIT:)D WORKAROUND PROJECT

pvz_pro wrote:

don't be hasty to pull the workaround card on block ideas, remember, the OP is most likely not aware of the workaround

pvz_pro wrote:

ChildCritic wrote:

pvz_pro wrote:

what about clones? start reading everybody's posts
pvz_pro Please post that on the topic as a reply so I know more about what you're talking about.
I did, link: https://scratch.mit.edu/discuss/topic/191814/?page=1

childcritic wrote:

pvz_pro wrote:

what about clones? start reading everybody's posts
Look at the other link.

Last edited by ChildCritic (April 25, 2016 00:54:20)

pvz_pro
Scratcher
500+ posts

([ v] of [parent v])

ChildCritic wrote:

Okay. Let's do this thoroughly.
This works if a clone's parent is a clone.
Just add before the cloning:
set [saveparent v] to (parent)//local
set [parent v] to (Clone number)//also local
create clone of [myself v]
set [parent v] to (saveparent)
This works if the parent is not a clone

*snip*
what do you mean by “local”
ChildCritic
Scratcher
500+ posts

([ v] of [parent v])

pvz_pro wrote:

ChildCritic wrote:

Okay. Let's do this thoroughly.
This works if a clone's parent is a clone.
Just add before the cloning:
set [saveparent v] to (parent)//local
set [parent v] to (Clone number)//also local
create clone of [myself v]
set [parent v] to (saveparent)
This works if the parent is not a clone

*snip*
what do you mean by “local”
The variable is a local variable.
theonlygusti
Scratcher
1000+ posts

([ v] of [parent v])

ChildCritic wrote:

Okay. Let's do this thoroughly.
This works if a clone's parent is a clone.
Just add before the cloning:
set [saveparent v] to (parent)//local
set [parent v] to (Clone number)//also local
create clone of [myself v]
set [parent v] to (saveparent)
This works if the parent is not a clone


Oh, there is an intuitive and obvious workaround! Change to No Support. </sarcasm>

Just because a block idea would have a workaround doesn't mean it shouldn't be implemented, when you don't support a suggestion, think through each of these: would it improve the Scratching experience? Would it make life easier for Scratchers? Would it make Scratch more accessible?

(HINT: the answer is yes to all of the above in this case)

Also:

ChildCritic wrote:

Let's remove the move block as it has a workaround:

move (10) steps // we don't need this anymore


go to x: ((x position) + (([sin v] of (direction)) * (number))) y: ((y position) + (([cos v] of (direction)) * (number)) // much better
theonlygusti
Scratcher
1000+ posts

([ v] of [parent v])

ChildCritic wrote:

Okay. Let's do this thoroughly.
This works if a clone's parent is a clone.
Just add before the cloning:
set [saveparent v] to (parent)//local
set [parent v] to (Clone number)//also local
create clone of [myself v]
set [parent v] to (saveparent)
This works if the parent is not a clone
Also, your workaround doesn't work:

pvz_pro wrote:

It would report a trait of a clone's creator, even if it was created by a clone.

I also wanted to point out 1 thing:

pvz_pro wrote:

Supporters:
  1. pvz_pro
  2. alexphan
  3. Mrcomputer1
  4. TheMonsterOfTheDeep
  5. Gamemaker232
  6. zekrom01
  7. braxbroscratcher
  8. theonlygusti
Non-Supporters:
  1. ChildCritic

ChildCritic, you have been put on the spot. Now you must provide valid reasons for not supporting (valid does not include a broken workaround.)

Last edited by theonlygusti (April 25, 2016 07:31:12)

ChildCritic
Scratcher
500+ posts

([ v] of [parent v])

@theonlygusti:
How about you reread my ENTIRE post.
It provides you with exactly what you need.
scratchisthebest
Scratcher
1000+ posts

([ v] of [parent v])

Don't really see why not, the x of y block already has a ton of technically not “needed” features. This would be a great quality of life improvement.

Don't see any reason that it would return the Stage if it's ran by a non-clone though. (What's the x position of the Stage?) I think it should just return it's own data, i.e. ([direction] of [parent]) is the same as (direction) if ran by a non-clone

Powered by DjangoBB