IDE tricks: what changed
Revision 2 to 3. Removed lines have a minus sign; added lines have a plus sign.
| Old | New | Line | |
|---|---|---|---|
| 1 | - | ||
| 2 | - | ||
| 3 | - | ||
| 4 | - | ||
| 5 | - | ||
| 6 | - | ||
| 7 | - | ||
| 8 | - | ||
| 9 | - | ||
| 10 | - | ||
| 11 | - | ||
| 12 | - | ||
| 13 | - | ||
| 14 | - | ||
| 15 | - | ||
| 16 | - | ||
| 17 | - | ||
| 18 | - | ||
| 19 | - | ||
| 20 | - | ||
| 21 | - | ||
| 22 | - | ||
| 23 | - | ||
| 24 | 1 | ## Create a new file with Open file | |
| 25 | 2 | ||
| 26 | - | ||
| 3 | + | You can create a new file and save it, or you can create a new file with filename and file type in one step: Just open file (`Ctrl+o`) and select a nonexistent filename. For example: unit1.pas. The IDE will ask you if it should be created. | |
| 27 | 4 | ||
| 28 | 5 | ## Customize new unit / form | |
| 29 | 6 | ||
| 30 | - | ||
| 7 | + | Since 0.9.27 you can right click on the 'New unit' (New form) speedbutton and set the file type that should be created. You can register more file types via the IDEIntf or the project templates package. | |
| 31 | 8 | ||
| 32 | 9 | ## IDE macros | |
| 33 | 10 | ||
| 34 | 11 | [[IDE Macros in paths and filenames]] | |
| 35 | 12 | ||
| 36 | 13 | ## IDE directives | |
| 37 | 14 | ||
| 38 | 15 | [[IDE directives]] | |
| 39 | 16 | ||
| 40 | 17 | ## Getting the compiler command line parameters created by the IDE | |
| 41 | 18 | ||
| 42 | - | ||
| 19 | + | You can copy the parameters from Project -\> Compiler Options -\> Show Options. Here the paths are relative to the project directory. So in most cases you can copy them without adjusting. | |
| 43 | 20 | ||
| 44 | - | ||
| 21 | + | The parameters are also saved to the *.compiled file. For example if your project is called test1.lpi, then a test1.compiled is created. It is a simple text XML file, so you can just copy the options and adjust the paths to compile on another computer. The file is put into the same directory, where the executable is created. | |
| 45 | 22 | ||
| 46 | - | ||
| 23 | + | For packages this works the same. | |
| 47 | 24 | ||
| 48 | - | ||
| 25 | + | This way, you can compile your (hopefully working and bug free) code, outside of the Lazarus IDE. | |
| 49 | 26 | ||
| 50 | 27 | ## Closing all editor files except one | |
| 51 | 28 | ||
| 52 | - | ||
| 29 | + | Under GTK (available for Linux, macOS and FreeBSD) the source editor pages have a close button to the right of their page name. Press the `Ctrl` key while clicking on the button, closes all files except the clicked one. | |
| 53 | 30 | ||
| 54 | 31 | ## Component palette | |
| 55 | 32 | ||
| 56 | 33 | ### Finding a component in the palette | |
| 57 | 34 | ||
| 58 | - | ||
| 35 | + | You know the component name, or part of it, but you don't know on which page it was? This tool finds it: Right click on any component in the palette to open the popup menu. Select 'View all' from the menu; this will pop open a dialog(also you can achieve it by pressing `Ctrl+Alt+P`). Enter the (partial) component name in the 'Find' box to filter the list. | |
| 59 | 36 | ||
| 60 | 37 | ### Open the package of a component in the palette | |
| 61 | 38 | ||
| 62 | - | ||
| 39 | + | Right click on the component to open the popup menu, then choose open package. | |
| 63 | 40 | ||
| 64 | 41 | ### Find the source declaration of a component in the palette | |
| 65 | 42 | ||
| 66 | - | ||
| 43 | + | Right click on the component to open the popup menu, then choose open unit. | |
| 67 | 44 | ||
| 68 | 45 | ### My application freezes my Linux desktop while debugging | |
| 69 | 46 | ||
| 70 | - | ||
| 47 | + | X (your desktop) can freeze, when an application that grabbed the mouse is stopped by gdb (the debugger). | |
| 71 | 48 | ||
| 72 | 49 | ### Using a second X session | |
| 73 | 50 | ||
| 74 | - | ||
| 75 | - | ||
| 76 | - | ||
| 77 | - | ||
| 51 | + | You can start a second X by: | |
| 78 | 52 | ||
| 79 | - | ||
| 80 | - | ||
| 81 | - | ||
| 82 | - | ||
| 53 | + | ` X :1 &` | |
| 83 | 54 | ||
| 55 | + | with `Ctrl-Alt-F7` you switch to :0 and with `Ctrl-Alt-F8` you switch to :1 after that you can start a second gnome session by: | |
| 56 | + | ||
| 57 | + | ` gnome-session --display=:1 &` | |
| 58 | + | ||
| 84 | 59 | ### Using VNC | |
| 85 | 60 | ||
| 86 | - | ||
| 87 | - | ||
| 88 | - | ||
| 89 | - | ||
| 61 | + | You can use vncserver/client by installing tightvncserver or realvncserver. Start the server with: | |
| 90 | 62 | ||
| 91 | - | ||
| 63 | + | ` vncserver :1` | |
| 92 | 64 | ||
| 65 | + | AFAIK, a session is also started. You can connect to the vncserver with vncviewer. | |
| 66 | + | ||
| 93 | 67 | ### Debug the application on the second server | |
| 94 | 68 | ||
| 95 | - | ||
| 96 | - | ||
| 97 | - | ||
| 98 | - | ||
| 69 | + | In Lazarus, in the run parameters for your project, check "use display" and enter | |
| 99 | 70 | ||
| 100 | - | ||
| 71 | + | ` :1` | |
| 101 | 72 | ||
| 73 | + | Now your application will run on the second server, so when it is being debugged, only the second server will freeze (but that won't affect you since you are debugging on the first). | |
| 74 | + | ||
| 102 | 75 | ## Compiling the IDE fast | |
| 103 | 76 | ||
| 104 | - | ||
| 77 | + | Working on Lazarus itself means rebuilding the IDE many times. If you use the following tricks and have enough memory and a recent CPU, you should be able to recompile the IDE in a few seconds. | |
| 105 | 78 | ||
| 106 | - | ||
| 107 | - | ||
| 108 | - | ||
| 79 | + | - Put the Lazarus sources on a fast hard disk or solid state drive. Not on a slow network filesystem. | |
| 80 | + | - Install only needed packages. | |
| 81 | + | - Set USESVN2REVISIONINC=0 to skip the update of the revision.inc file. | |
| 109 | 82 | ||
| 110 | 83 | ## DebugLn of the IDE or a LCL application | |
| 111 | 84 | ||
| 112 | - | ||
| 85 | + | The IDE writes many useful hints via [[DebugLn]]. You can get these this way: | |
| 113 | 86 | ||
| 114 | - | ||
| 115 | - | ||
| 87 | + | - Windows: start Lazarus with the command line parameter *--debug-log=filename.txt*. | |
| 88 | + | - Linux/FreeBSD/macOS/Solaris: just start Lazarus in a terminal. | |
| 116 | 89 | ||
| 117 | - | ||
| 90 | + | This is a general LCL feature. | |
| 118 | 91 | ||
| 119 | 92 | ## Finding the source file of an IDE window | |
| 120 | 93 | ||
| 121 | - | ||
| 122 | - | ||
| 123 | - | ||
| 124 | - | ||
| 94 | + | - Open the IDE window. | |
| 95 | + | - Press `Ctrl+Shift+F1` to open the help editor. | |
| 96 | + | - Remember the window classname. Close the window. | |
| 97 | + | - Use [[IDE Window: Find in files|Find In Files]] to find the source file of the class. | |
| 125 | 98 | ||
| 126 | 99 | ## Opening a Terminal Windows from the IDE | |
| 127 | 100 | ||
| 128 | - | ||
| 129 | - | ||
| 130 | - | ||
| 131 | - | ||
| 132 | - | ||
| 133 | - | ||
| 134 | - | ||
| 101 | + | Its often handy to be able to open a terminal in your current project's working directory. Maybe to use a revision control system like git or svn or for a host of other possible reasons. Here is how to add a menu item to Lazarus's Tool's menu. Thanks to taazz and other contributors to the [forum thread](https://forum.lazarus.freepascal.org/index.php/topic,42151.msg294206.html#msg294206). | |
| 135 | 102 | ||
| 136 | - | ||
| 103 | + | - Click Tools, Configure External Tools | |
| 104 | + | - Click 'Add' to add a new menu item (under Tools). | |
| 105 | + | - Set Title to (eg) "Open a Terminal" | |
| 106 | + | - Set Program File Name to the command on your system that opens a terminal, some suggestions below. | |
| 107 | + | - Set Parameters to what ever your terminal expects on the command line to open a specific directory and the Lazarus var that points there, \$projPath(). | |
| 137 | 108 | ||
| 138 | - | ||
| 109 | + | Those last two vary quite a lot between systems, if you don't know the first, try looking at a list of running programs, the word 'terminal' is likely to feature. For the second, once you know the terminal's name, look up its man page or google. | |
| 139 | 110 | ||
| 140 | - | ||
| 141 | - | ||
| 142 | - | ||
| 143 | - | ||
| 144 | - | ||
| 145 | - | ||
| 146 | - | ||
| 147 | - | ||
| 148 | - | ||
| 149 | - | ||
| 111 | + | Some examples include - | |
| 150 | 112 | ||
| 151 | - | ||
| 113 | + | | O.S. | Program File Name | Parameters | | |
| 114 | + | |----|----|----| | |
| 115 | + | | Ubuntu Mate | mate-terminal\|\|--tab --working-directory=\$projPath() | | | |
| 116 | + | | xfce | exo-open\|\|--launch TerminalEmulator --working-directory \$ProjPath() | | | |
| 117 | + | | KDE | konsole\|\|--working-dir \$projPath() | | | |
| 118 | + | | GNOME | gnome-terminal\|\|--working-directory \$projPath() | | | |
| 119 | + | | Mac (see below) | /User/\$HOME/bin/ttab | cd \$projPath() | | |
| 120 | + | | Windows | cmd.exe | /k cd "\$ProjPath()" | | |
| 152 | 121 | ||
| 153 | - | ||
| 154 | - | ||
| 155 | - | ||
| 156 | - | ||
| 122 | + | <img src="ExtTool.PNG" title="IDE Ext Tool" width="250" alt="IDE Ext Tool" /> **On the Mac**, where everything is so much easier, all you have to do is: | |
| 157 | 123 | ||
| 158 | - | ||
| 159 | - | ||
| 124 | + | 1. Install <https://www.npmjs.com/package/ttab>, its only 665 lines, use the path you installed it to instead of the example shown in the table above. | |
| 125 | + | 2. Run it so you can tick its security to access the Accessibility feature. | |
| 126 | + | 3. Then set the Lazarus Tools settings as described. | |
| 127 | + | 4. Then, from within Lazarus, Tools-\>Open Terminal, then similar to 3) tick to allow Lazarus to access the Accessibility thingo. | |
| 160 | 128 | ||
| 161 | - | ||
| 129 | + | **On Windows**, its also necessary to tick the "Show Console" as shown in the image on the right: | |
| 162 | 130 | ||
| 163 | 131 | ## Object Inspector: Events: Frames: Jump to the source of an inherited event | |
| 164 | 132 | ||
| 165 | - | ||
| 133 | + | The [[IDE Window: Object Inspector|Object Inspector]] shows the events of inherited events as *ClassName.MethodName*. Double clicking will create a new event. `Ctrl+Mouse click` on the combobox will jump directly to the inherited method body, without creating a new method. | |
| 166 | 134 | ||
| 167 | 135 | ## Events (Method properties) in the Object Inspector | |
| 168 | 136 | ||
| 169 | - | ||
| 137 | + | Events (Method properties) are special properties, because they need as value a code address pointer, which does not exist at design time. That's why Lazarus uses the same trick as the Delphi IDE: Every method value can be type cast to **TMethod**, which contains *Data* (the object or class pointer) and the *Code* (the address pointer). At runtime both are set. But at design time the IDE sets Data to a special key value for its internal lookup table and sets Code to nil. This means: | |
| 170 | 138 | ||
| 171 | - | ||
| 172 | - | ||
| 173 | - | ||
| 174 | - | ||
| 139 | + | - At runtime when the program loads the .lfm file the real method (Data+Code) is used | |
| 140 | + | - At design time a method value can either be a real method (Data\<\>nil and Code\<\>nil) or a fake method (Data\<\>nil,Code=nil) | |
| 141 | + | - The compiler has for Delphi compatibility some specials about comparing method values. | |
| 142 | + | - The = and the \<\> operator only checks the Code, not the Data. | |
| 175 | 143 | ||
| 176 | - | ||
| 177 | - | ||
| 144 | + | Do not use: | |
| 145 | + | ||
| 146 | + | ``` pascal | |
| 178 | 147 | if OnMyEvent = NewValue then exit; // wrong, because it compares only Code | |
| 179 | 148 | ``` | |
| 180 | 149 | ||
| 181 | - | ||
| 182 | - | ||
| 150 | + | Because this only compares the Code. Use instead | |
| 151 | + | ||
| 152 | + | ``` pascal | |
| 183 | 153 | if CompareMem(@FOnMyEvent, @NewValue, SizeOf(TMethod)) then exit; // correct, checking both Data and Code | |
| 184 | 154 | ``` | |
| 185 | 155 | ||
| 186 | - | ||
| 187 | - | ||
| 156 | + | Here is an example where the = operator fails: | |
| 157 | + | ||
| 158 | + | ``` pascal | |
| 188 | 159 | type | |
| 189 | - | ||
| 190 | - | ||
| 191 | - | ||
| 192 | - | ||
| 193 | - | ||
| 194 | - | ||
| 195 | - | ||
| 196 | - | ||
| 197 | - | ||
| 198 | - | ||
| 199 | - | ||
| 200 | - | ||
| 201 | - | ||
| 202 | - | ||
| 203 | - | ||
| 204 | - | ||
| 205 | - | ||
| 206 | - | ||
| 207 | - | ||
| 208 | - | ||
| 209 | - | ||
| 210 | - | ||
| 211 | - | ||
| 160 | + | TMyClass = class | |
| 161 | + | private | |
| 162 | + | FOnClick: TNotifyEvent; | |
| 163 | + | procedure SetOnClick(Value: TNotifyEvent); | |
| 164 | + | public | |
| 165 | + | procedure Click(Sender: TObject); | |
| 166 | + | property OnClick: TNotifyEvent read FOnClick write SetOnClick; | |
| 167 | + | end; | |
| 168 | + | ||
| 169 | + | procedure TMyClass.SetOnClick(Value: TNotifyEvent); | |
| 170 | + | begin | |
| 171 | + | if Value = FOnClick then exit; // bug, checks only for Code, not for data | |
| 172 | + | FOnClick := Value; | |
| 173 | + | end; | |
| 174 | + | ||
| 175 | + | var | |
| 176 | + | a, b: TMyClass; | |
| 177 | + | begin | |
| 178 | + | a := TMyClass.Create; | |
| 179 | + | b := TMyClass.Create; | |
| 180 | + | a.OnClick := @a.Click; | |
| 181 | + | a.OnClick := @b.Click; // same code, but different data, a.OnClick still points to @a.Click; | |
| 182 | + | end. | |
| 212 | 183 | ``` | |
| 213 | 184 | ||
| 214 | 185 | --- | |
| 215 | - | ||
| 186 | + | *From the Free Pascal wiki, page "IDE tricks", as it stood on 2021-10-11 after a change by Kai Burghardt, out of the wiki's dump of 2024-05-26. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).* |