Hello Ollydbg.
Please excuse my late reply but the Friday afternoon and Saturday are my most busy times in the week.
First of all please excuse my bad orthography, especial if it is the core-reason, that I was not able to describe my point understandable. I know that Firefox normally offers spell checking since in my company it works and I know that this is a tool I have to use as often as possible. But for some reasons it is not working on my private Win 8 computer even it is activated. Furthermore I'm not able to use the Button Preview of this forum anymore, what I normally use to check how my post looks like. I think I have to look for some plug-in updates and to check the security adjustments. If somebody has tip for me, it will be great.
As attachment I added the combination of 2 screen shots that contains for one project the symbol browsers of the nightlies from September the 16th and October the 12th. As you can see in the older nightly I have to open the nesting namespace to see the nested namespace ( as I like), while in the newer nightly the nested namespaces are visible on the directly under the root node together with the nesting namespaces also (as I don't like). For me the hiding of nested namespaces is a very important key feature of the old symbol browser since it gave me the only possibility to define a kind of package structure, that was respected by the symbol browser. The idea is, once I look for a special source element, I normally know in what sub-package it is located. Thus I open the namespace path step by step until I reach the one that contains this element. Now the root-list of namespaces is full of namespaces I'm not interested in, if I want to navigate to a special one by opening the tree stepwise. This kind of visibility makes it very difficult to find that top-level namespace I have to open to first, while my navigation.
Furthermore if I click on a nested namespace shown on the same level as the nesting namespaces, C::B is not showing the location where the namespace is defined. C::B just opens the file and shows its first source lines. This was the case last year also.
I assume that one reason you have to get my point, is that my use of namespaces is more or less a misuse of them to establish a workaround. I use them to reduce the number of source elements shown in the symbol browser. Without doing this for me it is very difficult, to use the symbol browser for navigating through the code, since this means always a lot of scrolling. Unfortunately the possibility to reduce the number of source elements shown in the symbol browser is very limited. For example you have a context command to enable the showing of inherited members but there is no context command to disable the showing of those member elements on the top level of the symbol browser. In the past namespaces gave me the possibility to do so. Using namespaces for convincing the symbol browser to offer me a package-view is not really a good solution but until the nightly of September the 16th it worked. If you define the new behaviour as a feature you disabled this last possibility. Once there are some additional configuration possibilities to configure the symbol browser to offer as deeper tree-view and to disable the view of flat lists I would delete most of my namespaces. That's why I asked so often if it would be possible to offer a possibility to define virtual folders like in the project browser.
I already mentioned the limited possibility of reducing the since of top level lists in the symbol browser in the past. But until now nobody reacted. OK, I can understand, that this may mean a bigger change, what may be currently not possible for the C::B developers. You may also ask me why I would not do it by my self. To be honest I already thought about and did some investigations in your sources. But doing it by myself means to stop my own projects. Furthermore it means I have to learn how C::B intently works. I don't think, that you would accept a change to improve one part of C::B, if it influences other parts negatively, since the one who implemented the change was not aware of it. As a newbie in C::B development I would assume, that it would take at least one year to provide a solution that harmonise with the rest of the project and while this time I need frequently support from you also. But perhaps this is a thing we should discuss not in the nightly forum.
However, I hope that my attached picture is helpful to understand my doubts as well as my description of the goal I try to reach by using namespaces.
Best regards,
Eckard Klotz.
