Thanks very much for the response.

Boss says that CS5 has been ordered, so I'm feeling hopfull of the changes.

Thanks again,

Cy

I installed the trial of DW:CS5 yesterday, and the ability to tell a PHP file to open in "code view", yet allow you to switch from code to spilt/design mode DOES NOT WORK. If I choose to open a file in code all the time, then the split/design buttons are grayed out, and there is no way to even change to split/design under the view context menu.

I am using a Mac with Snow Leopard 10.6.4, if that means anything.

What the hell, DW developers?

Just because a person wants a file to open in code view every time they open it DOES NOT mean they never want the option to click on split/design in order to see the results. Besides, the preferrences ask to only OPEN the file in code view, not "edit only" in code view.

All I want is for my pages/scripts to ALWAYS open in code view, no matter what. Then I will decide when I want to go to design view. As it is, all my PHP files open in design view, no matter what mode they were in when I closed them. I rarely use split/design view, but there are occasions where I need to.

This is really getting rediculous in my opinion. Just because we want files to open in code view does not mean we don't want the other options at our finger tips.

If I am missing something here, please, somebody point it out.

Thanks,

Cy

I did as you suggested and this morning when I opened DW, then opened the PHP file I was last editing yesterday. The same thing happened. It opened the file in design view.

This particular file is a class and would never really be looked at in design. Nevertheless, though I NEVER put it in design, it opened it that way. So the argument that a file will open in the last view it was in is not valid here either.

I just don't get it. Everybody I have told about this agrees that it is down-right unreasonable to lock out the ability to chose Split or Design just because you told DW to always open PHP files on code view from the preferences. The idea wreaks of a bunch of programmers deciding on usability, which they evidently don't understand in their own little world. I've worked at a major software development company and I know far too well the mentality of programmers who develop far beyond my capabilities.

DW devs, please take note: Just because we want to force open a file in CODE view doesn't mean we don't want to switch to design view at some point for that same file. Forcing us to open files in design is like telling us you know better, and believe me, you don't.

It's really simple - Allow us to set a file type to open only in code view, but don't lock us out by disabling the buttons to switch to split or design if we want.

Cy

PS: A pic of what happens when I force .php files to open in code view:

As you can see, Split and Design are disabled. WHY force this?