| By Charlie Arehart | Article Rating: |
|
| September 17, 2003 12:00 AM EDT | Reads: |
7,817 |
Studio has an interesting (and to some, annoying) mechanism for determining where to save newly created files. If you're not aware of this approach, you can be left feeling that Studio has made a mistake in deciding where to save a file—if you even notice it's not where you had expected.
The mechanism is controlled by the location pointed to in the "local files" tab in Studio's Resource Toolbar on the left of the screen. Whichever directory is highlighted in that tab will be where Studio saves newly created files. It's also where Studio starts looking when you ask it to open a file (using File Open).
What's most disconcerting to many, however, is that if one chooses to use File/Save As, to create a copy of a currently open file, it's normal in most editing tools for the default location for the newly copied file to be the same directory as the file from which the copy (save as) is being done. But Studio follows the same logic described above, even for a Save As.
The good news is that, as is almost always the case, Studio can be customized to work to your preferences. If you would like Save As to save into the current directory of the source file, de-select the option in Options>Settings>General for "Display Current Local Folder in File Dialogs". This is turned on by default (to create the behavior described above). You'd want it off, but keep in mind that it changes not just the Save As but all file dialogues.
It may seem that the wording is counter to what you'd expect, but when you realize that by "current local folder" they mean that selected in the "local files" tab rather than the "current local folder" of an opened file—as in a Save As situation—it makes some sense. Anyway, change it to suit your taste.
Charlie Arehart Education Director, Fig Leaf Software
Published September 17, 2003 Reads 7,817
Copyright © 2003 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
More Stories By Charlie Arehart
A veteran ColdFusion developer since 1997, Charlie Arehart is a long-time contributor to the community and a recognized Adobe Community Expert. He's a certified Advanced CF Developer and Instructor for CF 4/5/6/7 and served as tech editor of CFDJ until 2003. Now an independent contractor (carehart.org) living in Alpharetta, GA, Charlie provides high-level troubleshooting/tuning assistance and training/mentoring for CF teams. He helps run the Online ColdFusion Meetup (coldfusionmeetup.com, an online CF user group), is a contributor to the CF8 WACK books by Ben Forta, and is frequently invited to speak at developer conferences and user groups worldwide.
- Validating Input with Regular Expressions
- Getting Focus()ed and a Quick JavaScript Lesson
- Setting Up Your Development Server with ColdFusion 5, MX, and BlueDragon
- Toward Better Error Handling
- Monitoring Your ColdFusion Environment With the Free Log Parser Toolkit
- New Possibilities for Session/Client Variable Handling in CFMX
- Testing Existence in Arrays
- Making the Case for CFML on J2EE
- Exploring Amazon Web Services with ColdFusion MX
- Getting Focused - and a Quick JavaScript Lesson
- CFML on J2EE: Easy as 1-2-3
- Getting into HomeSite+



























