PLPTool: Module preset carry-over for new / open project from previous

[GoogleCodeExporter]

If one is simulating a project and proceeds to create a new project or open 
another project without exiting simulation mode first, the I/O preset will 
carry over.

Example scenario:

User is working on project A and is in simulation mode (plp.sim_mode is true). 
This project does not have a VGA module loaded in the I/O registry.

He proceeds to open another project (project B) that has VGA in the saved 
preset in the project file.

Result: No VGA in project B simulation in that session. Worse: this new preset 
will get saved if the user save the project.

This is not usually a problem since users don't typically modify the I/O 
registry, but it is annoying if you DO have to add/remove modules across 
different projects.

Original issue reported on code.google.com by wheerdam@gmail.com on 7 Oct 2011 at 4:35

[GoogleCodeExporter]

The cause of this bug is when Develop starts a new project or open an existing 
one (newPLPFile(), openPLPFile() methods), it doesn't check whether the project 
is in simulation mode. Fix on the way.

Original comment by wheerdam@gmail.com on 7 Oct 2011 at 5:04

[GoogleCodeExporter]

This issue was closed by revision 266b308550b9.

Original comment by wheerdam@gmail.com on 7 Oct 2011 at 5:05

• Changed state: Fixed