Download FilesInymCM for Mac - Contextual menu shows/hides file extensions in batch. MacUpdate Mac Contextual Menus Software Downloads

FilesInymCM is a contextual menu item for:

Showing/hiding/toggling the display of extensions of selected files in the Finder
Appending, prepending or renaming selected files in the Finder with the contents of the clipboard.
Changing the character case of the selected files in the Finder.

These operations can be applied to a folder's contents or the folder itself. Use the system preference pane to specify your preference.

FilesInymCM is part of the Limit Point Software "Utilities Bundle." Visit the Utilities home page at Utilities for a list of all the software available. Updates are always free, and new products always included.

Version 1.0.3:

The program now optionally recurses through subfolders if the option to process folders is on. This option is ON by default.
When prepending or appending the clipboard to the filename a space character is no longer inserted (if you want one just add it to the string you put on the clipboard.)

OTHER PEOPLE SUGGEST

FileUtilsCM X (votes: 2 )

Suggest something else:

JAZZJOHANNES Or just a switcher in Automator for the toolbar:

tell application "Finder"

set the selection_list to selection

if (count of selection_list) < 1 then

repeat with the_item in selection_list

set the extension_state to get extension hidden of the_item

if the extension_state is not true then

set the extension hidden of the_item to true

set the extension hidden of the_item to false

end tell
(Version 1.0.3)

BRIAN.MCGONIGLE What garbage! Just create two applescripts to do the same thing for free! Here's the code:

Filename: "Hide Selected File Extensions"

tell application "Finder"

set the selection_list to selection

if (count of selection_list) < 1 then

repeat with the_item in selection_list

set the extension_state to get extension hidden of the_item

if the extension_state is not true then

set the extension hidden of the_item to true

Filename: "Show Selected File Extensions"

tell application "Finder"

set the selection_list to selection

if (count of selection_list) < 1 then

repeat with the_item in selection_list

set the extension_state to get extension hidden of the_item

if the extension_state is true then

set the extension hidden of the_item to false

Just put both scripts in your "~/Library/Scripts/Applications/Finder" folder and enable the script menu. Done.
(Version 1.0)

Replies:

Feb 22 2008

JPPAGLIARO The AppleScript method is an alternative approach, I'll grant you that, and I am already familiar with that approach because I was using AppleScript myself.

However: it is much much much slower. In my tests the AppleScript approach takes from 2 to 4 times as long as my C program. This is significant when you are working with large collections of files. Why would you want to suffer people with the suggestion? (Not to mention the mechanics of getting it up and running!)

Second, I don't want the script menu enabled, and even if I did I don't necessarily want to move my mouse across my screen (which can be large) to get to it. I like contextual menus for the behavioral, as well as functional properties.

Also, this program is part of a large collection of programs I call the "Utilities Bundle" which are all activated when you make a variable amount payment. You can view these programs at the following location:

http://www.limit-point.com/Utilities.html

And finally, you'll notice I didn't give it an obvious name like HideShowExtensionCM. That's because I have other plans for it. It's only version 1, but it's still a good utility as is.
(Version 1.0)

Feb 22 2008

BRIAN.MCGONIGLE Want a context menu? Create and Automator plug-in.

1. Open Automator.

2. Create a one-step workflow using the "Run Applescript" action with the previous code I posted.

3. Click "Save as plugin..." from the File menu and save as a Finder plug-in.

4. Done.
(Version 1.0)

Feb 22 2008

JPPAGLIARO I think your ideas, from a programmatic viewpoint, are great, I really do. You seem to be a developer yourself. But, not everyone is, nor do they want to be or have time to be.

Automator is a wonder tool. But it, like AppleScript, is out of reach of some people who use a Mac because they don't have the time to construct Automator actions or workflows out of custom AppleScripts. It's not practical for them to do so.

Just like it isn't practical for me to starting farming and raising cattle because I want a "free" hamburger and salad with fries every now and then. :)
(Version 1.0)