Monthly Archives: January 2010
I was at a car show today and saw this woman wearing a t-shirt that said Cute Chick. I thought she was rather cute and when I saw her later sitting on a rail having a rest, asked if I could take her picture. She didn’t seem too keen at first but after considering for a few seconds, said "Why not".
This picture is #2 in my 100 strangers project. Find out more about the project and see pictures taken by other photographers at www.100Strangers.com.
I had to laugh this morning while walking from the car into Somerset Mall. I heard a crow having a good old squawk; looked around to locate it and you guessed it. It was sitting on the roof above Pick n Pay, right next to one of those shiny, whirly pyramid things that are apparently meant to keep birds away. So it seems they may not work quite as well as advertised.
I love the look this girl has in this photo. Makes me think that she has the potential to be a supermodel, if she was to be discovered by the right person.
I recently switched the default browser on all my machines from Firefox to Google Chrome. In general I’m loving Chrome but there is one behaviour that is driving me nuts. Scrolling with the mouse wheel takes keyboard focus away from the document.
Here’s what happens. I’ve just opened a page and can use the keyboard up/down and PgUp/PgDn keys to scroll it; no problem there. But if I then use the wheel on my mouse to scroll the page, it loses the keyboard focus and no longer responds to up/down, PgUp/PgDn, or in fact any other keyboard keys. I have to click on the page background to restore the keyboard focus. This is a minor inconvenience for scrolling but where it really drives me nuts is in Google Reader and Gmail where I use shortcuts a lot. Here I find that I scroll the article or e-mail I’m reading with the mouse wheel then get no response when I press j/k to move to the next or previous article or e-mail.
I would be eternally grateful if anyone can provide me with a solution to this problem.
UPDATE: Problem solved. There is apparently a bug in Chrome that cause some incompatibility with mouse wheel extenders such as KatMouse, which I use. Rob Boek has documented a workaround, where changing some settings in KatMouse solves the problem.