It's a very good concept, but I find one problem [which is easily fixed]. If you use Architectural or Engineering or Fractional Units, at the very least you MUST change (rtos opt) to (rtos opt 2) to force it to use decimal units. If you don't, offset distance values that involve fractions or feet will be truncated to integer values. This gets worse with values of 12 or more under Architectural or Engineering units, where if you give a distance of (for example) 19, whether picked by two points on-screen or typed in as 19 or 19" or 1'-7", (rtos) will make it 1'-7" and (read) will turn that into just 1, so the resulting value will be 1". Likewise, any value of at least 24 but less than 36 will become 2, etc. A lesser shortcoming: it would be better if, like the regular Offset command, it didn't quit if you miss in picking something.