Many workflows involve working with multiple applications at once. It is not uncommon that each of these applications consumes a lot of screen real estate.
Such workflows work perfectly fine on a multi-head workstation. On a low-resolution laptop, however, this can be problematic. We've seen workflows where users occasionally want to continue these real estate consuming workflows from their laptop when they are not at the office.
Before bug 7793, one could simply uncheck the "Resize remote session to the local window" checkbox and choose an arbitrary resolution higher than the native resolution of the laptop. This would result in a session where the user could pan the viewport.
As this is no longer possible, screen real estate consuming workflows become cramped and unmanageable when reconnecting to the session from a low-resolution device.
Note that this is very unclear if this is within the scope of ThinLinc. This is something that would happen if users tried to run their workflow locally on the laptop, and hence ThinLinc is fulfilling its goal of giving a local experience, good and bad.
The relevant questions are:
1. Should we provide a better experience than a local one in this case?
2. Is this not fully equivalent to working locally, e.g. because the session is being moved between clients, and hence could be considered within the scope of being a remote desktop issue?
I tried to find if there is something like this in similar products, like Citrix, Microsoft RDS and NoMachine, but I couldn't find anything obvious.
RDS and NoMachine have some resolution setting, but it doesn't go very high, and it's not clear how multiple monitors are handled. I wonder if they are simply holdovers from a time when they were unable to resize dynamically, much like we had.