closed loop protocol needs a set of default GUI tools

[GoogleCodeExporter]

the custom closed loop DLL could use a class that takes most of the headache 
out of writing a GUI- namely, something that can create a GUI in a separate 
thread, and update it outside of the main closed loop thread.  User could then 
write an 'update' function or something similar.

Alternatively, the GUI could be built in as one of NR's tabs

Original issue reported on code.google.com by RZellerT...@gmail.com on 12 Mar 2012 at 12:59

[GoogleCodeExporter]

I totally disagree with this. We should not interfere with how the user wishes 
to construct a CL protocol.

C#'s native support for constructing GUIs and all else is more than enough.

Original comment by jonathan...@gmail.com on 2 Apr 2012 at 3:30

[GoogleCodeExporter]

Perhaps a sample GUI that users could modify and work from? Not everyone is 
going to want to write C# from scratch, or is capable of it.

Original comment by nlaxpat....@gmail.com on 2 Apr 2012 at 3:34

[GoogleCodeExporter]

'sample' is perhaps a better term than what I posted initially- something like 
a stripped down version of SIMOC's gui or the gui I'm currently building, some 
skeleton /template code that the user has the option to base their own stuff on.

Which is to say- I'm planning on posting a stripped down version of my gui once 
I get the rest of the bugs out of it.

Original comment by RZellerT...@gmail.com on 3 Apr 2012 at 3:45

[GoogleCodeExporter]

The closed-loop examples, available for download here:

http://code.google.com/p/neurorighter/downloads/list

and source here:

http://code.google.com/p/neurorighter/source/browse/NR-ClosedLoop-Examples

Include the 'SeizureIntervention' example, which has a GUI in it. So I'm 
marking this fixed.

Original comment by jonathan...@gmail.com on 8 Nov 2012 at 3:53

• Changed state: Fixed