Closed AmbientOSX closed 9 years ago
I'm not sure what all of these changes are doing, aside from the position sensor drop-down (which we do want).
I don't think we want to close the blockly window when the program starts. There is a green task to close the palette, but at this point I wouldn't even do that - if it turns out to be the wrong thing, it's getting to be too late to change it back.
I'm good with dropping the m4 change from "_" to " ".
I didn't understand which the other issues that you wanted to drop are. FWIW, I enabled the drop-down in the variable blocks, which means that those have some of the other procedure functionality that I'd prefer to conceal... I think the drop-down is more important than concealing the functionality in that case.
Please make sure you're working blue/black tasks first. If you have tasks on your list that aren't on the punchlist, let me know and I'll figure out where to add them...
@kadst43 @BrettASwift
Getting these changes in to address the showstopper and a few quick other things. M3T2 resets XML appropriately for me but need verification. Blockly window closes on execute...
Things I have investigated but I'm inclined to say "won't fix" to: setting the underscores to spaces in triangle transformation blocks resurfaces the undefined bug. Tooltips and input block validation for procedures was done BUT required reenabling the "special" procedures and variables fields in the Blockly toolbox. The "correct" procedure_callnoreturn block would also not reliably load. This has to do a complex Core Blockly process for activating procedures.