What I understand this is done with CFBundleDocumentTypes property in the Info.plist. I made a quick test and got the ThinLinc client started when clicking a .tlclient file. Should be fairly simple to fix this issue.
Fixed. The tester should verify: * Documentation. * Use client config by double click on a .tlclient file. * Run the client via tlclient.cgi * Drag a .tlclient file to tlclient icon in Dock. Should work both before and after login to TL server. A bonus test would also be to launch a client config via Applescript.
*** Bug 3656 has been marked as a duplicate of this bug. ***
(In reply to comment #4) > *** Bug 3656 has been marked as a duplicate of this bug. *** Due to this change, make sure to test on multiple OS X versions.
When a ThinLinc Client is open and (partially) hidden behind other applications, opening a ThinLinc Client configuration file will first focus and raise the existing ThinLinc Client above other windows and then start a new client instance with the desired configuration. If the ThinLinc Client is on another desktop, OS X will move to that desktop and start the new client there instead of on the desktop you're currently at.
(In reply to comment #8) > When a ThinLinc Client is open and (partially) hidden behind other > applications, opening a ThinLinc Client configuration file will first focus and > raise the existing ThinLinc Client above other windows and then start a new > client instance with the desired configuration. > > If the ThinLinc Client is on another desktop, OS X will move to that desktop > and start the new client there instead of on the desktop you're currently at. Moved to Bug 5792.
(In reply to comment #10) > (In reply to comment #8) > > When a ThinLinc Client is open and (partially) hidden behind other > > applications, opening a ThinLinc Client configuration file will first focus and > > raise the existing ThinLinc Client above other windows and then start a new > > client instance with the desired configuration. > > > > If the ThinLinc Client is on another desktop, OS X will move to that desktop > > and start the new client there instead of on the desktop you're currently at. > > Moved to Bug 5792. Fine. > * Use client config by double click on a .tlclient file. Works fine. The "open" command also works fine. > * Run the client via tlclient.cgi Works with Firefox. Chrome saves the config file to disk by default, Safari hits bug 5707 and won't progress to the step where it downloads a configuration file. > * Drag a .tlclient file to tlclient icon in Dock. Should work both before and after login to TL server. Works both before and after login.
