armagetronad.protocol file does not slot properly
Bug #345171 reported by
Luke-Jr
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Armagetron Advanced |
New
|
Undecided
|
Unassigned | ||
Bug Description
This appears to be a static file. The 'exec' line needs to be fixed for multislot. As does the filename, so multiple versions don't overwrite the same .protocol file.
Revision history for this message
| Manuel Moos (z-man) wrote | #1 |
To post a comment you must log in.
Right. However, that's just the surface problem. The underlying problem is: if I have multiple versions installed and I click on an armagetronad:// link, which should be launched? Just changing the .protocol filename and and exec line won't solve that (unless that causes the browser to display a 'multiple applications registered for that protocol, which one should we pick?' selection box). I'd suggest to
a) shorten the protocol to arma://. We're rebranded to armacycles on paranoid distributions.
b) in addition to the arma:// protocol, which is handled by the last (highest, if possible) installed version, register arma03:// handled by the last installed version from the 0.3 series and arma031:// launching 0.3.1 specifically, multislot or not.
The added benefit of b) is that users of 0.3.1 will be told right away that clicking on an arma032:// is futile.