What’s the target audience for Dreamweaver MX?  Another frustrating thing is when you CTRL and ARROW to a <TAG>, the cursor does not stop at the <, but at the first letter after the bracket.  A MAJOR pain in the butt for highlighting chunks of text to delete.

 

I know this is not the forum, so I’ll stop the <rant>

 

Tom

 

 


From: Barney Boisvert [mailto:[EMAIL PROTECTED]
Sent: Monday, January 26, 2004 1:55 PM
To: [EMAIL PROTECTED]
Subject: RE: [CFCDev] Off topic: Dreamweaver MX 2004 (rant)

 

Nope to either.  The path one in particular is HUGE pain in the ass, but MM doesn't seem to think so.  It was that way in DWMX, and I know a lot of people complained, but it's still that way in DWMX'04.  Oh well.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Schreck, Thomas (PPC)
Sent: Monday, January 26, 2004 11:43 AM
To: [EMAIL PROTECTED]
Subject: [CFCDev] Off topic: Dreamweaver MX 2004 (rant)

I’m trying to like Dreamweaver, really.  I’m on my 3rd attempt to use it on a daily basis.  I must admit I’ve been very slow in letting go of Studio, but since change is the one constant in life…  Anyways, is there a way for Dreamweaver MX 2004 to display the full path of the file I have loaded in the IDE?  I’ve loaded a file from my local machine and the same one from production, however, in the title bar I get the folder/file name which happens to be the same for both files instead of the full path.

 

Also, I’ve noticed a behavior that’s irritating.  If I have a number of files open in Dreamweaver and happen to close one in the middle of the pack, the last file open receives focus.  In Studio, the file next to the one I close receives focus.  On the surface, this seems like a very minor detail, however, when working in an environment like fusebox where there’s a progression of files that are called to render a page, I open those files up in the progression they are called.  It’s somewhat irritating to have dreamweaver change focus.  Anyways, thanks for your help on an off topic.

 

 

Tom Schreck

 

Reply via email to