Re: No contextual menu in Script Editor
Re: No contextual menu in Script Editor
- Subject: Re: No contextual menu in Script Editor
- From: Michael Grant <email@hidden>
- Date: Sun, 7 Mar 2004 13:21:06 -0600
On Mar 6, 2004, at 11:00 PM, Sander Tekelenburg wrote:
One account is not showing a contextual menu in SE 2.0 v43 (Mac OS X
10.3.2).
Just plain nothing happens when I Ctrl-click. No such problem on
another
account. I've deleted SE's prefs, its cache and disabled some possible
causes
for conflicts (third-party contextual menu modules) without any result.
Any idea what might be the cause?
Not really, but if all else fails, I use a diagnostic method similar to
extension conflict testing under the pre-X Mac OS. Availability of
labels and fast user switching make this method much more convenient
under 10.3 than under previous versions of OSX.
First make sure the root account is enabled and, if you're
security-conscious, unplug the computer from the Internet. Log out of
the account where the problem exists and log in as root. Create a temp
folder on the desktop or some other convenient location, and open two
Finder windows, showing the home directory of the problem account and
your temp folder. You might want to use TinkerTool or something similar
to enable viewing of invisible items. Start by dragging the entire
contents of the problem account's home directory to the temp folder.
Since the system will create new copies of certain folders when you log
back into the account, you may want to apply a label to everything at
this point to identify the original items.
Now log back into the problem account, leaving the root login active,
and check whether the problem still exists. If not, it was apparently
caused by something in the contents of the home folder. Log out and
return to the root account. Chances are the problem item is somewhere
in the Library directory, so I usually test it first--drag it back to
the problem account's home folder (replacing the new copy created when
you logged into the account), then log back into the account and see if
the problem exists. If it does, the cause of the problem is somewhere
in the Library folder. To be completely sure, you may want to log out
and return to root, remove the Library folder again and return
everything else, but it's probably not really necessary and will save
time to skip it. If the problem was not in Library, log out, return to
root, and test the Documents folder the same way. If the problem is not
in the Documents folder either, drag half of the remaining items back
into the home folder to test whether any of them are the source of the
problem. As you continue testing, you will probably find it helpful to
apply an "OK" label to items you've eliminated. If the problem appears
when you restore one group of items, apply a "suspect" label to those
items and drag half of them back to the temp folder to continue
narrowing down the search. Always be sure to log out of the problem
account before returning to root and dragging items back and forth.
Once you've identified the folder containing the source of the problem,
return to root, drag everything remaining in the temp folder back to
the account home folder, and make the problem folder the target of the
window that previously showed the home folder. Now repeat the
elimination process at the level of this folder, and continue drilling
down until you reach the individual file causing the problem.
Michael
--
English is essentially an imprecise dialect of Java, without the object
orientation.
- Julian Morrison
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.