Better console managment

[GoogleCodeExporter]

As mentioned in issue 98, I want to redo the way that the simulations and 
console are integrated.  The launch protocol in eclipse is the way to do this 
(I believe), but it will take some work to get it running with the initial 
version of the simulation api that I wrote some time ago. 

Original issue reported on code.google.com by AdamMatthewSmith on 13 Oct 2012 at 7:29

[GoogleCodeExporter]

Would it be possible to simply get RB to automatically switch to the console 
connected to the model that is currently being viewed in the editor? This small 
change would improve the usability a lot. As things are currently, if you open 
two models sequentially and then go back to the first one the console doesn't 
switch back. This has caused a lot of confusion with students in the group. 
It's not immediately obvious to them that there are multiple consoles that you 
can switch between. For the sake of usability, this is a pretty high priority 
issue.

Original comment by lh64@cornell.edu on 30 Nov 2012 at 10:02

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

This is the next thing that I want to focus on. I'm planning on spending a good 
chunk of time on rb in the next few weeks, and I'll make this my first 
priority. 

Original comment by AdamMatthewSmith on 30 Nov 2012 at 12:06

[GoogleCodeExporter]

I submitted the short term fix suggested in comment #1.  There are still some 
issues with this (have two models open, select the not currently viewed one in 
the explorer for simulation, run it -> the running model is shown and not the 
current viewed), but it is better than before.  

As said in the original description, I believe there is a better way to use the 
console via the launch configuration api, but I am not familiar with it.  

Original comment by AdamMatthewSmith on 21 Apr 2013 at 12:48