Bug 6106 - different versions of the client aren't grouped on Windows
Summary: different versions of the client aren't grouped on Windows
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: 1.3.1
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.8.0
Assignee: Pierre Ossman
Keywords: derfian_tester, prosaic
Depends on:
Reported: 2016-12-07 11:15 CET by Pierre Ossman
Modified: 2017-03-24 16:25 CET (History)
1 user (show)

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2016-12-07 11:15:36 CET
If you install a new version of the ThinLinc client, or run several versions at once, then Windows isn't grouping them properly on the task bar. This is very annoying as it takes up extra space, and you have to keep fixing the pinning.

The problem is that we include the version number in our ID, which we probably shouldn't. This is what Microsoft says:

> An application must provide its AppUserModelID in the following form. It can
> have no more than 128 characters and cannot contain spaces. Each section should
> be camel-cased.
> CompanyName.ProductName.SubProduct.VersionInformation
> CompanyName and ProductName should always be used, while the SubProduct and
> VersionInformation portions are optional and depend on the application's
> requirements. SubProduct allows a main application that consists of several
> subapplications to provide a separate taskbar button for each subapplication
> and its associated windows. VersionInformation allows two versions of an
> application to coexist while being seen as discrete entities. If an application
> is not intended to be used in that way, the VersionInformation should be
> omitted so that an upgraded version can use the same AppUserModelID as the
> version that it replaced.

Two versions of the client aren't really "discrete entities" like e.g. two versions of Java, so we really should group things.
Comment 2 Pierre Ossman cendio 2016-12-08 10:54:39 CET
Checked that the nightly build and a custom build were properly grouped.
Comment 3 Karl Mikaelsson cendio 2016-12-08 14:14:03 CET
(In reply to comment #2)
> Checked that the nightly build and a custom build were properly grouped.

Tested on Windows 10.

Confirming that builds prior to r31938 are grouped based on the version number, and that any builds after r31938 are grouped regardless of version number.


Note You need to log in before you can comment on or make changes to this bug.