whoops

It's shifted downward to not overlap the menubar, since it's hard to make a child z-indexed below its parent.

It's a cleaner API IMO but ended up being a messy implementation...

These use a technique where the save/load functionality is passed from the component to its children via a function argument.  I opted for this rather than a higher order component because it is more readable and requires fewer intermediary components.

This could just as easily been done with a higher order component and would be happy to change it to that instead.

There is a performance implication since there is a function being defined in render. However the menu bar is not a highly re-rendered component, so I thought it would be ok in this case.

Sorry @carljbowman

Mostly to remove the repeated props

We have actual menu items now so the things that were menu items should be considered menu bar items

They open and close what more do you want?

Add more information to error boundary messages

The error message is included in the first line of the stack

While working on the menubar, I couldn't find the source of an error. This adds more stack info to the error messages emitted by the error boundary.

Update default project with new more compact serialization.

Add costume size/sound length details to sprite tile and update styling

Update scratch-paint to the latest version 

Fixing issue #1753

Update VM manually in package json

Remove camera upload options from sprite and backdrop selectors.