Leaderboard

You could explore some of the application properties, if I'm not mistaken there's a 'private' or 'system' property that should make it invisible for the GSW. Or you could launch the GSW. There is a menu launch token for the GSW that loads it into the front. Try to get Christina into this discussion, since she wrote a lot of code for the GSW. Ton

I should point out that in the configuration files example the View writes the control reference to the Model object (the Command) dynamically at run-time. That is actually an important part of the design. That way I can use any collection of controls I want, without editing the Model code in any way whatsoever. So the Model is still essentially independent. The alternative is to write the control data to the Model instead of the reference. Then the Model can send updated data (from a file, for instance) to the View, which can handle updating the control in turn. I decided that: 1) since I was using XML it was a little simpler to use the reference 2) since for this application the View will always be the same (just with different controls, which the solution handles gracefully) it was OK for the View to pass references to the controls to the Model. Note that in other situations, e.g., where we have a component Controller that may interface with View A, View B, or another Component (which we do all the time) we don't pass references, only "pure data," since the references would not be meaningful in all application contexts. Paul