J
Just Fun
This may seem like a re-post of an old thread, but the old thread got long
and stale... so here goes again.
I am experiencing a problem understanding the deeper meaning of what a
"VIEW" is. In a varity of other software, a "VIEW" is a distinct way of
seeing the data. The data in one view is not obcured by what is visible (or
not visible) in any other view. The windows metaphore makes me think of my
house and the the VIEW I have of my back yard from either my bedroom window
or my kitchen window. The MS Project metaphore of a VIEW does not work this
way. It works as follows: If I let the blinds down half way on the bedroom
window, the the blinds are half way down on the kitchen window. Let me
explain...
MS Project allows the Colapsed and Expanded Outline structure to carry over
from VIEW A to a subsequent VIEW B. My problem is that if I go to a VIEW B
that does not show the outline structure because the summary tasks are
hidden, I am unable to use the "Show All" button because it is disabled.
This forces me to go back to any other view that does show the summary tasks
and "SHOW ALL" before I proceed to the view that doesn't show the summary
tasks. OR, I run the risk of not having all the detail tasks visible in VIEW
B because they are hidden in VIEW A.
Yes, this may be obcure. I can explain why I use this less-than-typical type
of view, but that fact will only obscure the real question as it did in the
previous thread. (I can correctly create the VIEW B so don't try to explain
how to do that.)
Why does MS Project allow the outline structure to carry over from VIEW A to
a subsequent VIEW B???
I hope I have phrased the question better this time than in the last thread.
I am having a hard time remembering to "SHOW ALL" before going to VIEW B.
The problem isn't so much how do I remember, but how will I ever teach my
assistant to "SHOW ALL" before changing VIEWS?
If the WINDOW and VIEW metaphore I am thinking of should not be applied to
this software, then what metaphore can I adopt that will allow me to
remember to "SHOW ALL" before going to VIEW B?
and stale... so here goes again.
I am experiencing a problem understanding the deeper meaning of what a
"VIEW" is. In a varity of other software, a "VIEW" is a distinct way of
seeing the data. The data in one view is not obcured by what is visible (or
not visible) in any other view. The windows metaphore makes me think of my
house and the the VIEW I have of my back yard from either my bedroom window
or my kitchen window. The MS Project metaphore of a VIEW does not work this
way. It works as follows: If I let the blinds down half way on the bedroom
window, the the blinds are half way down on the kitchen window. Let me
explain...
MS Project allows the Colapsed and Expanded Outline structure to carry over
from VIEW A to a subsequent VIEW B. My problem is that if I go to a VIEW B
that does not show the outline structure because the summary tasks are
hidden, I am unable to use the "Show All" button because it is disabled.
This forces me to go back to any other view that does show the summary tasks
and "SHOW ALL" before I proceed to the view that doesn't show the summary
tasks. OR, I run the risk of not having all the detail tasks visible in VIEW
B because they are hidden in VIEW A.
Yes, this may be obcure. I can explain why I use this less-than-typical type
of view, but that fact will only obscure the real question as it did in the
previous thread. (I can correctly create the VIEW B so don't try to explain
how to do that.)
Why does MS Project allow the outline structure to carry over from VIEW A to
a subsequent VIEW B???
I hope I have phrased the question better this time than in the last thread.
I am having a hard time remembering to "SHOW ALL" before going to VIEW B.
The problem isn't so much how do I remember, but how will I ever teach my
assistant to "SHOW ALL" before changing VIEWS?
If the WINDOW and VIEW metaphore I am thinking of should not be applied to
this software, then what metaphore can I adopt that will allow me to
remember to "SHOW ALL" before going to VIEW B?