{"id":28426,"date":"2020-03-20T19:57:10","date_gmt":"2020-03-20T23:57:10","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=28426"},"modified":"2020-03-20T19:57:10","modified_gmt":"2020-03-20T23:57:10","slug":"what-does-the-move-to-command-do-in-iwork","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/03\/20\/what-does-the-move-to-command-do-in-iwork\/","title":{"rendered":"What Does the “Move To” Command Do in iWork?"},"content":{"rendered":"

Howard Oakley<\/a>:<\/p>\n

\n

First, it surprises you by not adopting the standard human interface. Instead of the normal Save File dialog, as used by countless apps for a great many years, it drops down a small sheet offering in a popup menu to move the document to where it already is. In the spirit of novelty, as if intended to exemplify bad interface design, that popup lists a strange assortment of locations, of which only a few seem remotely appropriate. If you want a properly-designed purposeful dialog, you have to click on Other… right at the bottom to see a familiar Save File dialog.<\/p>\n

[…]<\/p>\n

What arrives at the destination is disappointingly exactly what you’d get from a regular Finder move: all saved versions are stripped from it. So unless you like this idiosyncratic interface, there seems no advantage in using it over a standard Finder move, and if you want a copy instead, then you’ll want to use the Finder anyway, once again accepting that you’ll lose access to all versions in the process.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n