I've checked the search, but the options suggested within the postings I found (under Tools/Options/Source Code Engeneering, or package context menu-->Set as Namespace Root/Clear Namespace Root) are already set to the correct values
Done that - to no avail!
Or are you saying to avoid generating Namespaces I need to set the packages to "Namespace Root"? Sounds a bit counter-intuitive to me if that is the meaning of this option!?
P.S.: tried it - setting the containing package to "Namespace Root" finally did the trick.
I still consider the naming of this option misleading. After thinking about it I found what was my problem: You are thinking of the package hierarchy as equivalent to a namespace hierarchy (which makes sense for Java, but not C++). I wasn't getting what you referred to as 'Root' and just read 'Namespace' - and was thinking to myself: "No, I don't want a namespace for this package - clear that option!"
Basically you are asking the designer to "set" an option if he wants
no additional qualifying and "clear" that option if he wants it. It's like asking a user whether he wants to really proceed with a process he started and have him press [Cancel] to avoid the aborting of the proces (which the software considers the sensible approach, even if it is not).
Please consider that in some languages package hierarchies are not equivalent to namespaces. There is no global setting to use or not use namespaces at all (or is there?), which means every sub-package explicitely requires the user to set that option, no matter the language, no matter how often he did it before for other languages!
Please change this option to something that is obvious and positive, such as "package is namespace" instead of "package is Namespace Root" ("Root"? what would it be "root" of??), and inherit that setting to subpackages!
