From d417f31556c6ef2b0d5467471bf9393a8a2c6823 Mon Sep 17 00:00:00 2001 From: Westside Robotics Date: Thu, 26 May 2022 12:47:36 -0700 Subject: [PATCH] Update description of minor/internal edits to a myBlock. --- Custom-FTC-Blocks-(myBlocks).md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Custom-FTC-Blocks-(myBlocks).md b/Custom-FTC-Blocks-(myBlocks).md index 1e9afe5..831670e 100644 --- a/Custom-FTC-Blocks-(myBlocks).md +++ b/Custom-FTC-Blocks-(myBlocks).md @@ -203,7 +203,7 @@ If your Java change does affect external features, its updated myBlock is

[[/images/Custom-FTC-Blocks-(myBlocks)/a0260-editing-error-Blocks.png|editing error message]]

-If your edit affects only the myBlock's internal processing, it **will update** automatically after "Build Everything". In that case, it doesn't need to be replaced with a fresh version from the Java Classes menu. In fact, you don't even need to click Save OpMode in the Blocks screen. You can **simply re-run the OpMode** on the Driver Station, without re-selecting it from the list of OpModes. Just click INIT and Start; the edited myBlock will run. Really! This allows very fast testing of minor/internal changes to the myBlock. +If your edit affects only the myBlock's **internal** processing, it might update automatically after "Build Everything", without needing a fresh replacement from the Java Classes menu. In some cases you might not even need to click Save OpMode in the Blocks screen -- you could simply re-run the OpMode on the Driver Station with INIT and Start. This can allow very fast testing of minor/internal changes to the myBlock. In any case, consider adding **versions** to your myBlock names, such as myGreeting_v01. Copy and paste before editing, to keep all related myBlock methods in the **same Java class**. In Blocks, all uniquely named versions will be available in the Java Classes menu, under that single class name.