Henry Pinkard

Got it, thanks. I'll give that a shot. Awesome library overall!!

Yeah I think I saw that way in the example, but I opted for `clear()` because I'm not always calling `plot`. Sometimes `imshow`, `scatter`, `bar`, etc. As far as I...

Yeah, I think I would just need to create something similar to [this class](https://github.com/henrypinkard/micro-manager/blob/master/mmstudio/src/main/java/org/micromanager/events/internal/CoreEventCallback.java) into pycromanager-java, and make a corresponding wrapper object on the python side. Should be easy enough....

> The other issue would be the usage of methods that got added to pymmcore-plus such as `setRelativeXYZ` and `getOrGuessChannelGroup`. Would pycromanager need to implement those? No I don't think...

> It might be that we just start with the MDA widget for now. That is, any backend that accepts an MDASequence object, executes the experiment, and emits frame-ready signals,...

That makes sense. I think this is something that would need to be implemented on your end though, since there isn't an explicit wrapping layer around the core in pycromanager...

> 1) a more flexible signaling system Just that signalling class or is there more? > While it's certainly an attractive idea to decouple from core completely (i.e. dynamic discovery...

Back to the issue at hand: I added core callbacks to the new version of pycromanager/new MM nightly build. Since pycro-manager doesn't use any events/signalling, in order to keep the...

Yes, you're right. And both are excellent points. And I would add that one can always make the case that experimenting with new approaches is valuable for its own sake....

I guess I'd pictured this as more of me making changes on my side, you making changes on your side, but if you don't have interest/bandwidth for that, let's just...