[OpenSPIM] asynchronous writing of stacks bug?

[LUKE ADAM STUYVENBERG]

Hi Alexis,

On Mon, 26 Aug 2013 08:44:26 0200 Alexis Maizel wrote
> The next OpenSPIM update will use a different code base than the current one
> (1.4.x dev)? So unless I commit my update to the MM repository and get them
> part of the nightly build, it won't work, right?
Actually, what I meant was that from now on, the OpenSPIM plugin will try to
interact with the Cobolt device as though it were unchanged -- it will not
treat it as a shutter, and when altering laser power, it will attempt to set
the "Power" property, not "PowerSetpoint" (and so, having the property be named
"PowerSetpoint" even though the laser is a Cobolt will greatly confuse the
plugin). Essentially, the changes I'm making mean that the plugin will interact
with each device adapter differently.

By all means, though, commit your changes -- adapting the plugin to changes in
device adapters is very little work (which is the part of the point of this
update), so if your changes become 'canonical', I can easily change the
SPIMAcquisition plugin to support them.

I'm not planning to update the MM code base just yet -- as far as I am aware,
the nightly build's device adapters still work with the OpenSPIM version.

Thanks,
Luke

On Mon, 26 Aug 2013 08:44:26 0200 Alexis Maizel wrote

> Hi Luke,
> 
> > I should warn you in advance, though I'll try to make it clear when I
> > announce
> > the update: the next update *will* obsolete the changes you made to the
> > Cobalt
> > adapter. The reason is because it will be designed to work with the Cobalt
> > adapter in MM's nightly build -- I'm afraid you will need to revert your
> > changes.
> 
> I am not sure, I am following you here
> The next OpenSPIM update will use a different code base than the current one
> (1.4.x dev)? So unless I commit my update to the MM repository and get them
> part of the nightly build, it won't work, right?
> My amendments to the Cobolt code are now tested and stable, so I feel
> confident to have them added to the repository. I'll talk to Karl Llave.
> 
> With my best regards,
> 
> Alexis