MYZTIKJENZ  Demo tutorials are in the works... We create them as fast as we can but it does take time to produce a quality tutorial. Suggestions on what we should focus on (other than "everything")?  
(Version 4.0.3)

MYZTIKJENZ  Agreed, 4.0.3 is a bit unstable in Snow Leopard right now. We're working on it but to be honest, we were caught a little off-guard with the early release date. A compatible version is available on our site (http://startly.com/products/quickeys/mac/4/snowleopard/) but is still considered beta for the time being.

As for your comment about needing more advanced configuration and actions, please elaborate. QuicKeys is an extensive application and while we try to fill all the needs of our users, some people still use the application in ways we never intended. Feature requests submitted to our forums or to our Feedback form are always read and discussed.  
(Version 4.0.3)

MYZTIKJENZ  Ken, rich text formatting in abbreviations should be fixed in the next release.  
(Version 4.0)

MYZTIKJENZ  All pre-order keys were sent out prior to this past weekend. If you've not gotten yours, check your spam folder or contact our Sales department (sales@startly.com or 800-523-7638) and we'll be happy to get things sorted out.  
(Version 4.0)

MYZTIKJENZ  QuicKeys shouldn't even be in your process list if it's not running. Perhaps you mean the editor window isn't shown?

QuicKeys has to watch a lot of things and monitor several different areas of the operating system to do its job. Even when it seems like QuicKeys should be completely idle, it's still listening for events and waiting for triggers or abbreviations to resolve. There is going to be a certain level of overhead that we simply cannot remove... 1-7% CPU usage, fluctuating, is well within tolerances. A constant load over 10% would probably indicate a problem or an extreme use of triggers that are time-based.

If you think you have a legitimate issue, I encourage you to contact support and start a dialog with them. We'd be happy to take a deeper look into your situation and see if there's something we can do to help.  
(Version 4.0b6)

MYZTIKJENZ  Please quantify "too much processor power". QuicKeys idles between 0.1% to about 2.0% on a single CPU on my machine. Depending on how complicated your triggers are, you may see an increase in CPU usage but nothing that would cause an average user to say it's eating up too much CPU.

If you're seeing numbers a lot higher than this, please contact Technical Support and we'll figure out the issue.

-Jim  
(Version 4.0b6)

MYZTIKJENZ  Ah... you did exactly what my wife did when she installed TabStop. There's some room to improve the installation process, I think.

Don't worry about not seeing SIMBL folders... as long as TabStop is reporting that it loads, everything's working as expected.  
(Version 1.1.6)

MYZTIKJENZ  Try reinstalling both SIMBL and TabStop (make sure to do SIMBL first). I wonder if something got removed that shouldn't have.

When it's all said and done, you should have a TabStop.bundle file in /Library/Application Support/SIMBL/Plugins.

If you want, you can email me the last 100 or so lines of your console log. That might help me figure out what's going on here. My email address can be found on the main TabStop product page (click on the More Information link).  
(Version 1.1.6)

MYZTIKJENZ  /Applications/Utilities/Console or just type "Console" into Spotlight and select the result under Applications.

It'll bring up an application that will display the console log for you. Once that's up, restart Safari and you should see the log gets updated and scrolls for you.  
(Version 1.1.6)

MYZTIKJENZ  That makes more sense... if you were using Safari 1.x, the version of SIMBL required wouldn't have loaded and TabStop certainly wouldn't have worked either.

What does your console log say when you start up Safari? It should say something like "Safari [####] TabStop v1.1.6 loaded!" if TabStop indeed loads. If there are any errors, post them here and I'll see if there's something else going on.  
(Version 1.1.6)

MYZTIKJENZ  Are you saying a pre-1.1.6 version of TabStop was working with Safari 1.x? It never should have... I've always built TabStop to require at least Safari 2, bundle 412.

What version of OS and Safari are you running? And what version of TabStop did you get to run on Safari 1.x?  
(Version 1.1.6)

MYZTIKJENZ  I can come up with two reasons for that happening: you installed the old crappy ! version in your user's Application Support folder and the newer version in the main AppSupport folder and the two are competing with each other. Or you've not restarted Safari since installing.

Try this: Quit Safari, check to see if there is a TabStop.bundle in ~/Library/Application Support/SIMBL and delete it if there is, then re-run the 1.1.6 installer. Restart Safari and check the Console log to verify 1.1.6 did indeed start. If it did and you're still seeing the old icon, aliens have taken over and I suggest you run for the hills;)

Seriously, the icon is embedded in the bundle. The only way it could still be showing up is if an old bundle is being loaded somehow.  
(Version 1.1.6)

MYZTIKJENZ  v1.1.6 fixes this problem. Only wish I had gotten the bug report before I pushed 1.1.5 out the door. Oh well. Sorry for the inconvenience, folks.  
(Version 1.1.5)

MYZTIKJENZ  Hmm... it shouldn't be doing that (of course). I'll take a look into what's happening. Thanks for the report.  
(Version 1.1.5)

MYZTIKJENZ  Hmm... it shouldn't be doing that (of course). I'll take a look into what's happening. Thanks for the report.  
(Version 1.1.5)

MYZTIKJENZ  Yeah, this is a known problem. ForgetMetNot and TabStop both swizzle the same methods to watch for tab and window closures. Yanking those methods from ForgetMeNot causes it to go out of control (like you observed) and crash Safari.

I'm looking for a way to get TabStop to play nicely with existing plugins, but for now, the two shouldn't be used together.  
(Version 1.1)

MYZTIKJENZ  Not sure what happened there... but if it happens again, please let me know and I'll look into it.  
(Version 1.1)

MYZTIKJENZ  I agree. I was a bit over zealous with TabStop's behavior. The next release will correct this problem.  
(Version 1.0)

MYZTIKJENZ  HA!

You're totally right... An icon-maker I am not. I'll ditch this one and try something more clever. I know it's not required, but I like giving my little family o' apps some sort of face.  
(Version 1.0)

MYZTIKJENZ  Hey, constructive criticism! What a novel idea!

Both of your ideas are quite valid and honestly are ones that I hadn't thought of, especially creating a new FontBook collection. My intention was always to have the app work on copies of fonts made by the user, but giving the option to do that from inside the app would make it more obvious that's what people should do.

I'll definitely add your ideas to the list of things to do in the next release. Thanks for your ideas, porcustal.  
(Version 1.1)

MYZTIKJENZ  Don,

I can appreciate your sentiments that needlessly diddling with font internals can potentially be a Very Bad Thing. But this "utility" was born out of necessity.

The developer of the product I must use didn't have the foresight to realize that OpenType fonts can have (and usually do) different family and style nomenclature. Matching these up is the *only* way around this defect. I would have much rather the vendor fix the error, but that simply wasn't possible.

So I created this app so that others who may come across a similar situation won't have to suffer like I did to formulate a solution (or have nasty words with their vendors, like I did).

And as a side note, OTF Harmonizer is just a fancy-pants wrapper around tools that Apple freely provides that will modify/mangle OpenType fonts to your heart's delight. If you have a problem with a vendor allowing its users to potentially destroy fonts, you might want to complain to them too.

Jim  
(Version 1.0)