Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

A script for Logitech's Control Center and user switching Apps
I know how completely annoying the Logitech drivers have to be for some when they use fast user switching. So here's my solution to the problem:

First make sure you are using WinSwitch to change users, as we need its functionality. Next, you'll need this AppleScript:
on pscheck()
  tell application "System Events"
    return (get name of every process)
  end tell
end pscheck
tell application "Finder"
  set e to my pscheck()
  if e contains "LCCDaemon" then
    tell application "LCCDaemon"
      quit
    end tell
  else
    tell application "LCCDaemon"
      activate
    end tell
  end if
end tell
Now save the AppleScript as an application, and drop it in both your ~/Library -> Application Support -> WinSwitch -> Switch-In Items and your ~/Library -> Application Support -> WinSwitch -> Switch-Out Items folders. Something named LCC Spawn should help you remember what this app does. Make sure you also copy this script to the same locations for each user you plan on letting use the Logitech drivers.

Now whenever you switch to the other user, the switch-out part will quit the running LCCDaemon in your account and the other user's switch-in will spawn the daemon and it will fully work for them. Vice versa if you switch back to your account. Of course, if anyone has a better solution, speak up!
    •    
  • Currently 3.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (2 votes cast)
 
[20,639 views]  

A script for Logitech's Control Center and user switching | 14 comments | Create New Account
Click here to return to the 'A script for Logitech's Control Center and user switching' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Why not the main Library/Appliation Support folder
Authored by: jecwobble on Nov 05, '04 12:31:49PM

Couldn't you just put it in the Library -> Application Support -> WinSwitch folder so that it's automatic for all users?



[ Reply to This | # ]
LCC is not a real startup daemon! No OWF/boot keys availible!
Authored by: zahadum on Nov 05, '04 07:08:30PM

I am not sure what the exact problem you guys are having with Fast User Switching using LCC on Panther - i dont have any freezes etc.

Please elaborate!

But here is my gripe (yeah Logitech has always been lame at driver support!) ...

LCC runs in user-space ... it dont think it is even a kext! ...

even if it is is kext, it lacks BASIC compatibility for using open firmware key commands at startup (eg single user, verbose console mode, saftey mode, designate CDROM as boot volume, select boot volume, presumably also Target mode) ....

at least on their entry-level 'Internet Explorer' model, this lack of OFW support is a shocking obstacle when trying to trouble-shoot (eg with NDD).

since this is a 'pre-driver' issue (the computer will _run_ with the logitech kb just fine; it just wont handle boot-specific modes), i suspect that maybe all of logitech hardware is a lost cause for the mac (in trems of hard-core, low-level compatibility) ...

more feedback about LCC issues would be appreciated!


---
mailto:osxinfo@yahoo.ca
mailto:interactix@email.com



[ Reply to This | # ]
LCC is not a real startup daemon! No OWF/boot keys availible!
Authored by: stephenj on Nov 05, '04 09:18:41PM

The problem with LCCDaemon and fast user switching is that once one instance of LCCDaemon is running all special keys on your keyboard will only apply to the first user running it...

Kinda a pain for example.
Second user hits the Media button, iTunes launches in the first account. So the second user launches iTunes manually and the first account has total control of the iPod plugged in and the second user is out of luck...

I think you can think of even more creative problems, like email programs or Instant Message programs...

And yes you are quite correct in that the keyboard doesn't send the proper keycodes to openfirmware like the option key doesn't even begin to work till the login screen is active...

Hence why my apple pro keyboard sits near my machine for the single user mode boots...

---
if by chance or circumstance...



[ Reply to This | # ]
LCC is not a real startup daemon! no OWF/boot keys availible! / do bluetooth kb cmnd key boot?
Authored by: zahadum on Nov 07, '04 02:01:15PM

thanx for clarifying the fast-user aspect of LCC ...

it seems insane to have to have a wired apple kb standing by for emergencies!

what about bluetooth? ... i wouldnt mind having having an apple keyboard around if it actually did something useful at runtime (like wireless) ...

do the the startup keys work with blurtooth (apple or otherwise)?

i know - slightly off-topic ;-)

---
mailto:osxinfo@yahoo.ca
mailto:interactix@email.com



[ Reply to This | # ]
LCC is not a real startup daemon! no OWF/boot keys availible! / do bluetooth kb cmnd key boot?
Authored by: stephenj on Nov 08, '04 07:09:03AM

< it seems insane to have to have a wired apple kb standing by for emergencies!
yeah but it's needed sadly...
< do the the startup keys work with blurtooth (apple or otherwise)?
apple is pretty much promised to work with openfirmware, but logitech i wouldn't recommend..
< i know - slightly off-topic ;-)
yes but this is a hints site...

---
if by chance or circumstance...



[ Reply to This | # ]
Why not the main Library/Appliation Support folder
Authored by: stephenj on Nov 05, '04 09:14:23PM

If you're talking about the main /Library folder no you cannot do that, according to WinSwitch's documentation you have to put in users Library/Application Support/WinSwitch folders...

---
if by chance or circumstance...



[ Reply to This | # ]
Why not the main Library/Appliation Support folder
Authored by: eno on Nov 06, '04 06:06:25PM
From the docs: "To try out the sample scripts, drag, copy or make an alias in the appropriate folder. Note that the sample scripts are installed globally (for all users) in the "/Library/" hierarchy, but that to use them you must install them locally (for the current user only) in the "~/Library/" hierarchy in your home folder." I guess because switch-in/switch-out actions are generally per-user preferences.

[ Reply to This | # ]
Simpler Script
Authored by: cfoster on Nov 05, '04 01:21:08PM

The following script is just a bit simpler. If LCCDaemon is not running, the first line will cause an exception and it will bounce to "on error", otherwise, it continues to execute and LCCDaemon is launched.

     	try
      	   tell application "Finder" to get name of process "LCCDaemon"
	   tell application "LCCDaemon" to quit
     	on error
	   tell application "LCCDaemon" to activate
     	end try


[ Reply to This | # ]
Simpler Script
Authored by: cfoster on Nov 05, '04 01:24:45PM

Whoops. I mean "it continues to execute and LCCDaemon is quit."

Oh, and a guess you don't really need the "name of..." part of the script. Just 'process "LCCDaemon" is fine.



[ Reply to This | # ]
Simpler Script
Authored by: stephenj on Nov 05, '04 09:27:23PM
The reason I used System Events as it runs separate from the Finder so if the Finder acts funky during fast user switch this script will work...

But yes your script does work as well...
Also one thing to recommend and I forgot to put in the original hint (also forgot to login before I posted it *slaps forehead*):

If you're using an older machine like me (400mhz G3) you might want to put a sleep statement before the activate part. (Do not use wait as it sucks CPU)

something like:
do shell script "sleep 2"

This will make sure the daemon is launched at the proper time aka after everything else and all keys will work.

I spent a little bit of time before figuring out that problem...
Hope my/your script helps everyone...

Once again just for a reminder of the older machine script:

on pscheck()
tell application "System Events"
return (get name of every process)
end tell
end pscheck

tell application "Finder"
set e to my pscheck()
if e contains "LCCDaemon" then
tell application "LCCDaemon"
quit
end tell
else
do shell script "sleep 3"
tell application "LCCDaemon"
activate
end tell
end if
end tell

---
if by chance or circumstance...

[ Reply to This | # ]

A script for Logitech's Control Center and user switching
Authored by: TvE on Nov 05, '04 05:21:37PM

I ave been so unhappy with LCC and the lack of support from Logitech that I have switched to USBOverdrive (for the mouse).

I am having problem with Fast User Switching (which can probably be solved with this hint) as well as I had problems when I am using a USB based KVM swith with several computers...


I still hav'nt to figure out if it's possible to get the LCCdaemon handle the keyboard while USBOverdrive handles the mouse... - I guess it's a "all or nothing"



[ Reply to This | # ]
A script for Logitech's Control Center and user switching
Authored by: stephenj on Nov 05, '04 09:36:52PM

Sadly yes it's an all or nothing as far as I know...
I've attempted the same myself and have had no luck...
I really like my logitech elite keyboard and mx1000 to work 100% so the Logitech drivers are the only way to go for both it appears...

Perhaps one day Logitech will hire some decent developers or get with the author of Usboverdrive and get some better drivers out there for us...

---
if by chance or circumstance...



[ Reply to This | # ]
A script for Logitech's Control Center and user switching
Authored by: DavidRavenMoon on Nov 08, '04 10:32:48AM

I have to second the recommendation for USBOverdrive. I've been using it from before I had a Logitech mouse, even before I was on OS X, and after I replaced my MSIntellimouse with a Logitech MX 700, I just kept using USBO. Never had an issue with it. Never even tried the LCC software!


---
--
G4/466, 1 GB, Mac OS X 10.3.5



[ Reply to This | # ]
Same problem exists with MacAllyHelper
Authored by: tonyboy on Nov 06, '04 05:06:32PM
I'm really glad to see this solution here.

The same problem exists with MacAlly's keyboards with multimedia keys (e.g.: the NetKey) the their "MacAllyHelper" driver.

I had come to much the same diagnosis and solution as above, and created the following AppleScript:


try
	do shell script "killall MacallyHelper"
	open application "MacallyHelper"
end try
The problem is, I hadn't found a way to run this automatically at startup, so when either I or my roommate would switch into our accounts, we'd have to manually run the script (placed in our docks for convenience).

The WinSwitch solution is interesting, but I prefer to use Apple's own FUS mechanisms -- especially if WinSwitch needs to be activated for each user account. It just seems kind of hacky...

Is there any way to change an application like MacAllyHelper into a more compatible form, like a kernel extention just by moving it to a different location and/or changing it's package information?

[ Reply to This | # ]