Back to bug 7006

Who When What Removed Added
ossman 2017-08-14 14:07:22 CEST Target Milestone --- MediumPrio
mcurtis 2018-02-21 02:06:13 CET CC mcurtis
huglu 2021-06-09 09:28:05 CEST CC huglu
huglu 2021-06-09 14:28:11 CEST Acceptance Criteria ,
but not all monitors.
- Which monitors to use should be configurable via:
* A graphical interface component in the options dialog
(the “screen” tab).
* A configuration file that persistently stores the
settings.
flag on the command line interface.
- The graphical components should look no matter what
styling or theme FLTK has. - It should be possible to use full screen over multiple
huglu 2021-06-09 14:29:02 CEST Acceptance Criteria ,
but not all monitors.
- Which monitors to use should be configurable via:
* A graphical interface component in the options dialog
(the “screen” tab).
* A configuration file that persistently stores the
settings.
flag on the command line interface.
- The graphical components should look no matter what
styling or theme FLTK has. - It should be possible to use full screen over multiple 		, but not all monitors.

- Which monitors to use should be configurable via:
* A graphical interface component in the options dialog (the “screen” tab).
* A configuration file that persistently stores the settings.
* A flag on the command line interface.
- The graphical components should look no matter what styling or theme FLTK has. - It should be possible to use full screen over multiple
huglu 2021-06-21 17:21:58 CEST Acceptance Criteria command line interface.
- The graphical components should look no matter what styling or theme FLTK has. - It should be possible to use full screen over multiple , but not all monitors.

- Which monitors to use should be configurable via:
* A graphical interface component in the options dialog (the “screen” tab).
* A configuration file that persistently stores the settings.
* A flag on the 		, the vncviewer configuration file and via the command line interface.
- The monitors should be identified using a numerical identifier that the user should be able to deduce either from the GUI or by reading the manual.
* The numerical identifier should indicate what monitors are required to be part of the selection for it to be valid (the frame buffer must always be a square). To indicate this By modifying settings of vncviewer, the user should be able to enable one or more monitors to be used in fullscreen mode:
- The system’s monitor configuration should be presented graphically to the user.
- They should be able to identify monitors an, coordinates etc).
- When the user clicks on a monitor with the mouse, if no monitors have been selected, the regular fullscreen mode should be used instead. should be persistent and unchanged between sessions. It shouldn’t be dependent on implementation details and should be predictable.
* The user should be able to determine which monitors are selected and what monitors are available to be used.
*, a square representing the frame buffer should be presented behind the monitors if needed.

The user should be able to use vncviewer, when connected to a VNC session, without reading the manual, be able to choose what monitors to use.
- They should be able to modify the config using either the GUI, it should either be selected or deselected depending on its previous state.
- The user should be able to see clearly in the GUI whether a monitor is selected (either manually or as a consequence of selection limitations) or deselected.
- The GUI Any limitations regarding what monitors can be selected should be explained to the user.
- When the user hovers over a monitor, additional information that can be helpful to identify the monitor should be presented (resolution, with the selected monitors.
- The badge giving a hint to the user to press F8 should be centered as before this feature was implemented.
- If the configuration chosen by a user is invalid, the fallback should be understandable. For example
huglu 2021-06-22 16:56:17 CEST Acceptance Criteria , without reading the manual, be able to choose what monitors to use.
- They should be able to modify the config using either the GUI, it should either be selected or deselected depending on its previous state.
- The user should be able to see clearly in the GUI whether a monitor is selected (either manually or as a consequence of selection limitations) or deselected.
- The GUI Any limitations regarding what monitors can be selected should be explained to the user.
- When the user hovers over a monitor, additional information that can be helpful to identify the monitor should be presented (resolution, with the selected monitors.
- The badge giving a hint to the user to press F8 should be centered as before this feature was implemented.
- If the configuration chosen by a user is invalid, the fallback should be understandable. For example , the vncviewer configuration file and via the command line interface.
- The monitors should be identified using a numerical identifier that the user should be able to deduce either from the GUI or by reading the manual.
* The numerical identifier should indicate what monitors are required to be part of the selection for it to be valid (the frame buffer must always be a square). To indicate this By modifying settings of vncviewer, the user should be able to enable one or more monitors to be used in fullscreen mode:
- The system’s monitor configuration should be presented graphically to the user.
- They should be able to identify monitors an, coordinates etc).
- When the user clicks on a monitor with the mouse, if no monitors have been selected, the regular fullscreen mode should be used instead. should be persistent and unchanged between sessions. It shouldn’t be dependent on implementation details and should be predictable.
* The user should be able to determine which monitors are selected and what monitors are available to be used.
*, a square representing the frame buffer should be presented behind the monitors if needed.

The user should be able to use vncviewer, when connected to a VNC session 		, but not all monitors:
[ ] The system’s monitor configuration should be presented graphically to the user (*).
[ ] The user should be able to identify monitors:
[ ] Graphically (*)
[ ] By reading an explanation in the manual.
[ ] The user selected and what monitors are available to be used (*).
[ ] The user should be able to find additional information about a monitor that can be helpful to identify it:
[ ] The index used in the configuration file.
[ ] Monitor resolution
, the regular fullscreen mode should be used.
[ ] If monitors have been selected such that they do not create a rectangular frame buffer (for example if there is a gap between them) setups with the same monitor arrangement selected or not (*).
[ ] The user should be able to determine when a monitor has been included in the configuration because it is required to make the frame buffer rectangular.
[ ] The user should be given an explanation why this is the, it should be discarded.

Maintaining current behaviour:
[ ] When a VNC session has been started “Press F8 to open the context menu” should be shown in the middle of one of the selected displays.
[ ] It should be centered horizontally and should be able to modify the configuration:
[ ] Graphically (*)
[ ] From the command line interface (*)
[ ] From the configuration file (*)
[ ] The monitors should have a persistent identifier (*)
[ ] The identifier is used in the [ ] Monitor coordinates
[ ] A friendly name, the required monitors for it to be a rectangle should be included.
[ ] If the user has selected monitors, but not enabled “Selected”-mode, the selected monitors should not be used.
[ ] If the user has selected monitors and enabled “Selected” Those marked with (*) are considered minimum requirements for the first useful version.

The user should be able to use TigerVNC in fullscreen mode with multiple, but with different physical monitors that they move their computer between.
[ ] The user should be able to deduce a monitor's identifier by reading the explanation in the manual.
[ ] The user should be able to determine what monitors are case.

If the user has an invalid configuration:
[ ] The user should, no matter how the selected display configuration is invalid, always reach fullscreen mode.
[ ] If no monitors have been selected vertically. configuration file.
[ ] The identifier is used in the command line interface.
[ ] The identifier should persist for as long as the system’s monitor arrangement does not change (*).
[ ] The identifier should persist if the user has two, that for example can be matched with xrandr on platforms using X11/Wayland.
[ ] The user should be able to graphically alter whether a display is selected or not (*).
[ ] The user should be able to graphically determine whether a monitor is, but disabled fullscreen mode, the session should not start in fullscreen mode.
[ ] If the user has included the same monitor multiple times, it should still be included.
[ ] If the user has included a monitor that doesn’t exist
huglu 2021-06-30 08:18:21 CEST Acceptance Criteria should be able to modify the configuration:
[ ] Graphically (*)
[ ] From the command line interface (*)
[ ] From the configuration file (*)
[ ] The monitors should have a persistent identifier (*)
[ ] The identifier is used in the [ ] Monitor coordinates
[ ] A friendly name, the required monitors for it to be a rectangle should be included.
[ ] If the user has selected monitors, but not enabled “Selected”-mode, the selected monitors should not be used.
[ ] If the user has selected monitors and enabled “Selected” Those marked with (*) are considered minimum requirements for the first useful version.

The user should be able to use TigerVNC in fullscreen mode with multiple, but with different physical monitors that they move their computer between.
[ ] The user should be able to deduce a monitor's identifier by reading the explanation in the manual.
[ ] The user should be able to determine what monitors are case.

If the user has an invalid configuration:
[ ] The user should, no matter how the selected display configuration is invalid, always reach fullscreen mode.
[ ] If no monitors have been selected vertically. configuration file.
[ ] The identifier is used in the command line interface.
[ ] The identifier should persist for as long as the system’s monitor arrangement does not change (*).
[ ] The identifier should persist if the user has two, that for example can be matched with xrandr on platforms using X11/Wayland.
[ ] The user should be able to graphically alter whether a display is selected or not (*).
[ ] The user should be able to graphically determine whether a monitor is, but disabled fullscreen mode, the session should not start in fullscreen mode.
[ ] If the user has included the same monitor multiple times, it should still be included.
[ ] If the user has included a monitor that doesn’t exist, but not all monitors:
[ ] The system’s monitor configuration should be presented graphically to the user (*).
[ ] The user should be able to identify monitors:
[ ] Graphically (*)
[ ] By reading an explanation in the manual.
[ ] The user selected and what monitors are available to be used (*).
[ ] The user should be able to find additional information about a monitor that can be helpful to identify it:
[ ] The index used in the configuration file.
[ ] Monitor resolution
, the regular fullscreen mode should be used.
[ ] If monitors have been selected such that they do not create a rectangular frame buffer (for example if there is a gap between them) setups with the same monitor arrangement selected or not (*).
[ ] The user should be able to determine when a monitor has been included in the configuration because it is required to make the frame buffer rectangular.
[ ] The user should be given an explanation why this is the, it should be discarded.

Maintaining current behaviour:
[ ] When a VNC session has been started “Press F8 to open the context menu” should be shown in the middle of one of the selected displays.
[ ] It should be centered horizontally and 		should be able to modify the configuration:
[ ] Graphically (*)
[ ] From the command line interface (*)
[ ] From the configuration file (*)
[ ] The monitors should have a persistent identifier (*)
[ ] The identifier is used in the [ ] Monitor coordinates
[ ] A friendly name, the regular fullscreen mode should be used.
[ ] If monitors have been selected such that they do not create a rectangular frame buffer (for example if there is a gap between them) Those marked with (*) are considered minimum requirements for the first useful version.

The user should be able to use TigerVNC in fullscreen mode with multiple, but with different physical monitors that they move their computer between.
[ ] The user should be able to deduce a monitor's identifier by reading the explanation in the manual.
[ ] The user should be able to determine what monitors are ] If the user alters their selected monitor configuration while connected to a VNC session, the session should be updated accordingly.

If the user has an invalid configuration:
[ ] The user should, it should be discarded.

Maintaining current behaviour:
[ ] When a VNC session has been started “Press F8 to open the context menu” should be shown in the middle of one of the selected displays.
[ ] It should be centered horizontally and configuration file.
[ ] The identifier is used in the command line interface.
[ ] The identifier should persist for as long as the system’s monitor arrangement does not change (*).
[ ] The identifier should persist if the user has two, that for example can be matched with xrandr on platforms using X11/Wayland.
[ ] The user should be able to graphically alter whether a display is selected or not (*).
[ ] The user should be able to graphically determine whether a monitor is, the required monitors for it to be a rectangle should be included.
[ ] If the user has selected monitors, but not enabled “Selected”-mode, the selected monitors should not be used.
[ ] If the user has selected monitors and enabled “Selected”, but not all monitors:
[ ] The system’s monitor configuration should be presented graphically to the user (*).
[ ] The user should be able to identify monitors:
[ ] Graphically (*)
[ ] By reading an explanation in the manual.
[ ] The user selected and what monitors are available to be used (*).
[ ] The user should be able to find additional information about a monitor that can be helpful to identify it:
[ ] The index used in the configuration file.
[ ] Monitor resolution
, no matter how the selected display configuration is invalid, always reach fullscreen mode.
[ ] If no monitors have been selected vertically. setups with the same monitor arrangement selected or not (*).
[ ] The user should be able to determine when a monitor has been included in the configuration because it is required to make the frame buffer rectangular.
[ ] The user should be given an explanation why this is the case.
[, but disabled fullscreen mode, the session should not start in fullscreen mode.
[ ] If the user has included the same monitor multiple times, it should still be included.
[ ] If the user has included a monitor that doesn’t exist
huglu 2021-07-02 12:48:28 CEST Acceptance Criteria [ ] Monitor coordinates
[ ] A friendly name, the regular fullscreen mode should be used.
[ ] If monitors have been selected such that they do not create a rectangular frame buffer (for example if there is a gap between them) Those marked with (*) are considered minimum requirements for the first useful version.

The user should be able to use TigerVNC in fullscreen mode with multiple, but with different physical monitors that they move their computer between.
[ ] The user should be able to deduce a monitor's identifier by reading the explanation in the manual.
[ ] The user should be able to determine what monitors are ] If the user alters their selected monitor configuration while connected to a VNC session, the session should be updated accordingly.

If the user has an invalid configuration:
[ ] The user should, it should be discarded.

Maintaining current behaviour:
[ ] When a VNC session has been started “Press F8 to open the context menu” should be shown in the middle of one of the selected displays.
[ ] It should be centered horizontally and configuration file.
[ ] The identifier is used in the command line interface.
[ ] The identifier should persist for as long as the system’s monitor arrangement does not change (*).
[ ] The identifier should persist if the user has two, that for example can be matched with xrandr on platforms using X11/Wayland.
[ ] The user should be able to graphically alter whether a display is selected or not (*).
[ ] The user should be able to graphically determine whether a monitor is, the required monitors for it to be a rectangle should be included.
[ ] If the user has selected monitors, but not enabled “Selected”-mode, the selected monitors should not be used.
[ ] If the user has selected monitors and enabled “Selected”, but not all monitors:
[ ] The system’s monitor configuration should be presented graphically to the user (*).
[ ] The user should be able to identify monitors:
[ ] Graphically (*)
[ ] By reading an explanation in the manual.
[ ] The user selected and what monitors are available to be used (*).
[ ] The user should be able to find additional information about a monitor that can be helpful to identify it:
[ ] The index used in the configuration file.
[ ] Monitor resolution
, no matter how the selected display configuration is invalid, always reach fullscreen mode.
[ ] If no monitors have been selected vertically. setups with the same monitor arrangement selected or not (*).
[ ] The user should be able to determine when a monitor has been included in the configuration because it is required to make the frame buffer rectangular.
[ ] The user should be given an explanation why this is the case.
[, but disabled fullscreen mode, the session should not start in fullscreen mode.
[ ] If the user has included the same monitor multiple times, it should still be included.
[ ] If the user has included a monitor that doesn’t exist should be able to modify the configuration:
[ ] Graphically (*)
[ ] From the command line interface (*)
[ ] From the configuration file (*)
[ ] The monitors should have a persistent identifier (*)
[ ] The identifier is used in the 		[ ] Monitor coordinates
[ ] A friendly name, the regular fullscreen mode should be used.
[ ] If monitors have been selected such that they do not create a rectangular frame buffer (for example if there is a gap between them) Those marked with (*) are considered minimum requirements for the first useful version.

The user should be able to use TigerVNC in fullscreen mode with multiple, but with different physical monitors that they move their computer between.
[ ] The user should be able to deduce a monitor's identifier by reading the explanation in the manual.
[ ] The user should be able to determine what monitors are ] If the user alters their selected monitor configuration while connected to a VNC session, the session should be updated accordingly.

If the user has an invalid configuration:
[ ] The user should, it should be discarded.

Maintaining current behaviour:
[ ] When a VNC session has been started “Press F8 to open the context menu” should be shown, centered on the top configuration file.
[ ] The identifier is used in the command line interface.
[ ] The identifier should persist for as long as the system’s monitor arrangement does not change (*).
[ ] The identifier should persist if the user has two, that for example can be matched with xrandr on platforms using X11/Wayland.
[ ] The user should be able to graphically alter whether a display is selected or not (*).
[ ] The user should be able to graphically determine whether a monitor is, the required monitors for it to be a rectangle should be included.
[ ] If the user has selected monitors, but not enabled “Selected”-mode, the selected monitors should not be used.
[ ] If the user has selected monitors and enabled “Selected”, but not all monitors:
[ ] The system’s monitor configuration should be presented graphically to the user (*).
[ ] The user should be able to identify monitors:
[ ] Graphically (*)
[ ] By reading an explanation in the manual.
[ ] The user selected and what monitors are available to be used (*).
[ ] The user should be able to find additional information about a monitor that can be helpful to identify it:
[ ] The index used in the configuration file.
[ ] Monitor resolution
, no matter how the selected display configuration is invalid, always reach fullscreen mode.
[ ] If no monitors have been selected, on one of the selected displays.
[ ] It should be centered horizontally and vertically. setups with the same monitor arrangement selected or not (*).
[ ] The user should be able to determine when a monitor has been included in the configuration because it is required to make the frame buffer rectangular.
[ ] The user should be given an explanation why this is the case.
[, but disabled fullscreen mode, the session should not start in fullscreen mode.
[ ] If the user has included the same monitor multiple times, it should still be included.
[ ] If the user has included a monitor that doesn’t exist should be able to modify the configuration:
[ ] Graphically (*)
[ ] From the command line interface (*)
[ ] From the configuration file (*)
[ ] The monitors should have a persistent identifier (*)
[ ] The identifier is used in the
huglu 2021-07-06 13:01:43 CEST Acceptance Criteria [ ] Monitor coordinates
[ ] A friendly name, the regular fullscreen mode should be used.
[ ] If monitors have been selected such that they do not create a rectangular frame buffer (for example if there is a gap between them) Those marked with (*) are considered minimum requirements for the first useful version.

The user should be able to use TigerVNC in fullscreen mode with multiple, but with different physical monitors that they move their computer between.
[ ] The user should be able to deduce a monitor's identifier by reading the explanation in the manual.
[ ] The user should be able to determine what monitors are ] If the user alters their selected monitor configuration while connected to a VNC session, the session should be updated accordingly.

If the user has an invalid configuration:
[ ] The user should, it should be discarded.

Maintaining current behaviour:
[ ] When a VNC session has been started “Press F8 to open the context menu” should be shown, centered on the top configuration file.
[ ] The identifier is used in the command line interface.
[ ] The identifier should persist for as long as the system’s monitor arrangement does not change (*).
[ ] The identifier should persist if the user has two, that for example can be matched with xrandr on platforms using X11/Wayland.
[ ] The user should be able to graphically alter whether a display is selected or not (*).
[ ] The user should be able to graphically determine whether a monitor is, the required monitors for it to be a rectangle should be included.
[ ] If the user has selected monitors, but not enabled “Selected”-mode, the selected monitors should not be used.
[ ] If the user has selected monitors and enabled “Selected”, but not all monitors:
[ ] The system’s monitor configuration should be presented graphically to the user (*).
[ ] The user should be able to identify monitors:
[ ] Graphically (*)
[ ] By reading an explanation in the manual.
[ ] The user selected and what monitors are available to be used (*).
[ ] The user should be able to find additional information about a monitor that can be helpful to identify it:
[ ] The index used in the configuration file.
[ ] Monitor resolution
, no matter how the selected display configuration is invalid, always reach fullscreen mode.
[ ] If no monitors have been selected, on one of the selected displays.
[ ] It should be centered horizontally and vertically. setups with the same monitor arrangement selected or not (*).
[ ] The user should be able to determine when a monitor has been included in the configuration because it is required to make the frame buffer rectangular.
[ ] The user should be given an explanation why this is the case.
[, but disabled fullscreen mode, the session should not start in fullscreen mode.
[ ] If the user has included the same monitor multiple times, it should still be included.
[ ] If the user has included a monitor that doesn’t exist should be able to modify the configuration:
[ ] Graphically (*)
[ ] From the command line interface (*)
[ ] From the configuration file (*)
[ ] The monitors should have a persistent identifier (*)
[ ] The identifier is used in the 		[ ] Monitor coordinates
[ ] A friendly name, the regular fullscreen mode should be used.
[ ] If monitors have been selected such that they do not create a rectangular frame buffer (for example if there is a gap between them) https://bugzilla.xfce.org/show_bug.cgi?id=14015. Those marked with (*) are considered minimum requirements for the first useful version.

The user should be able to use TigerVNC in fullscreen mode with multiple, but with different physical monitors that they move their computer between.
[ ] The user should be able to deduce a monitor's identifier by reading the explanation in the manual.
[ ] The user should be able to determine what monitors are ] If the user alters their selected monitor configuration while connected to a VNC session, the session should be updated accordingly.

If the user has an invalid configuration:
[ ] The user should, it should be discarded.

Maintaining current behaviour:
[ ] When a VNC session has been started “Press F8 to open the context menu” should be shown, centered on the top configuration file.
[ ] The identifier is used in the command line interface.
[ ] The identifier should persist for as long as the system’s monitor arrangement does not change (*).
[ ] The identifier should persist if the user has two, that for example can be matched with xrandr on platforms using X11/Wayland.
[ ] The user should be able to graphically alter whether a display is selected or not (*).
[ ] The user should be able to graphically determine whether a monitor is, the required monitors for it to be a rectangle should be included.
[ ] If the user has selected monitors, but not enabled “Selected”-mode, the selected monitors should not be used.
[ ] If the user has selected monitors and enabled “Selected”, but not all monitors:
[ ] The system’s monitor configuration should be presented graphically to the user (*).
[ ] The user should be able to identify monitors:
[ ] Graphically (*)
[ ] By reading an explanation in the manual.
[ ] The user selected and what monitors are available to be used (*).
[ ] The user should be able to find additional information about a monitor that can be helpful to identify it:
[ ] The index used in the configuration file.
[ ] Monitor resolution
, no matter how the selected display configuration is invalid, always reach fullscreen mode.
[ ] If no monitors have been selected, on one of the selected displays.
[ ] It should be centered horizontally and vertically.

Special cases:
[ ] Tiled displays (consisting of multiple panels) should only show up as one display in the settings interface. See setups with the same monitor arrangement selected or not (*).
[ ] The user should be able to determine when a monitor has been included in the configuration because it is required to make the frame buffer rectangular.
[ ] The user should be given an explanation why this is the case.
[, but disabled fullscreen mode, the session should not start in fullscreen mode.
[ ] If the user has included the same monitor multiple times, it should still be included.
[ ] If the user has included a monitor that doesn’t exist should be able to modify the configuration:
[ ] Graphically (*)
[ ] From the command line interface (*)
[ ] From the configuration file (*)
[ ] The monitors should have a persistent identifier (*)
[ ] The identifier is used in the
huglu 2021-07-13 08:56:23 CEST Acceptance Criteria setups with the same monitor arrangement selected or not (*).
[ ] The user should be able to determine when a monitor has been included in the configuration because it is required to make the frame buffer rectangular.
[ ] The user should be given an explanation why this is the case.
[, but disabled fullscreen mode, the session should not start in fullscreen mode.
[ ] If the user has included the same monitor multiple times, it should still be included.
[ ] If the user has included a monitor that doesn’t exist should be able to modify the configuration:
[ ] Graphically (*)
[ ] From the command line interface (*)
[ ] From the configuration file (*)
[ ] The monitors should have a persistent identifier (*)
[ ] The identifier is used in the [ ] Monitor coordinates
[ ] A friendly name, the regular fullscreen mode should be used.
[ ] If monitors have been selected such that they do not create a rectangular frame buffer (for example if there is a gap between them) https://bugzilla.xfce.org/show_bug.cgi?id=14015. Those marked with (*) are considered minimum requirements for the first useful version.

The user should be able to use TigerVNC in fullscreen mode with multiple, but with different physical monitors that they move their computer between.
[ ] The user should be able to deduce a monitor's identifier by reading the explanation in the manual.
[ ] The user should be able to determine what monitors are ] If the user alters their selected monitor configuration while connected to a VNC session, the session should be updated accordingly.

If the user has an invalid configuration:
[ ] The user should, it should be discarded.

Maintaining current behaviour:
[ ] When a VNC session has been started “Press F8 to open the context menu” should be shown, centered on the top configuration file.
[ ] The identifier is used in the command line interface.
[ ] The identifier should persist for as long as the system’s monitor arrangement does not change (*).
[ ] The identifier should persist if the user has two, that for example can be matched with xrandr on platforms using X11/Wayland.
[ ] The user should be able to graphically alter whether a display is selected or not (*).
[ ] The user should be able to graphically determine whether a monitor is, the required monitors for it to be a rectangle should be included.
[ ] If the user has selected monitors, but not enabled “Selected”-mode, the selected monitors should not be used.
[ ] If the user has selected monitors and enabled “Selected” , but not all monitors:
[ ] The system’s monitor configuration should be presented graphically to the user (*).
[ ] The user should be able to identify monitors:
[ ] Graphically (*)
[ ] By reading an explanation in the manual.
[ ] The user selected and what monitors are available to be used (*).
[ ] The user should be able to find additional information about a monitor that can be helpful to identify it:
[ ] The index used in the configuration file.
[ ] Monitor resolution
, no matter how the selected display configuration is invalid, always reach fullscreen mode.
[ ] If no monitors have been selected, on one of the selected displays.
[ ] It should be centered horizontally and vertically.

Special cases:
[ ] Tiled displays (consisting of multiple panels) should only show up as one display in the settings interface. See 		same monitor arrangement not.
[ ] The user should be able to determine when a monitor has been included in the configuration because it is required to make the frame buffer rectangular.
[ ] The user should be given an explanation why this is the case (+).
[ ] If the, but disabled fullscreen mode, the session should not start in fullscreen mode.
[ ] If the user has included the same monitor multiple times, it should still be included, but only once.
[ ] If the user has included a monitor that doesn’t exist should be able to modify the configuration:
[ ] Graphically
[ ] From the command line interface
[ ] From the configuration file
[ ] The monitors should have a persistent identifier
[ ] The identifier is used in the configuration ] A more friendly description, the current monitor fullscreen mode should be used.
[ ] If monitors have been selected such that they do not create a rectangular frame buffer (for example if there is a gap between them), its behaviour should be preserved. Migration to a potentially new flag should be done automatically.

Special cases:
[ ] Tiled displays (consisting of multiple panels) should only show up as one display in the settings interface (+). See Items marked with (+) are considered to be future improvements, not part of the first version.

The user should be able to use TigerVNC in fullscreen mode with multiple, but with different physical monitors that they move their computer between.
[ ] The user should be able to deduce a monitor's identifier by reading the explanation in the manual.
[ ] The user should be able to determine what monitors are user alters their selected monitor configuration while connected to a VNC session, the session should be updated accordingly.

If the user has an invalid configuration:
[ ] The user should, no matter how the selected display configuration is invalid, it should be discarded, but an error message should be shown in the log.

Maintaining current behaviour / Migration behaviour:
[ ] When a VNC session has been started “Press F8 to open the context menu” should be shown, centered on the top file.
[ ] The identifier is used in the command line interface.
[ ] The identifier should persist for as long as the system’s monitor arrangement does not change.
[ ] The identifier should persist if the user has two setups with the, that for example can be matched with xrandr on platforms using X11/Wayland.

[ ] The user should be able to graphically alter whether a display is selected or not.
[ ] The user should be able to graphically determine whether a monitor is selected or, the required monitors for it to be a rectangle should be included.
[ ] If the user has selected monitors, but not enabled “Selected”-mode, the selected monitors should not be used.
[ ] If the user has selected monitors and enabled “Selected”-m https://bugzilla.xfce.org/show_bug.cgi?id=14015., but not all monitors:
[ ] The system’s monitor configuration should be presented graphically to the user (*).
[ ] The user should be able to identify monitors:
[ ] Graphically
[ ] By reading an explanation in the manual.
[ ] The user selected and what monitors are available to be used.
[ ] The user should be able to find additional information about a monitor that can be helpful to identify it:
[ ] The index used in the configuration file.
[ ] Monitor resolution.
[, always reach fullscreen mode.
[ ] If no monitors have been selected, on one of the selected displays.
[ ] The user should be able to identify that a command line/configuration file flag has been deprecated.
[ ] If a user has an old command line/configuration file flag in their config
huglu 2021-07-16 13:38:22 CEST Acceptance Criteria should be able to modify the configuration:
[ ] Graphically
[ ] From the command line interface
[ ] From the configuration file
[ ] The monitors should have a persistent identifier
[ ] The identifier is used in the configuration, always reach fullscreen mode.
[ ] If no monitors have been selected, on one of the selected displays.
[ ] The user should be able to identify that a command line/configuration file flag has been deprecated.
[ ] If a user has an old command line/configuration file flag in their config same monitor arrangement Items marked with (+) are considered to be future improvements, not part of the first version.

The user should be able to use TigerVNC in fullscreen mode with multiple not.
[ ] The user should be able to determine when a monitor has been included in the configuration because it is required to make the frame buffer rectangular.
[ ] The user should be given an explanation why this is the case (+).
[ ] If the, but disabled fullscreen mode, the session should not start in fullscreen mode.
[ ] If the user has included the same monitor multiple times, it should still be included, but only once.
[ ] If the user has included a monitor that doesn’t exist ] A more friendly description file.
[ ] The identifier is used in the command line interface.
[ ] The identifier should persist for as long as the system’s monitor arrangement does not change.
[ ] The identifier should persist if the user has two setups with the, the current monitor fullscreen mode should be used.
[ ] If monitors have been selected such that they do not create a rectangular frame buffer (for example if there is a gap between them), its behaviour should be preserved. Migration to a potentially new flag should be done automatically.

Special cases:
[ ] Tiled displays (consisting of multiple panels) should only show up as one display in the settings interface (+). See, but with different physical monitors that they move their computer between.
[ ] The user should be able to deduce a monitor's identifier by reading the explanation in the manual.
[ ] The user should be able to determine what monitors are, but not all monitors:
[ ] The system’s monitor configuration should be presented graphically to the user (*).
[ ] The user should be able to identify monitors:
[ ] Graphically
[ ] By reading an explanation in the manual.
[ ] The user user alters their selected monitor configuration while connected to a VNC session, the session should be updated accordingly.

If the user has an invalid configuration:
[ ] The user should, no matter how the selected display configuration is invalid, it should be discarded, but an error message should be shown in the log.

Maintaining current behaviour / Migration behaviour:
[ ] When a VNC session has been started “Press F8 to open the context menu” should be shown, centered on the top, that for example can be matched with xrandr on platforms using X11/Wayland.

[ ] The user should be able to graphically alter whether a display is selected or not.
[ ] The user should be able to graphically determine whether a monitor is selected or, the required monitors for it to be a rectangle should be included.
[ ] If the user has selected monitors, but not enabled “Selected”-mode, the selected monitors should not be used.
[ ] If the user has selected monitors and enabled “Selected”-m https://bugzilla.xfce.org/show_bug.cgi?id=14015. selected and what monitors are available to be used.
[ ] The user should be able to find additional information about a monitor that can be helpful to identify it:
[ ] The index used in the configuration file.
[ ] Monitor resolution.
[ 		be able to modify the configuration:
[ ] Graphically
[ ] From the command line interface
[ ] From the configuration file
[ ] The monitors should have a persistent identifier
[ ] The identifier is used in the configuration file.
, the current monitor fullscreen mode should be used.
[ ] If monitors have been selected such that they do not create a rectangular frame buffer (for example if there is a gap between them), its behaviour should be preserved. Migration to a potentially new flag should be done automatically.

Special cases:
[ ] Tiled displays (consisting of multiple panels) should only show up as one display in the settings interface (+). See arrangement Items marked with (+) are considered to be future improvements, not part of the first version.

The user should be able to use TigerVNC in fullscreen mode with multiple user alters their selected monitor configuration while connected to a VNC session, the session should be updated accordingly.

If the user has an invalid configuration:
[ ] The user should, no matter how the selected display configuration is invalid, it should be discarded, but an error message should be shown in the log.

Maintaining current behaviour / Migration behaviour:
[ ] When a VNC session has been started “Press F8 to open the context menu” should be shown, centered on the top, that for example can be matched with xrandr on platforms using X11/Wayland.

[ ] The user should be able to graphically alter whether a display is selected or not.
[ ] The user should be able to graphically determine whether a monitor is selected or [ ] The identifier is used in the command line interface.
[ ] The identifier should persist for as long as the system’s monitor arrangement does not change.
[ ] The identifier should persist if the user has two setups with the same monitor, the required monitors for it to be a rectangle should be included.
[ ] If the user has selected monitors, but not enabled “Selected”-mode, the selected monitors should not be used.
[ ] If the user has selected monitors and enabled “Selected”-m https://bugzilla.xfce.org/show_bug.cgi?id=14015., but with different physical monitors that they move their computer between.
[ ] The user should be able to deduce a monitor's identifier by reading the explanation in the manual.
[ ] The user should be able to determine what monitors are, but not all monitors:
[ ] The system’s monitor configuration should be presented graphically to the user.
[ ] The user should be able to identify monitors:
[ ] Graphically
[ ] By reading an explanation in the manual.
[ ] The user should, always reach fullscreen mode.
[ ] If no monitors have been selected, on one of the selected displays.
[ ] The user should be able to identify that a command line/configuration file flag has been deprecated.
[ ] If a user has an old command line/configuration file flag in their config not.
[ ] The user should be able to determine when a monitor has been included in the configuration because it is required to make the frame buffer rectangular.
[ ] The user should be given an explanation why this is the case (+).
[ ] If the, but disabled fullscreen mode, the session should not start in fullscreen mode.
[ ] If the user has included the same monitor multiple times, it should still be included, but only once.
[ ] If the user has included a monitor that doesn’t exist selected and what monitors are available to be used.
[ ] The user should be able to find additional information about a monitor that can be helpful to identify it:
[ ] Monitor resolution.
[ ] A more friendly description
ossman 2021-11-04 14:44:52 CET Depends on 7785
frifl 2021-11-17 10:08:40 CET See Also https://www.cendio.com/bugzilla/show_bug.cgi?id=7793
CC frifl
ossman 2021-12-09 09:40:09 CET Depends on 7803
wilsj 2021-12-13 11:38:35 CET CC wilsj
ossman 2021-12-27 10:43:26 CET Target Milestone MediumPrio 4.14.0
ossman 2021-12-27 10:55:27 CET Acceptance Criteria , but not all monitors:
[ ] The system’s monitor configuration should be presented graphically to the user.
[ ] The user should be able to identify monitors:
[ ] Graphically
[ ] By reading an explanation in the manual.
[ ] The user should selected and what monitors are available to be used.
[ ] The user should be able to find additional information about a monitor that can be helpful to identify it:
[ ] Monitor resolution.
[ ] A more friendly description, the current monitor fullscreen mode should be used.
[ ] If monitors have been selected such that they do not create a rectangular frame buffer (for example if there is a gap between them), its behaviour should be preserved. Migration to a potentially new flag should be done automatically.

Special cases:
[ ] Tiled displays (consisting of multiple panels) should only show up as one display in the settings interface (+). See arrangement user alters their selected monitor configuration while connected to a VNC session, the session should be updated accordingly.

If the user has an invalid configuration:
[ ] The user should, no matter how the selected display configuration is invalid, it should be discarded, but an error message should be shown in the log.

Maintaining current behaviour / Migration behaviour:
[ ] When a VNC session has been started “Press F8 to open the context menu” should be shown, centered on the top be able to modify the configuration:
[ ] Graphically
[ ] From the command line interface
[ ] From the configuration file
[ ] The monitors should have a persistent identifier
[ ] The identifier is used in the configuration file.
, that for example can be matched with xrandr on platforms using X11/Wayland.

[ ] The user should be able to graphically alter whether a display is selected or not.
[ ] The user should be able to graphically determine whether a monitor is selected or, the required monitors for it to be a rectangle should be included.
[ ] If the user has selected monitors, but not enabled “Selected”-mode, the selected monitors should not be used.
[ ] If the user has selected monitors and enabled “Selected”-m https://bugzilla.xfce.org/show_bug.cgi?id=14015. Items marked with (+) are considered to be future improvements, not part of the first version.

The user should be able to use TigerVNC in fullscreen mode with multiple, but with different physical monitors that they move their computer between.
[ ] The user should be able to deduce a monitor's identifier by reading the explanation in the manual.
[ ] The user should be able to determine what monitors are, always reach fullscreen mode.
[ ] If no monitors have been selected, on one of the selected displays.
[ ] The user should be able to identify that a command line/configuration file flag has been deprecated.
[ ] If a user has an old command line/configuration file flag in their config [ ] The identifier is used in the command line interface.
[ ] The identifier should persist for as long as the system’s monitor arrangement does not change.
[ ] The identifier should persist if the user has two setups with the same monitor not.
[ ] The user should be able to determine when a monitor has been included in the configuration because it is required to make the frame buffer rectangular.
[ ] The user should be given an explanation why this is the case (+).
[ ] If the, but disabled fullscreen mode, the session should not start in fullscreen mode.
[ ] If the user has included the same monitor multiple times, it should still be included, but only once.
[ ] If the user has included a monitor that doesn’t exist 		same labels as the system's monitor configuration GUI (BONUS)

* It should be visible which "extra" monitors are also included

* The configuration values should follow a system that is easy to understand

* The configuration should be stable as configuration is invalid

* Changes to which monitors are selected should take effect immediately

* If an old configuration is used then it should be migrated to an equivalent new configuration (BONUS) long as the logical layout of screens is stable

* Two systems with the same logical monitor setup should have identical configuration

* The configured monitors should be remembered * It should be possible to configure to use a specific sub set of monitors in full screen

* It should be possible to configure things graphically

* It should be easy to understand which monitor are configured in the GUI

* The GUI should use the , even if another mode is temporarily used

* If the configured setup isn't possible then a useful fallback should be used

* There should be a log entry when the configured setup cannot be used

* There should be a log entry when the stored
ossman 2021-12-28 16:11:20 CET Acceptance Criteria * It should be possible to configure to use a specific sub set of monitors in full screen

* It should be possible to configure things graphically

* It should be easy to understand which monitor are configured in the GUI

* The GUI should use the , even if another mode is temporarily used

* If the configured setup isn't possible then a useful fallback should be used

* There should be a log entry when the configured setup cannot be used

* There should be a log entry when the stored same labels as the system's monitor configuration GUI (BONUS)

* It should be visible which "extra" monitors are also included

* The configuration values should follow a system that is easy to understand

* The configuration should be stable as configuration is invalid

* Changes to which monitors are selected should take effect immediately

* If an old configuration is used then it should be migrated to an equivalent new configuration (BONUS) long as the logical layout of screens is stable

* Two systems with the same logical monitor setup should have identical configuration

* The configured monitors should be remembered 		* It should be possible to configure to use a specific sub set of monitors in full screen

* It should be possible to configure things graphically

* It should be easy to understand which monitor are configured in the GUI

* The GUI should use the it should be migrated to an equivalent new configuration (BONUS), even if another mode is temporarily used

* If the configured setup isn't possible then a useful fallback should be used

* There should be a log entry when the configured setup cannot be used

* There should be a log entry when the stored same labels as the system's monitor configuration GUI (BONUS)

* It should be visible which "extra" monitors are also included

* The configuration values should follow a system that is easy to understand

* The configuration should be stable as configuration is invalid

* Changes to which monitors are selected should take effect immediately

* A session created in full-screen mode should be created with the correct dimensions already from the start

* If an old configuration is used then long as the logical layout of screens is stable

* Two systems with the same logical monitor setup should have identical configuration

* The configured monitors should be remembered
ossman 2022-01-03 17:33:50 CET Resolution --- FIXED
Keywords relnotes
Status NEW RESOLVED
ossman 2022-01-03 17:35:26 CET Resolution FIXED ---
Status RESOLVED REOPENED
ossman 2022-01-04 09:40:40 CET Status REOPENED RESOLVED
Resolution --- FIXED
frifl 2022-01-04 12:17:53 CET Keywords frifl_tester
linma 2022-01-04 16:23:35 CET CC linma
Keywords linma_tester
linma 2022-01-11 17:14:52 CET Resolution FIXED ---
Status RESOLVED REOPENED
ossman 2022-01-12 17:52:33 CET Status REOPENED RESOLVED
Resolution --- FIXED
linma 2022-01-13 16:31:18 CET Status RESOLVED REOPENED
Resolution FIXED ---
ossman 2022-01-14 09:13:40 CET Status REOPENED RESOLVED
Resolution --- FIXED
linma 2022-01-21 12:49:45 CET Status RESOLVED CLOSED
ossman 2022-08-23 14:12:38 CEST See Also https://bugzilla.cendio.com/show_bug.cgi?id=3546

Back to bug 7006