Thoughts on client/matlab window

Support
1

Chris,

I’ve done a little thinking about my preferred interface for the
matlab plugin and client.

First, it would be nice if there was a ‘reload experiment’ client
button that would cause everything to be reset (incl matlab state) but
all the client windows - python, matlab, variables, etc. would stay in
the same position and state. (right now we have a labjack plugin bug
that prevents unloading; we should and will fix that).
Reason: we want matlab state (and things like the success/failure
MWorks variables) to be reset between animals, and just loading a
different var set doesn’t do that.

It would be great if the matlab window could somehow have an option to
save state across experiment reload. Haven’t thought about this
deeply but it would be nice to be able to fix bugs in the XML without
blowing away the record of the current session - which is maintained
in matlab for me.

The Matlab window, if it’s going to retain an Events list, should have
a separate one for each experiment. I’m hoping it can just ship every
event over and efficiency/time reasons won’t prevent that. And it
should also change the matlab script name based on the experiment
name.

It would be great if there was a hotkey for saving the variable set.
And a recent variables menu for loading (in the top menu bar).
I really would like a way to turn the window animation off - today
when I was debugging I probably restarted the client 50 times and
clicking through definitely makes me annoyed at MWorks (the tech who
has been running animals shares this view). We want users to feel
happy with MWorks… :slight_smile:

Also it would be nice if the Python bridge window scrolled to the
bottom on output.

Maybe you should stop by here sometime to see how we use this; it
might make our use cases clearer.

thanks!!!
Mark

2

Hi Mark,

First, it would be nice if there was a ‘reload experiment’ client button that would cause everything to be reset (incl matlab state) but all the client windows - python, matlab, variables, etc. would stay in the same position and state.

Am I correct to assume that task definition file support obviates your need for this, or do you see it addressing use cases that TDFs do not?

It would be great if the matlab window could somehow have an option to save state across experiment reload.

Makes sense – I’ve opened a ticket.

The Matlab window, if it’s going to retain an Events list, should have a separate one for each experiment. I’m hoping it can just ship every event over and efficiency/time reasons won’t prevent that. And it should also change the matlab script name based on the experiment name.

Again, I assume TDFs meet your needs here.

It would be great if there was a hotkey for saving the variable set.

OK, I’ll tack this on to the “make client more keyboard friendly” to-do item.

And a recent variables menu for loading (in the top menu bar)

Again, I’m guessing TDFs cover your use case (but correct me if I’m wrong).

I really would like a way to turn the window animation off

Do you mean the variable set selection panel (meaning this is part of the previous request)?

Thanks,
Chris

3

Hi Chris,

I agree with all your points below. TDFs cover all the cases you mention. The window animation stuff I now address by setting Mac OS X defaults. We still get missed frames warnings on window minimization and some popups, but they’re rare enough that I don’t worry about them.

And a “Save variable set” hotkey would be great!

Mark