Related files Issues

I've just installed CS4. The related files bar looks like a great addition...
but... I am having one issue. If I make changes to several files in the
related files bar and decide that I don't want to save one of the files, it
seems as if there is no way to not save the changes for an individual file. I
can either save the individual files that i want to keep and then close the tab
of the main file choosing 'no' when it asks me if I want to save the file whose
changes I want to discard. Yuck! Is there some way to just "close" the
changed file and essentially start over without having to save the other
related files?

Also related to this, I had to disable the "Reload Modified Files" preference
to "Never" because I use an external development environment for JavaScript.
If I choose "Prompt" (which is my preferred setting), I get an popup window
every(!) time I save the javascript file, which is not good. If I choose
"Always", then that deals with the javascript issue, but will overwrite any
external changes to all other file types, which defeats the purpose of having
that option in the first place.

Does anyone know if there is a way to address either or both of these issues?

It is looking as if I need to disable Related Files altogether, which I really
would rather not do, since it's implementation is definitely a step in the
right direction.

Thanks in Advance.

GarryCT,

If I make changes to several files in the related files bar
and decide that I don't want to save one of the files, it seems
as if there is no way to not save the changes for an individual file.

Give the file focus and use Undo.

HTH,
Randy

Thanks Randy,

Not what I was looking for, but it helps, although when you launch a browser,
it still wants to save it, which would overwrite the changes made in an
external editor. Ack!

I do wish the Adobe developers addressed this type of thing. Also it seems it
would be a simple thing to get rid of the asterisk after it is completely
undone, this is to mark the file as not modified. Even MS Visual Studio does
that.

Another weird thing that has migrated to CS4 from CS3 (and probably before) is
when you launch an unsaved html file. It warns you and presents 3 options.
Yes (action:Save and Launch), No (action: Don't save and launch). Those make
sense, but the third button - Cancel, does the same thing a 'No'. Seems that
should be Don't save and don't launch. Amazing they haven't addresssed this.
Like, duh! Drives me nuts!

If anyone can rationalize that... well... I'd be impressed

Do you have preview with temp files enabled?

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"GarryCT" <webforumsuser (AT) macromedia (DOT) com> wrote

Thanks Randy,

Not what I was looking for, but it helps, although when you launch a
browser,
it still wants to save it, which would overwrite the changes made in an
external editor. Ack!

I do wish the Adobe developers addressed this type of thing. Also it
seems it
would be a simple thing to get rid of the asterisk after it is completely
undone, this is to mark the file as not modified. Even MS Visual Studio
does
that.

Another weird thing that has migrated to CS4 from CS3 (and probably
before) is
when you launch an unsaved html file. It warns you and presents 3
options.
Yes (action:Save and Launch), No (action: Don't save and launch). Those
make
sense, but the third button - Cancel, does the same thing a 'No'. Seems
that
should be Don't save and don't launch. Amazing they haven't addresssed
this.
Like, duh! Drives me nuts!

If anyone can rationalize that... well... I'd be impressed

No, I don't use preview with temporary file. I'll have to try that. I tend to
do server stuff (php/xhr) on most of the pages, so I usually use a testing
server with IIS with the testinf folder pointing to the source folder.
I've assumed that preview with temporary files was used to launch a static,
web-serverless page.

I've assumed that preview with temporary files was used to launch a
static,
web-serverless page.

Nope. It's used to a) allow root relative links to work in preview, and b)
allow you to preview changes that have not been saved.


--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"GarryCT" <webforumsuser (AT) macromedia (DOT) com> wrote

No, I don't use preview with temporary file. I'll have to try that. I
tend to
do server stuff (php/xhr) on most of the pages, so I usually use a testing
server with IIS with the testinf folder pointing to the source folder.
I've assumed that preview with temporary files was used to launch a
static,
web-serverless page.

That was helpful, thanks. It still does force me to set "reload modified
files" to never, which is something I really like to set to "prompt". The
problem is that I edit all Javascript and PHP outside of Dreamweaver (by
setting the default editor in "File Types/Editors" & removing .js and .php in
the "Open in code view" area in Preferences. If prompt is set, it asks if I
want to save the changes in DW every time I make changes outside of it.

It seems as if they shouldn't include those in the related files, since (good
or bad) the user as specified that they wish to maintain these file types
external to DW. Hopefully Adobe development reads these forums once in a
while. This is definitely a defect.

Anyway, I've disabled related files even though the concept of having the HTML
file and it's CSS dependencies it a very nice thing to have. Hopefully they
address this issue as well as allowing you to reset a related file (i.e. reload
the original from disk) without having to jump through hoops by saving the ones
you want to keep individually.

Murray, Thanks for your help!