Vanessa:
The simple answer is that the VI editing window does not behave like the editing windows of most plugins. What happens is that you can access the VI window when it is floating on top of the Logic windows - as long as you don't then click on the any of the Logic windows. The VI window goes to the back if you click on the Logic windows - leaving only the small control panel visible. While this is different in operation from other plugins it is, I think, more of a feature than a problem because the VI window takes up quite a bit of screen real estate - - it simply gets out of the way when you are not accessing it so you don't have close it or maneuver it this way and that to get at the parameters you wish to work on in Logic. Should you want to edit in the VI window, then you can instantly summon it to the front with the "show window" button on the control panel. This is actually a lot faster than having to close and reopen windows to regain screen real estate as one has to do with more standardly behaving plugins with large GUIs - - e.g. Altiverb or Ozone 3. Actually it's behavior is not dissimilar from Logic itself, where you summon different pages with keyboard commands. Of course if you have a 30" monitor, you could position the VI interfaces somewhere on the screen so that when they go the back they are still visible. Or if you had two 23" monitors you could put Logic on one and the VI interfaces on the other.
Also, in Logic, you need to name the tracks manually - - unlike what happens when you load an instrument into EXS24. Apart from the technical issues that may have made this difficult - - since the VI software is not really running as plugin but is a separate application with its own memory partition - - it may also have been a decision based on the fact that each instance of VI software is likely to have a matrix - - with quite a number of patches in it. (However it would be helpful if the Matrix name automatically appeared as the track name.) What I do after constructing a matrix is write down its structure and control data and then save it as a custom matrix. That way, even months later, I can usually find a matrix that will provide a useful starting point for new work. I also try to design my matrices so that they have similar structures and control parameters.
I hope this is helpful.
