Over in the Bug thread I posted that I'd discovered a problem in the transfer page where items can be lost while working on this. I think I can fix the problem, but it's a bit out of scope of where I'm working at the moment.
The issue is that the next/previous base buttons are not reinitializing the transfer menu when they are clicked. The transfer linked list just gets dumped with all the items in it. What I think should happen is that the prev/next callbacks should check if they are on the transfer page and issue a command to reset the transfer page and unload the cargo before the next base is selected. That is outside of the scope of cp_transfer_callbacks.c I'm working on now, and at least for the moment, I'd like to stay in that scope. But I could save the current state in cp_transfer_callbacks in global and check it when the items are accessed to see if there had been a change in the source base, and reset things when I detect that. I'm looking if I can detect that state without using globals (I don't like globals, though I know it's common in C).
Ideas? Direction? Leave it for others to fix?
