Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
stacker:support:knownissues [2018/09/09 18:31] rjlittlefield [Settings are retained across uninstall / reinstall] |
stacker:support:knownissues [2020/03/04 23:32] rjlittlefield |
||
|---|---|---|---|
| Line 22: | Line 22: | ||
| * [[#windows_manually_edited_program_files_persist_across_re-installation|Windows, manually edited program files persist across re-installation]] | * [[#windows_manually_edited_program_files_persist_across_re-installation|Windows, manually edited program files persist across re-installation]] | ||
| * [[#macintosh_os_x_could_not_establish_communications_with_stackshot_controller|Macintosh OS X, "Could not establish communications with StackShot controller"]] | * [[#macintosh_os_x_could_not_establish_communications_with_stackshot_controller|Macintosh OS X, "Could not establish communications with StackShot controller"]] | ||
| + | * [[#macintosh_os_x_zerene_stacker_will_work_on_only_one_stack_at_a_time|Macintosh OS X, Zerene Stacker will work on only one stack at a time]] | ||
| * [[#macintosh_os_x_mountain_lion_reports_installation_bundle_is_damaged_move_to_trash|Macintosh OS X (Mountain Lion) reports installation bundle is "damaged, move to trash"]] | * [[#macintosh_os_x_mountain_lion_reports_installation_bundle_is_damaged_move_to_trash|Macintosh OS X (Mountain Lion) reports installation bundle is "damaged, move to trash"]] | ||
| * [[#macintosh_os_x_how_to_recover_from_excessive_memory_allocation|Macintosh OS X, how to recover from excessive memory allocation.]] | * [[#macintosh_os_x_how_to_recover_from_excessive_memory_allocation|Macintosh OS X, how to recover from excessive memory allocation.]] | ||
| Line 237: | Line 238: | ||
| Interestingly, in most cases just going through the above steps to collect the required information also makes the problem disappear. That probably has to do with the reboot and order of operations. | Interestingly, in most cases just going through the above steps to collect the required information also makes the problem disappear. That probably has to do with the reboot and order of operations. | ||
| + | |||
| + | ===== Macintosh OS X, Zerene Stacker will work on only one stack at a time ===== | ||
| + | |||
| + | Solution: open a Terminal window and launch additional copies of Zerene Stacker using the command | ||
| + | <code> | ||
| + | open -n /Applications/ZereneStacker.app | ||
| + | </code> | ||
| + | |||
| + | If you put the ZereneStacker icon (the ZereneStacker.app application bundle) someplace besides in /Applications, then just edit the command line accordingly. | ||
| + | |||
| + | The explanation here is that by design, Zerene Stacker is programmed using the "single document" model. This means that each instance of Zerene Stacker can only work with one stack at a time. The normal process of launching Zerene Stacker by clicking its icon will not launch a second instance. Instead, clicking the icon just makes the current instance foreground, apparently in the expectation that all programs are multi-document. Unfortunately there seems to be no way to just tell MacOS that Zerene Stacker is single document and it should launch another instance when the launch icon is clicked. The "-n" argument on the open command says to create a new instance regardless of whether there's already one running. | ||
| + | |||
| ===== Macintosh OS X (Mountain Lion) reports installation bundle is "damaged, move to trash" ===== | ===== Macintosh OS X (Mountain Lion) reports installation bundle is "damaged, move to trash" ===== | ||