We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
Whenever I cut the procedure, it erases all of the triggers that call that procedure, so I can’t really move procedures between tabs unless I can go back through and remember all the places I put a trigger. Is there another way to do this?
I feel the pain….completely hate how its working right now.
My only work around is to not use CUT
I copy it… it will then create a duplicate…Procedure2….Then I can go back and rename all the locations of the prior Procedure call….but thats horrible too…because you can easily forget one.
Unfortunately, the problem is when you paste the new procedure in, it get’s renamed with a number 2 on the end, and it isn’t linked to any of the triggers. It’s a real pain to find them all and retarget them all by hand, which is easier to do when they still exist, as opposed to when they simply disappear.
I agree with everyone in this thread, but there is another way to do this. You can move the procedure by editing the XML file directly. This can be dangerous because mistakes are easy to make, but if you have a good code editor, like VSCode, and you have a continuous backup strategy in place, it is not too dangerous.
1. Save your puzzles.
2. Edit visual_logic.xml
3. Identify your “to” and “from” tab elements
4. Identify your procedure definition. It will be in a <block> element. The type attribute will be type=”procedures_defnoreturn”. The inner text of the name field element will match your procedure name.
5. Move the whole procedure definition between <tab> elements. If using VSCode, the emmet: balance(outward) command will assist you with the selection.
6. Save the XML file.
7. Reload the puzzle editor.
Agreed! Thank you Jeremy! Though I’d like to make this a formal feature request for working with tabs, along with the ability to rename and reorder them.
.
