The way I interpret that problem is that you haven't defined your contexts well enough. If it really is that big an effort to change which codebase you are working in then you need to have a context for @codebase1 @codebase2 etc.
Originally Posted by cfoley
What I find myself doing in debugging code (yes, I do some programming in addition to delivering lambs) is I set up a context for each major project. So for example right now I have a context for my LambTracker program. It's a subcontext of Android Development. In the LambTracker context I have several projects and next actions for them. One project is integrate yearly lambing history with the EID program. The current next action on it is design the SQL table to hold yearly lambing history for all ewes. Another project is Design the I/O Screens for the doSheepTask activity with a next action of Implement gravity for navigation buttons for both landscape vs portrait displays. Another project is Debugging LambTracker and the current next action is Figure out why loadDataBase works in the emulator but fails on the Nexus 7. They all have the context of LambTracker. So when I am in the development environment and working on LambTracker I can do all the tasks associated with it.
You need to adapt your contexts to be ones that work for you and there are many ways to do that.
I create, use, and then delete contexts as often as I need to.
Oogie McGuire - Mac, iPhone & Omnifocus
OogieM on Twitter
Paonia, CO USA