I haven't originally put the steps to activate OCSmartHacks in Leopard intentionally here, since I have believed only users which understand Mac OS X should do that, and those would know what to do without being told. Nevertheless, there was too big demand, so well, here you are -- completely at your own responsibility:
First the standard ones which you have already done (if you have installed Hacks), but just for the record:
(i) mount the OCSmartHack.dmg package
(ii) launch the application
(iii) if needed, use the OCSmartHacks/Register menu item and enter the e-mail/registration code pair
(iv) click "Register" (which would, after entering a proper mail/code, be available)
(v) click Install (the "OCSmart Hacks installation changed" warning sheet would occur) and quit the application.
If in Tiger, you are done.
In Leopard though, we are all SOL since Apple has seriously crippled the Input Manager support; the steps to be taken to partially re-surrect it are (and I again stress out you should understand what you are doing before doing that!):
(iv) open a Terminal window
(v) perform the command
cd ~/Library/InputManagers
(vi) re-log in as root (sudo -s, enter administrator password)
(vii) perform the commands
chown -R root:admin OCSmartHacks
chmod -R a-w OCSmartHacks
mkdir /Library/InputManagers
mv OCSmartHacks /Library/InputManagers
The commands should have no visible result (nothing printed out to the Terminal window); if they do, there's a problem there. The only possible non-problematic result would be a warning that /Library/InputManagers already exist, if it happens to:
# mkdir /Library/InputManagers
mkdir: /Library/InputManagers: File exists
#
this would be all right. When done successfully, close the Terminal window.
From now on, Hacks will work in all newly launched Cocoa applications (try e.g. TextEdit), which allow Input Managers. Note that there are applications, which, by Apple design, do not allow Input Managers at all, and therefore Hacks can not work there. Namely, those are applications which
- are running with the root privilege
- are running with the wheel group privilege
- are not in the active workspace session
- have changed their user or group id
- are 64-bit.