Here's a problem that can be solved easily. My question is how solve it correctly if I'd like to adhere to the MVVM pattern.
The model (M) is simple:
It analyses the machine's audio system (Mono or Stereo).
Passes this data to VM
Passes to VM volume level of all (Left/Right or Mono) channels
Gets the selected channel from the user
So, the VM is also quite simple. It holds the following boolean properties:
IsMono - true if mono system false if stereo
IsLeft - Relevant for stereo only
Also, there are 3 integer properties: RightLevel, LeftLevel and MonoLevel
The V will look like this (for Stereo):
Now, If the system is Mono then the Audio Channel frame box should not be displayed and the Audio Level frame box should display a single row, labeled "Mono". The source of the level meter will be MonoLevel.
The logic seems to be straightforward, but where do I implement it? I need to bind the IsVisible of frame box "Audio Channel" and other controls to "not IsMono", to bind the mono level meter to "IsMono". There are other (simple) logic that I need to add such as correct labeling and icon.
Should I use Convertors as my main tool? Are convertors considered to be a part of the View (V) or the VM? Should I create (in XAML) a separate view for Mono and Stereo and just make the selected one visible? Is it a good idea to extend the VM to include IsStereo (which is nothing but NOT IsMono) and other redundancies to simplify the XAML?