Ticket #1692 (closed enhancement: moved)
Opened 2013-03-15T11:50:20-05:00
Last modified 2013-04-03T13:53:48-05:00
Add an auto-run facility to Fiji (forward-compatible with ImageJ2)
Reported by: | dscho | Owned by: | dscho |
---|---|---|---|
Priority: | major | Milestone: | imagej2-b9-rois |
Component: | Scripting | Version: | |
Severity: | serious | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | #1516, #1776 |
Description (last modified by dscho)
As discussed on IRC ( http://fiji.sc/cgi-bin/imagejdev-irc?times=prefix&start-date=2013-03-15&end-date=2013-03-15#20130315T163800), we should have a way for users to define macros or scripts to run upon startup that is more flexible than StartupMacros.ijm.
We need to add handling for scripts/AutoRun/ (in alphatbetical order for consistency) for that.
For Fiji, StartupMacros.fiji.ijm needs to be refactored to use that facility (so that users can switch off individual features they do not like by simply uninstalling those components).
Change History
comment:1 Changed 2013-03-15T14:09:00-05:00 by dscho
comment:5 Changed 2013-03-27T09:45:35-05:00 by dscho
- Milestone changed from imagej2-unscheduled to imagej2-b7-ndim-data
comment:6 Changed 2013-04-03T13:46:35-05:00 by bdezonia
- Blocking 1776 added; 1460, 1610, 1664 removed
comment:7 Changed 2013-04-03T13:53:48-05:00 by bdezonia
- Milestone changed from imagej2-b7-ndim-data to imagej2-b9-rois
comment:8 Changed 2014-05-06T09:08:42-05:00 by curtis
- Status changed from new to closed
- Resolution set to moved
Migrated to https://github.com/imagej/imagej/issues/77
In Fiji, this was fixed in https://github.com/fiji/fiji/commit/371d3786ffcacb2c5f2ebbfb31de7526180e6338. Something similar is probably needed for ImageJ2, but we can do that more properly.