IDE tricks/ru: what changed

Revision 1 to 2. Removed lines have a minus sign; added lines have a plus sign.

Old	New		Line
1	1		# Создание нового файла с помощью \[функции\] "Открыть файл"
2	2
3		-	Вы можете создать новый файл и сохранить его, или вы можете создать новый файл с именем файла и типом файла за один шаг: Просто откройте файл (<span class="kbd">ctrl</span>+<span class="kbd">O</span>) и выберите несуществующий файл. Например: unit1.pas. IDE спросит вас, нужно ли его создавать.
	3	+	Вы можете создать новый файл и сохранить его, или вы можете создать новый файл с именем файла и типом файла за один шаг: Просто откройте файл (`ctrl`+`O`) и выберите несуществующий файл. Например: unit1.pas. IDE спросит вас, нужно ли его создавать.
4	4
5	5		# Настройка нового модуля / формы
6	6
7	7		Начиная с версии 0.9.27 вы можете щелкнуть правой кнопкой мыши на кнопке быстрого запуска 'New unit' (New form) и установить тип файла, который должен быть создан. Вы можете зарегистрировать больше типов файлов через IDEIntf или пакет шаблонов проектов.
8	8
9	9		# Макросы IDE
10	10
11	11		[[IDE Macros in paths and filenames/ru\|Макросы IDE в путях и именах файлов]]
12	12
13	13		# Директивы IDE
14	14
15	15		[[IDE directives]]
16	16
17	17		# Получение параметров командной строки компилятора, созданных в среде IDE
18	18
19	19		Вы можете скопировать параметры из Project -\> Compiler Options -\> Show Options. Здесь пути относятся к каталогу проекта. Таким образом, в большинстве случаев вы можете скопировать их без настройки.
20	20
21	21		Параметры также сохраняются в файле *.compiled. Например, если ваш проект называется test1.lpi, то создается test1.compiled. Это простой текстовый XML-файл, поэтому вы можете просто скопировать параметры и настроить пути для компиляции на другом компьютере. Файл помещается в тот же каталог, где создается исполняемый файл.
22	22
23	23		Это работает так же и для пакетов.
24	24
25	25		Таким образом, вы можете скомпилировать свой (надеюсь, работающий и свободный от ошибок) код за пределами IDE lazarus.
26	26
27	27		# Closing all editor files except one
28	28
29	29		Under gtk (available for Linux, macOS and FreeBSD) the source editor pages have a close button right to their page name. Press the Ctrl key while clicking on the button, closes all files except the clicked one.
30	30
31	31		# Component palette
32	32
33	33		## Finding a component in the palette
34	34
35	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.
36	36
37	37		## Open the package of a component in the palette
38	38
39	39		Right click on the component to open the popup menu, then choose open package.
40	40
41	41		## Find the source declaration of a component in the palette
42	42
43	43		Right click on the component to open the popup menu, then choose open unit.
44	44
45	45		# My application freezes my linux desktop while debugging
46	46
47	47		X (your desktop) can freeze, when an application that grabbed the mouse is stopped by gdb (the debugger).
48	48
49	49		## Using a second X session
50	50
51	51		You can start a second X by:
52	52
53	53		` X :1 &`
54	54
55	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	56
57	57		` gnome-session --display=:1 &`
58	58
59	59		## Using VNC
60	60
61	61		You can use vncserver/client by installing tightvncserver/realvncserver Start the server with:
62	62
63	63		` vncserver :1`
64	64
65	65		AFAIK, a session is also started. You can connect to the vncserver with vncviewer.
66	66
67	67		## Debug the application on the second server
68	68
69	69		In Lazarus, in the run parameters for your project, check "use display" and enter
70	70
71	71		` :1`
72	72
73	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	74
75	75		# Compiling the IDE fast
76	76
77	77		Working on Lazarus itself needs 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.
78	78
79	79		- Put the Lazarus sources on a fast harddisk. Not on a slow network filesystem.
80	80		- Install only needed packages.
81	81		- Set USESVN2REVISIONINC=0 to skip the update of the revision.inc.
82	82
83	83		# DebugLn of the IDE or a LCL application
84	84
85	85		The IDE writes many useful hints via debugln. You can get these this way:
86	86
87	87		- Windows: start Lazarus with the command line parameter --debug-log=filename.txt.
88	88		- Linux/BSD/macOS/Solaris: just start Lazarus in a terminal.
89	89
90	90		This is a general LCL feature.
91	91
92	92		# Finding the source file of an IDE window
93	93
94	94		- Open the IDE window.
95	95		- Press Ctrl+Shift+F1 to open the help editor.
96	96		- Remember the window classname. Close the window.
97	97		- Use [[IDE Window: Find in files\|Find In Files]] to find the source file of the class.
98	98
99	99		# Opening a Terminal Windows from the IDE
100	100
101	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 <https://forum.lazarus.freepascal.org/index.php/topic,42151.msg294206.html#msg294206>
102	102
103	103		- Click Tools, Configure External Tools
104	104		- Click 'Add' to add a new menu item (under Tools).
105	105		- Set Title to (eg) "Open a Terminal"
106	106		- Set Program File Name to the command on your system that opens a terminal, some suggestions below.
107	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().
108	108
109	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.
110	110
111	111		Some examples include -
112	112
113	113		\| O.S. \| Program File Name \| Parameters \|
114	114		\|----\|----\|----\|
115	115		\| Ubuntu Mate \| mate-terminal\\|\\|--tab --working-directory=\$projPath() \| \|
116	116		\| xfce \| exo-open\\|\\|--launch TerminalEmulator --working-directory \$ProjPath() \| \|
117	117		\| KDE \| konsole\\|\\|--working-dir \$projPath() \| \|
118	118		\| Mac (see below) \| /User/\$HOME/bin/ttab \| cd \$projPath() \|
119	119		\| Windows \| ? \| ? \|
120	120
121	121		On the Mac, where everything is so much easier, all you have to do is -
122	122
123	123		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.
124	124		2. Run it so you can tick its security to access the Accessibility feature.
125	125		3. Then set the Lazarus Tools settings as described.
126	126		4. Then, from within Lazarus, Tools-\>Open Terminal, then similar to 3) tick to allow Lazarus to access the Accessibility thingo.
127	127
128	128		# Object Inspector: Events: Frames: Jump to the source of an inherited event
129	129
130	130		The 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.
131	131
132	132		# Events (Method properties) in the Object Inspector
133	133
134	134		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 casted to TMethod, which contains Data (the object or class pointer) and the Code (the address pointer). At runtime both are set. But at designtime the IDE sets Data to a special key value for its internal lookup table and sets Code to nil. This means:
135	135
136	136		- At runtime when the program loads the .lfm file the real method (Data+Code) is used
137	137		- At designtime a method value can either be a real method (Data\<\>nil and Code\<\>nil) or a fake method (Data\<\>nil,Code=nil)
138	138		- The compiler has for Delphi compatibility some specials about comparing method values.
139	139		- The = and the \<\> operator only checks the Code, not the Data.
140	140
141	141		Do not use:
142	142
143	143		``` pascal
144	144		if OnMyEvent = NewValue then exit; // wrong, because it compares only Code
145	145		```
146	146
147	147		Because this only compares the Code. Use instead
148	148
149	149		``` pascal
150	150		if CompareMem(@FOnMyEvent, @NewValue, SizeOf(TMethod)) then exit; // correct, checking both Data and Code
151	151		```
152	152
153	153		Here is an example when the = operator fails:
154	154
155	155		``` pascal
156	156		type
157	157		TMyClass = class
158	158		private
159	159		FOnClick: TNotifyEvent;
160	160		procedure SetOnClick(Value: TNotifyEvent);
161	161		public
162	162		procedure Click(Sender: TObject);
163	163		property OnClick: TNotifyEvent read FOnClick write SetOnClick;
164	164		end;
165	165
166	166		procedure TMyClass.SetOnClick(Value: TNotifyEvent);
167	167		begin
168	168		if Value = FOnClick then exit; // bug, checks only for Code, not for data
169	169		FOnClick := Value;
170	170		end;
171	171
172	172		var
173	173		a, b: TMyClass;
174	174		begin
175	175		a := TMyClass.Create;
176	176		b := TMyClass.Create;
177	177		a.OnClick := @a.Click;
178	178		a.OnClick := @b.Click; // same code, but different data, a.OnClick still points to @a.Click;
179	179		end.
180	180		```
181	181
182	182		---
183	183		From the Free Pascal wiki, page "IDE tricks/ru", as it stood on 2019-12-22 after a change by Trev, 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).

Back to history