https://sourceforge.net/p/babes/tickets/2013-07-04T16:15:03.845000ZRecent changes to tickets2013-07-04T16:15:03.845000Z2013-07-04T16:15:03.845000ZSteve Thorntonhttps://sourceforge.net/u/heavymeshing/https://sourceforge.netdce788fa3d198052e64002822512f5cea48b8556

<div class="markdown_content"><p>There are quite a few minor bugs and inconsistences in version 1. This seems like a good point to do a fairly major rewrite and refactor of the code. The GUI will need to be modified (slightly) to fit in with this scheme (see ticket).</p></div>

2013-06-30T12:27:50.194000Z2013-06-30T12:27:50.194000ZSteve Thorntonhttps://sourceforge.net/u/heavymeshing/https://sourceforge.net266059cd3740ba8f98e480b37dac529231e88695

2013-06-30T08:44:37.227000Z2013-06-30T08:44:37.227000ZMike Playlehttps://sourceforge.net/u/mplayle/https://sourceforge.net1ccc8ffe3070209f0407682c39b2b6058f01396e

<div class="markdown_content"><p>Communication between the GUI and the simulation involves a FIFO in each direction and will probably grow to involve some shared memory too.</p> <p>Initially it supports 3 use cases:</p> <ul> <li>Simulation started from command line connects to existing GUI</li> <li>Simulation started from command line starts new GUI and connects to it</li> <li>Simulation started from within GUI</li> </ul> <p>At present this is done in a fairly ad hoc way. It would be a good idea to think it through and make sure it can do everything we want robustly without any risk of deadlocks or other problems.</p></div>

2013-06-30T08:44:37.227000Z2013-06-30T08:44:37.227000ZMike Playlehttps://sourceforge.net/u/mplayle/https://sourceforge.netc21d931579437c7c4aaffb5c455ace400f2ed034

<div class="markdown_content"><p>Ticket 1 has been modified: Formalise GUI-to-simulation communication protocol<br /> Edited By: Steve Thornton (heavymeshing)</p></div>