I'm glad that worked!

I might be the second to last person to see Firefox's 3D page visualisation tool (our business users *really* proved their point--there's hearing your app goes 15 tables deep, and then there's seeing it does). I will be showing that tool around Monday like no one's business.

Strix, I know nothing about the Nook, but your friend may want to check into the availability of titles in Canada. I have a Kindle and I have found some books at the Kindle store unavailable for purchase because of licensing issues in Canada. I end up having to buy e-books from Kobo and breaking the DRM.

(Don't get me started on being unable to subscribe to the New Yorker.)

Will do. Thanks, Sue!

Hey, who knew that using System Restore on Windows 7 triggers a message saying "This copy of Windows is not genuine"?

Because now I do.

I am trying to work out best practices for Tasker, and it's lopsided enough that I'm just confused.

What I want to do, is to set up my phone so that if I place it face down at night, calls, texts, and voicemails don't make any perceptible sounds. Alarms, on the other hand, should be left alone.

It seems to be designed so that you have a context of 1 item (as in, either the time period or the phone orientation) that triggers certain results. The lopsidedness to which I refer means that I have to detect the face down status in the context, because I don't see how to pick that up later with vanilla Tasker.

So, basically--that part I can do, but I need to make sure that if the phone is face up, or if it's not in that time period, the volumes are unfucked with. Should I achieve this entirely with exit tasks? Or should some/any of that be in the elses of the if statements that parse the time period?

You can add multiple contexts, I'm pretty sure. Long press on the existing context and it should come up with a menu including "add."

I haven't set it back up since I got this (third!) replacement phone, but the way I had it was, if it's night, and plugged in, and at home, then shush everything except alarms and calls.

You can do two contexts at once. The task will only happen when both contexts occur simultaneously. Add one of the contexts, then add the action. Then go back to the main screen, click the profile to expand it, then press (don't long-press) on the context you already added. A menu pops up with the ability to add a new context.

So you would make a new profile with the context "face-down" and the task "make things different loudnesses" and then go back, press on the "face-down" context and add a new context for "nighttime".

It is a REALLY poorly designed interface element, but once you discover it, it's very useful!

Thanks! Since I had only done 1 context 1 task scenarios, I didn't realise that add wasn't for more tasks. There is an add for more tasks, right? Lemme go look...okay--I guess you would have to chain those together from inside one task?

Back to best practices--should I be recording the state of the device when the contexts are satisfied and restoring that state in the exit task? I can't decide if that's better than having a default context/profile the way Locale does.

Have any of you done anything including scenes?

I think Tasker stores the previous state and restores it automatically for state, time, and location contexts. In fact, I know it does - when I leave work, my phone goes back to whatever it was when I got to work (ring, vibrate, or silent).

ETA: I've never played with scenes. They seem possibly cool, but I haven't found a need yet.

My latest awesome tasker profile was for emergency calls - when my phone is on silent or vibrate or has a low volume, and the same person calls me twice within 10 minutes, the second call always rings. I did this because I was thinking about the fact that at night, my wife and I both completely silence our phone. I want to be reachable in emergencies.