css copy paste problem in Dreamweaver CS4

[q]Originally posted by: Newsgroup User
Not to belabor the obvious, but it's important to realize that there are
many users who do not have these problems. Nobody posts to say "I have to
complain about not having this problem".[/q]

I'm sorry but that is entirely irrelevant here. DW is a commercial product
which is part of an expensive commercial suite of products which one can
reasonably expect to work as promoted. I am quick to sing a product's praises
at every opportunity where it might help sales, but that works both ways.

As I said, I develop apps myself so I understand very well the nature of
intermittent bugs, but I also understand the size of Adobe's resources and the
size of its turnover. I'm not impressed with a text editor that can't even cut
and paste properly!

Oh; and another thing: for every user who takes the trouble to post about a
problem on a forum somewhere in the big wide interweb, there are probably many
dozens more who just accept the bug not ever dreaming that they might be able
to influence a fix, or simply not being bothered to try and do something about
it.

New information about bug...

Although I work entirely in php these days, I just had cause to open an old
script with sections of php mixed with sections of HTML. When attempting to
copy a line or character of php code, DW selects the entire section of php code
but no more. At the same time, the arrows and vertical line in the side margin
show the entire (DW) selected block of code.

...so it's not just the whole script that gets selected!

I just wanted to let everyone know that I'm having this problem on my Mac OS X
10.5.6. Deleted config files, rebooted program, still have the same issue.

I will fill out the bug report form as well

Yes I realise that David. If you look at where I came in a few hours ago, I was
mearly letting people know that I had raised a support ticket for this issue.
Murray and yourself kept the thread going, to which I naturally responded - as
one does when conversing.

Thank you for emailing the product manager. I hope that he bumps this bug up
the order of priorities because I really don't want to have to start learning a
new app interface after all these years of using DW.

My current work-around (until Adobe pushes out a patch) is to quickly change
workspaces (saved pallet locations) to some random workspace and then back to
my workspace. This seems to reset some bit inside Dreamwaver getting the
code-selection working again TEMPORARILY (it will eventually creep back in).

I highly suspect the "Element View" (right click on a div in design view) has
something to do with it since it seems to want to select whole-blocks as though
the element views were set to "hidden."

Does anyone have a quicker work-around?

I haven't really found a workaround. One thing I did notice, though, is that if
I work with the code in the Code Inspector as opposed to the Code View it
doesn't happen. So, I'll now have to just use F10 a whole lot. Still not an
ideal workflow that's for sure. Hope they fix it soon!

Further info about the bug now that I am using DW4 more...

The bug only occurs when one first switches to a page/script, so if one is
working on a single script then it will only show itself until one carries out
an action that negates it e.g. when first selecting a script, place the cursor
anywhere among the code, press return, then delete. Once this is done the bug
remains hidden until another script is selected.

As mentioned above, the area that is selected by the bug is limited to the
current section of php (for example) if one is working on a script with both
php and html within.

So, if you work with single scripts and do not hand-code, you may not notice
the bug but if like me you are constantly cutting or copying and pasting code
from script to script, this is a serious impediment to work flow efficiency.

"David Powers" <david (AT) example (DOT) com> wrote

Roy Sinclair wrote:
Further info about the bug now that I am using DW4 more...

That's useful information. I'll pass it on to the QA team to see if it
helps them identify the cause.

Small nitpick, it's DW CS4. DW4 is an ancient version. Confusing name, I
know, but referring to the wrong one could give the incorrect impression
that you're talking about an ancient version that's no longer supported.

I didn't know Adobe was still supporting Dreamweaver CS4. That's good to
know :-)


--
Al Sparber - PVII
http://www.projectseven.com
Dreamweaver Menus | Galleries | Widgets
http://www.projectseven.com/go/apm
An Accessible & Elegant Accordion

Update: After restarting my Mac at the weekend and opening only DW CS4, Firefox
and Mail, the bug is no longer apparent. This means that it is probably being
triggered by another app, or a sub-app within CS4. This is good news (that it
might be traceable) so I will watch for it returning then note what I did and
will report back.