Q. Was consideration given to also including a Reload option in the migration dialog?
If a user manually exports a .chex file and gives it a custom name, and then declines the offer on exit to export to a .chex file (because they know they already have one), the migration dialog does not provide a straight-forward path to reloading the user-initiated custom-named .chex file. Granted, they can choose the Delete Data option in the migration dialog, and then proceed to go to menu File>Reload (which will anyway delete the existing data (OOTB in this case). Minimally, this might be something to add to the instructions or something. Optimal, to me, would be to stick a "Reload" button on the migration dialog that would do the same thing as File>Reload, but I defer to those who have thought through this workflow as to whether this additional button would add confusion for the typical new user. Thanks, Andre On Wed, 07 Nov 2007 14:26:17 -0800, "Heikki Toivonen" <[EMAIL PROTECTED]> said: > Now on shutdown Chandler will ask if the user would like to create > backup.chex. On startup, Chandler will first try to open the repository, > but in case of version errors will try to fall back to reloading from > backup.chex. In all migration cases the user will be presented with a > dialog which also has the old manual migration option. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
