VAOutline is so wonderful feature.I use it so frequently;
But the Node-level is sometimes unconsistent and really confuse me.
e.g. They are the some #ifndef-#endif block,But the first #ifndef-#endif is the some level but the second gif show the #endif is sub-level of #ifndef. (1)
(2)
I think is should be consistent and fullly reflect the code-level in source file.
How often do you see the #endif at the same level as the #ifndef line? At a guess, something is confusing VA Outline when this happens. Are you seeing problems with Alt-M in this file?
Can you post a code sample that shows this problem, or send me a sample file that does this for me to study? If so please submit the files via the form:
quote:How often do you see the #endif at the same level as the #ifndef line?
Te file is a h file.only the top-level #ifndef -#endif is at the same level.
the other is not.
(2) But especially when the #ifdef-#else-#endif block appear.
like:
I found #ifdef with #else at the same level,in the nature point view,I tend to find the #endif to enclosing the whole block.But on the contrary,#endif is sub-level included in #else clause .I think it may not intuitive for us.
Thank you for the file, the closing } at the end of the file is the trigger for this bug with the #endif. I have put in a bug report for this:
case=71463
VA Outline is showing you a tree view overview of the file. Remember this is also designed to help you drag and drop items to reorder the file. So showing the #ifdef and the #else at the same level makes sense, since they are both possible targets for drag and drop. The end of the block is shown by this node not having any more children in the tree.
A suggestion to VAOutline
Posted - Dec 27 2012 : 06:02:16 AM
