Problem
If you decide to move or copy a method to a different class or module, you have to copy and paste the name, arguments list, return value, generic spec, comments, AND code individually and separately.
In any other environment, you would just copy the whole method onto the clipboard and then paste it into a different file inside whatever containing class you want it in.
Proposed Solution
Since I can imagine almost more "I'm not even going to consider it" opposition to this form-defined GUI for coding than for BASIC itself, this seems like a major downside you could compensate for with some kind of "copy / move method" feature, and I'd suggest hooking it into the Edit menu where someone unfamiliar with the product might hopefully seek it out, or even reflexively go there due to muscle memory.
Example Workflow
With the method active, select Cut Method or Copy Method from the Edit Menu. Go to the destination class or module, and select Paste Method.
Alternatives Considered
It may be safer not to have a Cut Method function -- have them copy and paste method and then go back and delete the source method. But I'd suggest leaving that up to the user, if they're paranoid they can just not use Cut Method. Maybe warn and get confirmation on Cut or Copy Method if an un-pasted method is already on the "clipboard".
Who Would This Help?
Everyone
You would have to think about edge cases. For example don't allow pasting an extension method into anything but another module, don't allow a method marked Override to be pasted anywhere but another class. If the source can't pretty much go to the destination as-is, maybe the user should have to hand-move it. OTOH it's a judgment call -- maybe you put up a dialog showing what needs attention after the paste, and maybe you have this feature participate in Undo, IDK. It just feels like this would be a big aid to someone who tends to work "in the flow", tries out ideas and refines things as they go. It would make the UI feel less straight-jackety.