User forums > Nightly builds
The 06 August 2013 build (9246) is out.
Jenna:
--- Quote from: ollydbg on August 12, 2013, 03:51:58 am ---BTW: when I use CTRL+MOUSE_WHEEL to zoom the fonts, is there any way to "reset" the zoom value to the default value? I can't find a menu item...
--- End quote ---
"Edit -> Special commands -> Zoom -> Reset", I use "CTRL+0" (CTRL+zero") as shortcut on my system.
eckard_klotz:
Hello again.
In the meanwhile I implemented A workaround like this:
--- Quote ---#define USING_NAMESPACE using namespace
};}; USING_NAMESPACE CL_ACTION_GRAMM;
#undef USING_NAMESPACE
--- End quote ---
The result is that that the symbol-browser shows a reduced list again since the parser is not recognizing the using namespace lines any more.
But to be honest this is a workaround of a workaround and what happens the parser will start to solve the preprocessor directive ]#define USING_NAMESPACE using namespace
.
I think the real solution is that the symbol-browser provides a configuration to hide inherited members from higher tree-levels if they are shown as inherited members. Inherited members can already shown as sub-nodes so the only work is to erase them in the tree-levels above. I know there are also users which prefer flat lists and accept if this list are very long so it should be configurable. But for users like me one advantage of object orientated programming is to design hierarchies and in this case you expect this hibachi in a symbol-browser also.
Best Regards,
Eckard Klotz.
raynebc:
It took me a moment to realize why ALT+F wasn't bringing up the File menu like it always had done: The F hotkey is overloaded and is now assigned to the Fortran menu as well. Luckily this can be removed pretty easily by disabling the plugin, but it may be worth seeing if that menu can get another hotkey (I didn't check all plugins, but ALT+A and ALT+N don't seem to be tied to any of the default menus).
eckard_klotz:
Hello Everybody.
I assume that currently no urgent problems have to be discussed here so I hope I'm allowed to discuss an additional symbol-browser point. This discussion may result in a requirement but currently I don't know in which requirement.
As I wrote before I see a problem in the long lists you get in the symbol-browser. In a object orientated software-project it may be possible to use the language depending hierarchy definitions to move elements from the top-level to deeper levels like class inheritance or nested name-spaces.
But in more old fashioned software-projects with no object-hierarchies like in C and not Cpp this will not help. The user has to define the hierarchy some how else. My proposal is to give the user to define package-hierarchies inside the symbol-browser which represent a user-define tree whose nodes can be used to carry all symbols like the user wants.
* The user defines a package-structure that works like a folder-system and where a package may contain sub-packages and sub-sub-packages and sub-sub-sub... . This package-structure will be saved as independent xml-file or as part of the project-file. May be, it will good to have more than one independent package tree to represent different views.
* The activated package-structure will be displayed in the symbol-browser and can now be used to move symbols in. Once a symbol is moved in a package or its sub-package its id will be saved in the corresponding package xml-node. It may be possible to insert the symbol-id in more than one independent package-tree.
* The configuration of the symbol-browser allows the user to disable the display of moved symbols outside of their packages. Once the symbol-parser finds a changed symbol its id will be searched in the active package tree to prepare the display there and only there. Thus the user has to open the package to se the symbol and to reach its source but not shown symbols do not disturb the searching.
My idea is not to replace the current behaviour of the symbol-browser completely but to extend it. some more questions have to be discussed for example how to deal with change symbol-ids It may be useful to have a special tomb-package for symbols not found anymore or a delivery-package for new symbols. It may be good to add comment to every package and perhaps this may be used later to define a doxygen grouping definition. May be that this kind of browsing is to different compared with the currently used Symbol-browser what results in implementing a Package-browser parallel to the symbol-browser.
And may be you tell me that this already exists and I just was not able to activated it (Jens may remember the "disable the MouseSap-plugin" discussion we had in the last days, very embarrassing). So please help me to fill the vacuum between my ears.
Best Regards,
Eckard.
eckard_klotz:
Hello Everybody.
Now I have an total other question:
I know how to create in one project several targets.
I saw also, that it is possible to use the target-definition for creating an independent project.
But is it also supported to merge a project into an other for adding its targets (together with all associated configurations)?
In my example I have on the one side projects which contain application-targets (release and debug) and on the other side projects with test-targets (unit-tests). The independent test-projects are created by different colleges but once the tests are ready it is useful to have them in the application-project also. Here you are able to define a virtual target to compile and run altogether.
Currently we redefine all test-targets in the application-project by hand what may create more bugs. Thus a C::B function to copy a target from one project to the other may be very helpful.
Is there already something available?
Best regards,
Eckard.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version