Concerning my earlier explanation...
I probably should have been more specific with my terminology, but the "window positions" that I was referring to concerned the position of the source, ui editor and function panel editor windows. At the time that the workspace was introduced, in CVI 6.0, only these windows existed as top-level windows. At the time, the CVI ADE consisted of a bunch of top-level windows, and persisting the size and position of these windows was a lot more important than it is today, since today, typically, users keep these widows confined within the top-level workspace window. These other "windows" that vix and Wolfgang are referring to now aren't really windows per se. Unlike the windows that are associated with a document on disk, these others are simply UI controls that are contained in the workspace UI panel (although, admittedly, this is an implementation detail that is not all that important, as evidenced, for example, that they all appear under a "Windows" menu).
As these workspace controls were introduced over time, their visibility and positions were persisted globally, as opposed to in the workspace.
I'm not necessarily defending the decision to persist these control positions globally. I just wanted to explain how they're different. It might be that, at least for some of these controls, it would make more sense to persist their position in the workspace. But I suspect that that would be a decision that will have to be made on a case by case basis. I understand and accept Wolfgang's point about the resource tracking window. Right now, I'm a tad skeptical that it would apply to all other controls. But I'll need to think about it some more.
Luis
