Week 9: Bugs, Bugs Everywhere...

While I’ve been working on the test code interface, I’ve noticed a rather annoying bug. Whenever one navigates back from the test authoring perspective to the edit code perspective, the declarations editor disappears, and the IDE looks like the screen-cap below.

There’s only one instance of the declarations editor, so there needs to be some sort of way for the code perspective as well as the test editor perspective to “share” that one instance.

The solution I came up with this week was to add a refresh method to the code perspective.The refresh method sets the code perspective’s view to null, then calls createView(). The refresh method is called from handlePreActivation() and adds about 50 milliseconds to the code perspective loading time. Thus far, I’ve been unable to isolate the calling of the refresh method to only switches from the test editor to the code perspective.

I realize this may seem like a trivial programming problem, but I bring it up because it’s really irked me for the past week or so, and I have two questions: Is this a good solution? And are there any better solutions?

I’m currently working on figuring out how to detect when not to refresh the code perspective (like when the user goes from the scene editor perspective to the code perspective).

Also, I’ve begun to put the code in place to support communication with the community. At this point, I’m concentrating on the step where test authors receive 10 worlds from the community to test their scripts on. By the end of today, the fourth step of the test authoring process will display 10 worlds from the community (…hopefully).