Closed DartBot closed 9 years ago
This comment was originally written by jimhug@google.com
Attachment: [ui 2.zip](https://storage.googleapis.com/google-code-attachments/dart/issue-1632/comment-1/ui 2.zip) (19.94 KB)
Jim, could you provide exact steps to follow to reproduce this problem? I have duplicated it, sort of, but I'm not confident what I've done fits your symptoms. Besides, my dup doesn't look right, since the files are correct on disk and we use frog to create the javascript.
This comment was originally written by jimhug@google.com
I can't easily repro this problem in the latest editor builds - 4586. I'm going to mark the priority as Low until I can repro it, and you should feel free to close the bug if you see fit.
Removed Priority-Critical label. Added Priority-Low label.
Still an issue with latest build?
This comment was originally written by jimhug@google.com
Is the current integration build stable? I had been waiting to move to a new editor build until I heard word from the editor team that the new file view had fully landed. Is this in now for me to try?
I'd give the new integration build a whirl. And let us know how you fare... Thanks!
Please confirm that this is still a problem with the most recent build. If so, reassign to to Dan Rubel.
Set owner to jimhug@google.com.
This issue was originally filed by jimhug@google.com
Using DartEditor - build 3934
The attached project builds correctly. However, if I have both the bench and ui libraries open, and then I go into the ui library and make changes, the editor does a full recompile - but it appears to be using an older copy of the files. I can make changes to bench.dart after this happens, see a full recompile happen automatically and also force a full recompile. In all cases, the generated bench.dart.js file is based on an old copy of bench.dart that must somehow be being kept in memory.
I can temporarily fix this issue by quitting the editor and starting again; however, after a small amont of editing - particularly editing in a different library (ui) I can get back to the state where the builds are all happening against an old copy of bench.dart. This issue is serious enough that I can no longer use the DartEditor until it is resolved.