If you have, and click on, a similarly named file in the destination folder (at the point of saving) that will fill in much of the file-name already, just change the naming specifics to that of the new file.
I say sell the Mac and a buy a few PCs and some Shapeoko accessories with the money.
1 Like
Haha, yes, I used to work on a mac mini (still do for most things) so that is already in line with what a capable windows system would run…
I will say I really dislike file management in windows, the way you sort by date yet all subfolders aren’t sorted interspersed with the files, they are instead bunched at the bottom or top, not helpful. Or how pointer focus isn’t transferred from sidebar to main pane until I click on the pane background (instead of focus on hover). And scrolling with the scroll wheel of a mouse is either useable speed and spurty (not smooth but in chunks), or smoother but then too slow (by lowering chunk size)… Makes me realize how many things on a mac just work like you expect them to…
1 Like
Too old to switch over now Neil 
@ Stephen, not sure what you mean. Ever time you go to post process, its blank. You have to type new name with file ext. Before you could just use the program # 1001, and it would would safe as 1001.nc, not anymore:( Has to be typed in manually
2 Likes
@Steadiguy
Well that would be very different from before.
As far as I remember, when clicking post-process in F360 it would have the default of 1001 in the filename slot of that pop-up window, but when you clicked ‘Post’ it would pull up the ‘Save’ location folder (the folder on the drive where the file would be saved). From that window you could select other files that are named similarly and follow the process I described above…
There is a dropdown selection button towards the bottom of that ‘Save’ window, you can pull that down to say ‘All Files’ and you should see your other files in the same folder if they aren’t initially shown.
Personally I prefer the PC file management system to the one on the Mac (and we have eight Macs). As a matter of fact, I found a file manager for the Mac that approximates File Manager for the PC. 
the mac os got is start from unix and in unix there were no file extensions typically. so that is probably why fusion doesnt generate them
It’s a bit more complex than that.
The original Mac OS used file and creator types in the filesystem, stored in a “resource fork” and other aspects of the filesystem metadata rather than file extensions.
Steve Jobs left Apple and created the NeXT which used file extensions, including nifty concepts such as folders which would be treated as files based on their extension, so a .rtfd was a folder with an .rtf file and any associated graphics which seemed to just be a document in Workspace.app
When Apple’s Taligent venture w/ IBM crashed and burned, and Apple needed a new OS, after considering all the possible options, they bought NeXT to use OPENSTEP as the basis for their next generation OS. After a bit of adjustment to what was announced as Rhapsody based on market realities and licensing (in particular, Adobe refusing to honor an agreement to provide a free license for Display PostScript), Apple reworked NeXtstep to create the Carbon programming environment/API which made it simple to port existing Mac programs to what was announced as Mac OS X.
Mac OS X supports file extensions and file/creator types, and which a program prefers is typically based on the programming environment used for a given application.
Big Sur makes it just “macOS” and it may be that there was some change in how file extensions are handled in it which has caused this.
1 Like
Well, I guess I’m a mac guy at heart…
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.