The rubber band idea would work. However being able to input a fix by VOR/RAD/DIST would be nice.
"But I wonder why you're using VORs instead of GPS."
Here's my thoughts...maybe some controllers or more experience pilots will correct me.
1. GPS can have outages, rare, but it can happen.
2. GPS equipment in the a/c can go out.
3. Practicing conventional navigation because of #1 & 2.
4. If IFR and your a/c doesn't have an IFR legal GPS. Your gps driven IFly can't legally be used for primary nav, only situational awareness.
Mostly it would be something you plan in advance for some reason. While ATC is not likley to give you a fix to go to in this manner, they can...for example...hold W of XXX VOR on the 270 radial at 10 DME. Maybe you want to practice flying an arc and you want XXX/270/10 to be your starting point. For me, the issue is simply readability. If you've got Lat/Long points in your IFly flight plan, how many people can look at that lat/long and visualize where that is? It's fairly easy to do if you simply reference it off a VOR/Rad/Dist. It is a valid way to file a waypoint in an FAA flight plan. Here is an excerpt from the "help" description from 1-800-Wxbrief on ways to input a route in a flight plan.
8-11 alphanumeric fix-radial-distance in the format (A)(A)(A)AAaaabbb, where parentheses denote optional characters
- (A)(A)(A)AA is 2-5 alphanumeric airport/heliport/NAVAID/waypoint identifier
- aaa is radial measure in degrees from North in the range 001-360
- bbb is distance in nautical miles in the range 001-999
My $.02