[OpenSPIM] New OpenSPIM version available

[Luke Stuyvenberg]

Hello everyone,

I've finished updating the plugin to use (nearly) the latest Micro-Manager base. The changes have been pushed to our update site; please be sure you update Fiji to get the latest code (This is a good idea in general, particularly if you encounter a possible issue.). I should point out that completely updating Fiji sometimes takes two or three goes before all changes have been acquired successfully; please make sure that the updater says "Your ImageJ is up to date!" at the end (or, if you're tinkering with the development environment, there will only be locally-modified files).


There is one known issue I've encountered: having the plugin auto-start with Micro-Manager causes stage controls to not function. (I suspect the startup sequence for Micro-Manager has changed, causing the startup script to run earlier than expected.) As a temporary workaround, please do not auto-start the plugin. I hope to have a fix for this tomorrow or early next week.


I also expect people using unexpected hardware may receive load errors saying the device adapter interface versions are mismatched. (This may also happen silently, causing unexpected program crashes.) If this is the case, please download the latest _non-nightly_ version of Micro-Manager and try the adapters from there. (For reference, the Hamamatsu device adapter we distribute now comes from the October 11 nightly build: http://valelab.ucsf.edu/~MM/nightlyBuilds/1.4/Windows/MMSetup_32bit_1.4.16_20131011.exe -- any device adapters from that release will almost certainly work with OpenSPIM.)
N.B.: The latest nightly build has once again changed version numbers, so device adapters from that build will _not_ load in OpenSPIM -- yet. :-)


Some special notes for people using our development environment:
- You will need to "git pull" to update to the latest source code.
- Your device adapters may not show any need for updating, but their use could cause trouble -- see the above note for where to find replacements, if you aren't building them from scratch.


As always, if you encounter any problems, feel free to e-mail myself and/or the list; I'll do my best to address issues as they are raised.


Thank you,
Luke Stuyvenberg