Quote:
|
I can't believe it's true of MOST of us, considering the awful mess that it can create.
|
You're not hearing me,,,, It does not cause such an awful mess, especially if you learn what causes unintended consequences and avoid those operations in Book View. You quickly learn the operations that cause unintended consequences and switch to Code View for a few seconds when doing those things. Yes - this is not a perfect situation, but you don't abandon a very valuable feature just because it has some flaws that can be worked around! You also have to occasionally switch to Code View and clean things up a bit.
The part you're not understanding is that IT'S WORTH IT. We are not complaining. Book View is still a valuable and needed productivity feature, even with its flaws. Yes, if it can be improved that would be great, but don't remove it!
Quote:
|
If the statement is true, I think it is a good reason to eliminate Book View on the ground that it tempts people to do what they ought not do.
|
Who are you to decide whether other users should or should use Book View?? I respect your use of the software for your application, why can't you respect our usage and not second guess what is good for other users???? If you don't want to use Book View, than don't use it. It seems strange that WE WHO DO USE IT are not complaining about it making an "awful mess", but you who do not want to use it are complaining about it!!!!
One more time - Book View is a valuable productivity feature for many users, regardless of its flaws. We know it's not perfect, but we use it every day because it helps us work more efficiently. If it doesn't help you work efficiently then don't use it.