Comment 7 for bug 1682542

I second the notion that adding support for multiple top bars would be a step in the right direction for multi-monitor support.

Also in regards to the comment that it would be non-trivial to implement this, in particular the part about: "[can't] use the monitor with the top bar as indicator for the primary monitor in Settings" - that sounds strictly like a code improvement, and a good reason to do this.

The primary monitor should have a unique attribute that designates it this way - other features tied to or built on top of it should not act as the method for determining which monitor is the primary one in the first place - we're breaking the single utility principle here no? It certainly would feel wrong to me if I tweaked my own Linux system and moved the top bar to a secondary display and suddenly the Ubuntu OS started treating that one as my primary display.

This refactoring would also make changes like this in the future much easier to achieve, since the stack doesn't have un-intuitive relationship to monitor components (it instead relates directly to the monitor class/module/object). Just my 2c.