and then restart Finder. When files or folders are selected in Finder, the Cut command will be active in the Edit menu, and present in the context menu.
Unfortunately, all it does today is a move-to-trash, and there's no ability to paste and have the file retrieved and put in the active Finder window or selected folder. So I don't know if this is a feature half-done, a feature dead-ended, or just a redundant command disabled because it would confuse people.
I kind of hope it's half-done and will be available in 10.5. The move-to-trash as an interim step appeals to me, because while the superficial user experience is consistent with any other cut operation, it's less inherently destructive.
[robg adds: I tested it and it works (half works?) as described. If you want to disable it again, just repeat the above command but replace the 1 with a 0. This will leave the value in your Finder's preferences, but it will be disabled. If that bothers you for some reason, you can delete it entirely by typing defaults delete com.apple.finder AllowCutForItems. If someone can test this on 10.3, please comment -- I don't have a bootable 10.3 partition at the moment.]
I had downloaded around 100 images from my camera using Image Capture and was wanting to view a quick, lightweight Finder slideshow. About two slides in, I realized that pictures are kind of boring without music. I guess I could've opened iTunes, but I didn't want to bother, so I opened a new Finder window in Column View. I navigated just a few simple steps into my iTunes music library, found a song, and started playing it using the Finder.
I was fairly sure it would stop as soon as I clicked the Finder window with all of my pictures in it, but it didn't. I thought, "Surely, when I start the slideshow it'll stop...", but it didn't, and I was amazed. An ultra light-weight slideshow with music. No iTunes or iPhoto needed.
[robg adds: This only works if you use a separate Finder window for playing back the music; the Finder will stop playing as soon as you navigate out of the window containing the playing song. And yea, this is fairly standard OS X behavior, but combining two Finder functions into a new one is sort of unique.]
The /Users/Shared folder is setup by default with permissions such that anyone may add items to it, for the perusal of others (and only the person who added the item, or an Admin, may remove it). However, the default permissions of items created by users is 'Read & Write' for the owner, but 'Read Only' for 'Group' and 'Everyone.' This means that added items will not be writable by others, unless permissions are manually changed first, because standard permissions normally only apply to the item itself and are not inherited. This often goes against the expectations of prospective users of the Shared folder.
Access control lists (ACL) can also be used to control access to files and folders, based on who is trying to access them, and what groups they belong to. ACL rules apparently trump standard permissions, and unlike standard permissions, ACL rules can be set to be inherited, even on local volumes. These previous hints (1, 2) describe how to set up ACLs in 10.4.
The only thing this hint adds to the above is making use of the 'Everyone' group (gid=12), for which "Group membership [is] calculated by [the] system." This makes it unnecessary to create and add users to a common group, like 'Staff,' for example.
I use the CD/DVD burning feature of the Finder a lot. Sometimes the verification fails, but I found that it is worth it to try the 'failed' CD/DVD anyway. When this problem occurs, the CD/DVD has mounted correctly quite often. Of course, I verify it to make sure the data I added is all there and is correct.
Sometimes, it seems that the verification routine is a bit overzealous...
[robg adds: I've seen this exact situation on my machine, though very rarely. I probably wouldn't trust a CD/DVD that failed the verification step for long-term archival use, but for a simple file transfer or similar, as long as you confirm everything works, it should be fine.]
After upgrading to a MacBook Pro, I discovered that my Calculate Size Contextual Menu item (which calculated total size of everything selected in finder) wasn't showing up, even though it was installed. After digging around for a few days, I made my first real AppleScript -- a substitute for the non-functional CM item.
I added the script to Butler's smart items with a trigger hotkey, and it works just fine. (I still haven't figured out why when added to OnMyCommand items it shows the alert more times than necessary). Hope this helps somebody.
[robg adds: This worked for me on my MacBook, also via a Butler Smart Item.]
I was attempting to make some new icons recently, and I wanted to start with an existing one, but modify it in a graphics program. I thought there was a way to copy the icon into the clipboard in previous versions of OS X, but each time I tried (Get Info, select icon, copy), I would only get a small version of the icon (about 32x32), and without transparency. But I wanted the larger version and with the transparency. I do realize there are some shareware utilities out there for this, but this should be do-able by the system itself. Turns out, it is.
So, here's the tip I found -- perhaps this has been reported before, but I couldn't find it.
Drag the item which has the icon you want to use into the Dock, then activate OS X's window capture screenshot feature -- press Shift-Command-4, then press the Space Bar. Now position the camera icon over the icon in your Dock and click. On your desktop will be a PNG file of the full-sized icon (128x128), with its transparency and nothing else. Easy!
[robg adds: I didn't realize the camera tool would see each Dock icon as a separate window; that's a pretty useful tip right there. When I tested this, though, I found that I only got good results when the icons in the Dock were as large as possible. Compare the two shots (of Butler's icon) seen at right. The leftmost one was taken with my Dock at its usual "smallish" setting. The one on the right was taken after removing all excess icons from the Dock, to make the Dock icons as large as possible. Although both captures are 128x128 (I shrunk them for display here), it seems OS X simply zooms the smaller capture up to the 128x128 size.]
I keep my Public Drop Box folder and a Samba share online all the time when I'm on the college network, and occasionally someone will drop files into either. Sometimes I won't notice for a while afterwards, which is annoying if it's big or I need to organise the folder better. So I wrote this Folder Action AppleScript that pops up a Growl notification whenever a file is added to a folder.
Just add the script as a Folder Action on a folder that you want monitored, and it'll pop up whenever something is added. If one file is added, the icon of that file pops up in the Growl notification; if more than one are added, then that folder's icon is displayed.
Over in the Macworld forums the other day, a reader lamented the switch in functionality of Command-N between OS 9 (new folder) and OS X (new Finder window).
It's been so many years since I switched over that I'd basically completely forgotten about that change -- and I make new windows more often than new folders, so I actually prefered the switch. Nonetheless, I was pretty sure we must have run a hint on how to swap the existing shortcut keys, which became possible with the release of 10.4. But all I could find when searching was this old hint I wrote about other ways to easily create new folders. It seems I never documented the method of switching the New Finder Window and New Folder keyboard shortcuts. So I did that yesterday in this Macworld tip writeup.
In a nutshell, you can make Command-N create new folders by first assigning the New Finder Window command to another key combo, then reassigning the New Folder command to Command-N (all done in the Keyboard Shortcuts tab of the Keyboard & Mouse System Preferences panel, of course). You can then switch New Finder Window over to Shift-Command-N, if you want to. If you need more detail, I went through the process step-by-step in the above-linked writeup.
But the more interesting version of this hint is the general one -- you can use this same technique to swap any pair of existing shortcuts. For instance, I swapped Command-I and Command-Option-I -- Command-I now gives me the Inspector window, and Command-Option-I brings up the Get Info window. I use the Inspector much more often than I use the Get Info window, and it's now but a simple Command-I away. To swap any existing combos, just do this, using my swap as the sample case:
In the Keyboard Shortcuts panel, reassign the command (Get Info) whose shortcut (Command-I) you'd like to use to something else (I used Command-Control-I).
In the Keyboard Shortcuts panel, assign the now-vacant combo (Command-I) to the command you'd like it to activate (the Inspector).
Relaunch the Finder to activate the first swaps.
Back in the Keyboard Shortcuts panel, change the temporarily-assigned command (Get Info, Control-Command-I) to the now-vacated shortcut from the other command (Inspector, Command-Option-I).
Relaunch the Finder again to activate the change.
The last two steps are optional -- you only need to do them if you want to have the same two shortcuts as you had before.
Having just bought a MacBookPro, I wanted a fast and easy way to see what apps I have that are universal, versus the ones that are PowerPC. This AppleScript will apply finder color labels to all of you applications. PowerPC apps are labeled grey, and Intel-only apps are labeled yellow. Universal Apps get no color label.
[robg adds:This earlier hint explained how to use Terminal to return a list of Intel-ready applications, and this hint used a different shell script to find all non-universal applications (with more nicely formatted output). This AppleScript, since it relies on the System Profiler report, will only work for applications located in the /Applications or ~/Applications folders, but it will traverse any subfolders of those directories as well.
If you want to remove the labels at some point, just modify the script so all instances of the set app_type... line read set app_type to 0, and then run it again. The script worked as described when I tested it on my Core Duo mini.]
I was replying to a question in the forums when I realized that this would make a great tip for the main site. Just like the original poster, I have a lot of desktop images, and sometimes I can't remember the name of the one that's currently displayed when I want to edit it (or trash it). So here's the AppleScript that I came up with to solve that problem...
tell application "System Events"
set my_desktop to value of (property list item "LastName" of ¬
property list item "1983938400" of property list item ¬
"Background" of property list file ¬
((path to preferences as Unicode text) & ¬
display dialog my_desktop
This script looks in the com.apple.desktop.plist file in your user's Library/Preferences folder for the name of the current desktop image. On my Mac running 10.4.5, there are actually several plist items under Background, each of which contain entries for desktop images that are not being displayed, so it took some poking around to find the correct path.
Apparently, there are some variations in the way that this .plist file looks. For this to work on your own system, you should open your own com.apple.desktop.plist file with the Property List Editor.app, and see where the value for your current desktop image is kept. Then change the value in the script (1983938400 in the above code) to match the value of the appropriate LastName entry for your current desktop image.
I have my Mac set to cycle through the images kept in a single "Screens," folder and I have double-checked that it will snag the name of the file again after the image has cycled a few times. This also works with two-monitor setups. I'll leave the modification for two monitors to your own ingenuity.