Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 331283

Summary: Metabm editor does not open up when workbench is first opened
Product: [Modeling] AMP Reporter: Edward MacKerrow <mackerrow>
Component: AMFAssignee: Miles Parker <milesparker>
Status: RESOLVED WORKSFORME QA Contact: Miles Parker <milesparker>
Severity: normal    
Priority: P3    
Version: 0.8.0   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Edward MacKerrow CLA 2010-11-28 09:05:31 EST
when you close the workspace down and reopen it, the editor tree does not open up for an existing AMP project.  The only way I can get it to open is to close the project and reopen it again.



Version: 0.8.0.v201007010013-17N-9oB5855Q58558E
Build id: {0}
Comment 1 Miles Parker CLA 2010-11-28 12:33:38 EST
I'm not sure exactly what the issue is. Are you saying that if you had a model open up before hand that the editor isn't open when you restart the workspace? I'm not able to reproduce that. Please give step by step instructions for replicating issue.
Comment 2 Edward MacKerrow CLA 2010-11-28 12:47:45 EST
This bug is not reproducing for me now (honestly, it was happening ;-) )

1) If I had an AMP project open, working on the model and running a simulation, then

2) close out of Eclipse without closing the project, then

3) when reopening Eclipse the AMP project icon in the explorer was not working properly, it did not have a triangle to open, even though the project icon did not indicate it was closed.  To work around this, I would close the project and then reopen it and everything was fine.

Not sure why I do not see it now, perhaps there was an issue with a broken model on my part.
Comment 3 Miles Parker CLA 2010-11-28 18:50:58 EST
I've seen this happen with all kinds of projects before, i.e. I don't think it is AMP specific. I actually think it might be Subversive related as I've only seen it happen for an SVN project. Marking as WORKSFORME but pls reopen if you find the same issue and it seems AMP related.