Few color picker changes to propose

[Joey Wunderlich (jwunderl)]

few changes to suggest:

ability to specify which format to start with via block attribute (in this case, hex b/c that's what simulator theming shows / takes in

a square at the front that evals out when possible, ? when not

ability to apply defaults to the shadow you're puttin in category, including e.g. wanted duplicateOnDrag for these blocks, color to match, etc.

do these sorts of changes make sense with what you had in mind for the builtinblockids behavior or nah / things to trim out richard?

[Hassan Sufi (aznhassan)]

Can we get an Arcade upload target to try out the new blocks?

[Joey Wunderlich (jwunderl)]

ah the arcade side of pr had em, here's a build with a very simple project https://arcade.makecode.com/app/590bd0d230b87b393be2ea5905452f455f73966f-ef652ebaad#pub:S43701-26279-46872-67107

[Hassan Sufi (aznhassan)]

Switching back and forth between blocks/javascript/blocks again causes the square to just display a black block:

[Hassan Sufi (aznhassan)]

If you use a variable to store the color, then switch to javascript and make any change (such as addding a comment), when you switch back to blocks and remove the variable, the background of the color picker will now be brown:

[Joey Wunderlich (jwunderl)]

fix for decomp (it was reading values that were replaced later in decompilation pass) https://arcade.makecode.com/app/d151c4577c684b9c7a93cfb1fa84c770dc21ab6a-310979b002

[Hassan Sufi (aznhassan)]

It's no longer brown, but now you get this instead:

[Joey Wunderlich (jwunderl)]

ah i see i'm dumb, i saw a different minor issue in screenshot and misread it as that -- fix 2.0 https://arcade.makecode.com/app/384d26ca1019facdcb6c58fdd8d4071150a1654a-6d485d983c (will have to make a new block for it b/c old one got swapped in too far)

[Hassan Sufi (aznhassan)]

Okay, let me know when the new block has been pulled through. Still seeing it in the recent build:

[Joey Wunderlich (jwunderl)]

Okay, let me know when the new block has been pulled through. Still seeing it in the recent build:

Ah meant new blocks as in from toolbox, the old one compiled to a function it shouldn't have basically so the project javascript itself wrong now - dragging out new one, ->Javascript, >blocks works as expected as far as i can tell

[Richard Knoll (riknoll)]

definitely get rid of the question mark, it looks like an error. in that case i would just kill the box entirely