> right click on the start orb, select Properties, go to Customize and
scroll down to
> "Search Files" there's a "Search entire index" option
....to search the entire index rather than just this user's files, which was
the default option it seems.
Again, excellent info - thanks.
> In general however, regarding choices, I respectfully have to disagree.
>see Joel's http://joelonsoftware.com/uibook/cha...000000059.html
I appreciate the perspective, but with equal respect I shall continue to
disagree with both of you (I'm big on the philosophy of choice anyway at the
moment for reasons that don't belong here, so this is just a slice
Joel writes entertainingly and clearly and he makes his points well, but he
misses *the* point, as illustrated by the following two assertions that
feature prominently in his text:
1. "Asking the user to make a decision isn't in itself a bad thing"
2. "Every time you provide an option, you're asking the user to make a
decision."
*The* point arises from the fact that, unfortunately, neither of these
statements is necessarily true.
*Asking* a user to make a choice can indeed be a bad thing - the Help wizard
example is a classic example, a hangover from the days of smaller disks and
slower computers.
The problem however is not choice per se, but *requiring* a choice. It's the
interruption of the process by the very act of asking for a decision by the
user that's the issue.
It would have been better for the designer to provide a quick answer -
perhaps one that would take no longer than to exercise the choice actually
presented - based on the best choice that could be made at the design stage,
and in case the results were not helpful to *offer* the user the choice of
repeating the search more slowly (maximised index).
Point 2 is clearly related: the existence of options does not require the
user to make a choice unless you first decline to make a choice yourself.
It seems very simple: do the best you can as designers and developers, and
if the result is not what the user requires (which only they can decide at
the time) tell them that it can be done differently. An item in the search
results list labelled "Can't find what you are looking for?" would be a good
for-instance here: click it and I would be shown a list of the locations
indexed, a statement on which parts of the index were used in my failed
search, etc. etc. and controls to allow me to do it differently - this time
only or always.
Joel's other great example was the moved and resized taskbar. The problem
again is not that placement and size is an option, it is the absence of an
Undo operation for this sort of thing: the implementation *commits* the user
to a choice that they may have been unaware of making. A global undo list on
a per object basis would be extremely powerful and could resolve all such
issues.
Many people are still intimidated by IT; I encourage those who ask me for
advice to explore the choices available with the observation on applications
that "you can usually undo everything, and if you can't, a well-written
program should warn you before you commit yourself" - it's good application
design, why doesn't it apply to the OS? Undo that window move, undo that
taskbar resize, undo that toolbar rearrangement, un-map that drive, etc.
Windows Key + Z perhaps?
Such a change in philosophy would not be trivial, I concede, but I think the
rewards would outweigh the costs.
The problem is not choice, it's declining to take responsibility for the
choices that have to be made - which necessarily include "do nothing".
I am not upset that MS makes choices about how to do certain things - it has
to; I do get frustrated when it also chooses not to allow me to choose
otherwise (or even tell me that I can) - when and if I might wish reasonably
to do so. The situation we have been discussing would seem to be a case in
point.
Thanks Dave,
Julian