IDE tricks/ru: what changed

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

Old	New		Line
1	1		# Создание нового файла с помощью \[функции\] "Открыть файл"
2	2
3	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		-	~~` X :1 &`~~
	53	+	```text
	54	+	X :1 &
	55	+	```
54	56
55	57		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	58
57		-	~~` gnome-session --display=:1 &`~~
	59	+	```text
	60	+	gnome-session --display=:1 &
	61	+	```
58	62
59	63		## Using VNC
60	64
61	65		You can use vncserver/client by installing tightvncserver/realvncserver Start the server with:
62	66
63		-	~~` vncserver :1`~~
	67	+	```text
	68	+	vncserver :1
	69	+	```
64	70
65	71		AFAIK, a session is also started. You can connect to the vncserver with vncviewer.
66	72
67	73		## Debug the application on the second server
68	74
69	75		In Lazarus, in the run parameters for your project, check "use display" and enter
70	76
71		-	~~` :1`~~
	77	+	```text
	78	+	:1
	79	+	```
72	80
73	81		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	82
75	83		# Compiling the IDE fast
76	84
77	85		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	86
79	87		- Put the Lazarus sources on a fast harddisk. Not on a slow network filesystem.
80	88		- Install only needed packages.
81	89		- Set USESVN2REVISIONINC=0 to skip the update of the revision.inc.
82	90
83	91		# DebugLn of the IDE or a LCL application
84	92
85	93		The IDE writes many useful hints via debugln. You can get these this way:
86	94
87	95		- Windows: start Lazarus with the command line parameter --debug-log=filename.txt.
88	96		- Linux/BSD/macOS/Solaris: just start Lazarus in a terminal.
89	97
90	98		This is a general LCL feature.
91	99
92	100		# Finding the source file of an IDE window
93	101
94	102		- Open the IDE window.
95	103		- Press Ctrl+Shift+F1 to open the help editor.
96	104		- Remember the window classname. Close the window.
97	105		- Use [[IDE Window: Find in files\|Find In Files]] to find the source file of the class.
98	106
99	107		# Opening a Terminal Windows from the IDE
100	108
101	109		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	110
103	111		- Click Tools, Configure External Tools
104	112		- Click 'Add' to add a new menu item (under Tools).
105	113		- Set Title to (eg) "Open a Terminal"
106	114		- Set Program File Name to the command on your system that opens a terminal, some suggestions below.
107	115		- 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	116
109	117		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	118
111	119		Some examples include -
112	120
113	121		\| O.S. \| Program File Name \| Parameters \|
114	122		\|----\|----\|----\|
115	123		\| Ubuntu Mate \| mate-terminal\\|\\|--tab --working-directory=\$projPath() \| \|
116	124		\| xfce \| exo-open\\|\\|--launch TerminalEmulator --working-directory \$ProjPath() \| \|
117	125		\| KDE \| konsole\\|\\|--working-dir \$projPath() \| \|
118	126		\| Mac (see below) \| /User/\$HOME/bin/ttab \| cd \$projPath() \|
119	127		\| Windows \| ? \| ? \|
120	128
121	129		On the Mac, where everything is so much easier, all you have to do is -
122	130
123	131		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	132		2. Run it so you can tick its security to access the Accessibility feature.
125	133		3. Then set the Lazarus Tools settings as described.
126	134		4. Then, from within Lazarus, Tools-\>Open Terminal, then similar to 3) tick to allow Lazarus to access the Accessibility thingo.
127	135
128	136		# Object Inspector: Events: Frames: Jump to the source of an inherited event
129	137
130	138		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	139
132	140		# Events (Method properties) in the Object Inspector
133	141
134	142		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	143
136	144		- At runtime when the program loads the .lfm file the real method (Data+Code) is used
137	145		- 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	146		- The compiler has for Delphi compatibility some specials about comparing method values.
139	147		- The = and the \<\> operator only checks the Code, not the Data.
140	148
141	149		Do not use:
142	150
143	151		``` pascal
144	152		if OnMyEvent = NewValue then exit; // wrong, because it compares only Code
145	153		```
146	154
147	155		Because this only compares the Code. Use instead
148	156
149	157		``` pascal
150	158		if CompareMem(@FOnMyEvent, @NewValue, SizeOf(TMethod)) then exit; // correct, checking both Data and Code
151	159		```
152	160
153	161		Here is an example when the = operator fails:
154	162
155	163		``` pascal
156	164		type
157	165		TMyClass = class
158	166		private
159	167		FOnClick: TNotifyEvent;
160	168		procedure SetOnClick(Value: TNotifyEvent);
161	169		public
162	170		procedure Click(Sender: TObject);
163	171		property OnClick: TNotifyEvent read FOnClick write SetOnClick;
164	172		end;
165	173
166	174		procedure TMyClass.SetOnClick(Value: TNotifyEvent);
167	175		begin
168	176		if Value = FOnClick then exit; // bug, checks only for Code, not for data
169	177		FOnClick := Value;
170	178		end;
171	179
172	180		var
173	181		a, b: TMyClass;
174	182		begin
175	183		a := TMyClass.Create;
176	184		b := TMyClass.Create;
177	185		a.OnClick := @a.Click;
178	186		a.OnClick := @b.Click; // same code, but different data, a.OnClick still points to @a.Click;
179	187		end.
180	188		```
181	189
182	190		---
183	191		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