Home Download Screenshots Documentation FAQ Forum
# LiteEditor's FAQ ## General questions 1) Question: Why yet another IDE? Why not extend an existing IDEs? Answer: There are several answers to this question, I will point two: At first, LiteEditor was developed as a sample application to test and demonstrate CodeLite functionality, one thing lead to another and before I noticed, it evolved to become what it is today I am a programmer. I like writing code from scratch. No one likes to maintain someone else's code. 2) Question: How can I restore LiteEditor to its default layout setting? Answer: Close LiteEditor Open liteeditor.xml using ant text editor but no LiteEditor! (On Linux, it will be located under $HOME/.liteeditor/config, and on Windows, it will under C:\Program Files\LiteEditor\config) Search for xml entry named '<Perspective Name="Default"...>", delete it, save the file and restart LiteEditor 3) Question: I did what you suggested in the previous question, I found 'Perspective Name="Default"' deleted it, restarted LiteEditor - and the layout remains as before! Answer: You should do it from another editor and not from within LiteEditor, this is because, LiteEditor saves the settings before it exist, thus it will override the changes you have made 4) Question: I copied the liteeditor.xml file from Windows to Linux, and the layout looks funny ... Answer: See question 2 ## CodeLite related questions 5) Question: How does CodeLite works? Answer: See this document http://codelite.sourceforge.net/docs/CodeLite_Overview.html 6) Question: I wrote some code, added new classes, but the Outline view is not updated! Answer: The parsing thread, parses the files only at save time, so to keep your Outline view up-to-date, simply save it (Ctrl+S) 7) Question: I modified some files of my project in another editor, and now the outline view (or any other feature such as 'Find Implementation / Declaration') is not synchronized. It places the caret on a wrong line, or worse, some functions/classes are missing! Answer: Since you modified your sources from another editor, you probably added / removed some lines, so you need to update your database. This can be done by right clicking on the project (or even on the Workspace) icon and selecting the 'Retag option'. In general, this is a good advice whenever anything goes wrong with your CodeCompletion 8) Question: I have the following declaration: wxString str; str-> and guess what, it works!, doesnt CodeLite check whether the type is a pointer or an object? Answer: No 9) Question: I typed std:: and nothing is suggested, whats wrong? Answer: You need to point CodeLite to the database that contains the static symbols (AKA External database) - wx-stl.db . LiteEditor shifts with a ready to use database that contains the symbols for wxWidgets-2.8.4 and the STL. To select a database: Tags->Open External Database... and select the file you want to load. 10) Question: My external database symbol is huge, how can I improve the performance? Do you provide any caching mechanism? Answer: Yes. By default, LiteEditor reads from the external database directly from the disk, but if you are experiencing bad CodeCompletion response time, you could try to load the external database to memory by doing the following steps: Close the external database (Tags->Close External database) Enable the caching: Tags -> Options... -> CodeLite Tab, and check 'Load external database symbols to memory' Open the external database again ( Tags -> Open External database) 11) Question: Does CodeLite supports comment in tooltip? Answer: Yes it does. You will need to enable the following: Enable 'Parse Comments' field (Tags -> Options -> CodeLite tab) Enable 'Display Comments in tooltip' (Tags -> Options -> CodeLite tab) Note that at this point you wont see any code comments in the tooltip, since it does not exist in the database yet. You will need to retag your workspace or project (see question 7) 12) Question: My code contains many macros, which confuses the CodeCompletion library, what can I do to improve it? Answer: Since the symbol database is created by ctags, LiteEditor offers ctags options to do it, with some additional improvements, (hence ctags-le and not ctags) In the ctags tags of the Tags options' dialog, you can provide list of macros to be handled specially by CodeLite. The format it accepts, is as follows: MACRO=VALUE - in this format, whenever ctags-le will read the token MACRO is will be replaced by VALUE, a classic example for this is MinGW header files, which contains #define _GLIBCXX_STD std by adding _GLIBCXX_STD=std to the macro list, it tells CodeLite to replace _GLIBCXX_STD with std MACRO - a single macro tells CodeLite to simply ignore this token for more information about this field, can be found here (ctags -I option): http://ctags.sourceforge.net/ctags.html