I know the classic has been forever - “No, you can’t do that.”
However… Based on my recent post on hatch rotation and scaling, I discovered that ExportWithOrigin does precisely that - it ‘moves the origin’ and then exports the geometry relative to the moved origin. It even takes into account not only translation, but rotation of the CPlane. Pretty useful for solving a few situations.
OK, I’m sure internally it simply moves the Geometry before exporting, or perhaps runs a transformation on all the numerical data that actually create geometry. Whatever. If that can be done for Export, why can it not be done internally?
The large advantage of a command like that over simply moving/rotating all your geometry with Rhino commands is that it could act on the whole file, no matter if objects are hidden, locked, on off layers, etc. Like changing the units of a file now does.
I assume there are probably a lot of worms in that particular can. But it could be quite useful and I know I’m not the first person who has requested it… So I’ll just toss it out here. For V8.