IDE tricks

From Free Pascal wiki
Revision as of 02:56, 1 October 2009 by Devilica (talk | contribs) ('New Unit/Form'의 설정 바꾸기(개인화))

Deutsch (de) English (en) français (fr) magyar (hu) 日本語 (ja) 한국어 (ko) русский (ru) slovenčina (sk)

파일 열기로 새 파일 생성하기

사용자는 보통 New File을 한후 저장합니다. 그러나 다음과 같이 할경우 한번에 파일 이름과 종류를 설정하여 새 파일을 생성 할 수도 있습니다. 파일 열기(Ctrl+o)를 실행하여 현재 디렉토리에 존재하지 않는 파일이름을 입력합니다. 예를들어 현재 디렉토리에 없는 파일 이름이라고 가정하고 'Unit1.pas'를 입력합니다. 이경우 IDE는 파일을 새로 생성 할 것인지 물어볼 것입니다. 생성하기를 선택할 경우 'Unit1.pas'라는 파일로 새파일이 생성되며 편집기에 열리게 됩니다.

'New Unit/Form'의 설정 바꾸기(개인화)

이 기능은 0.9.27 버젼 이후부터 가능합니다.

'New Unit'(New form) 버튼을 마우스 오른쪽 버튼으로 눌러서 새로 만드는 파일의 종류를 변경 할 수 있습니다. 또한 IDEIntf 이나 Project Templates Package를 통해 다른 종류의 파일을 추가 할 수도 있습니다.

IDE macros

IDE Macros in paths and filenames

Getting the compiler command line parameters created by the IDE

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.

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.

For packages this works the same.

This way, you can compile your (hopefully working and bugfree) code, outside of the lazarus IDE.

에디터 창을 한개 제외하고 모두 닫기

gtk 환경(리눅스, 맥OS X, FreeBSD에서 가능)의 소스 에디터 페이지의 경우 각 페이지 이름 오른쪽에 닫기 버튼이 있습니다. Ctrl키와 함께 닫기 버튼을 클릭하면 클릭한 페이지를 제외한 다른 모든 페이지가 닫히게 됩니다.

Component palette

Finding a component in the palette

You know the component name, or part of it, but you don't know in which page it was? This tool finds it: Right click on a component in the palette to open the popup menu. Choose 'Find component'. Type part of the name to filter the list.

Open the package of a component in the palette

Right click on the component to open the popup menu, then choose open package.

Find the source declaration of a component in the palette

Right click on the component to open the popup menu, then choose open unit.

My application freeze my linux desktop while debugging

X (your desktop) can freeze, when an application that grabbed the mouse is stopped by gdb (the debugger).

Using a second X session

You can start a second X by:

  X :1 &

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:

  gnome-session --display=:1 &

Using VNC

You can use vncserver/client by installing tightvncserver/realvncserver Start the server with:

  vncserver :1

AFAIK, a session is also started. You can connect to the vncserver with vncviewer.

Debug the application on the second server

In lazarus, in the run parameters for your project, check "use display" and enter

 :1

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).

Compiling the IDE fast

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.

  • Put the Lazarus sources on a fast harddisk. Not on a slow network filesystem.
  • Install only needed packages.
  • Set USESVN2REVISIONINC=0 to skip the update of the revision.inc.
  • Compile only parts. If the packager registration is recompiled, then all installed packages are recompiled too. If the IDEIntf is recompiled, then all installed design-time packages are recompiled.

DebugLn of the IDE or a LCL application

The IDE writes many useful hints via debugln. Under windows you can get them by starting lazarus with the command line parameter --debug-log=filename.txt. Under Linux/BSD/Mac OS X/Solaris: Just start lazarus in a terminal. This is a general LCL feature.

Finding the source file of an IDE window

  • Open the IDE window.
  • Press Ctrl+Shift+F1 to open the help editor.
  • Remember the window classname. Close the window.
  • Use Find In Files to find the source file of the class.

Object Inspector: Events: Frames: Jump to the source of an inherited event

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.

Events (Method properties) in the Object Inspector

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). Normally both are not nil. The IDE sets Data to a special key value for its internal lookup table and sets Code to nil. This means:

  • At runtime when the program loads the .lfm file the real method (Data+Code) is used
  • At designtime a method value can either be a real method (Data<>nil and Code<>nil) or a fake method (Data<>nil,Code=nil)
  • The compiler has for Delphi compatibility some specials about comparing method values.

Do not use: <Delphi> if OnMyEvent<>nil then OnMyEvent(...); // wrong, because it checks Data too </Delphi>

Because this checks both Data and Code and will execute the fake method, resulting in a jump to nil. This will only raise an exception, so it does not do much harm, but the IDE will show the user an error dialog. Use instead the Assigned function: <Delphi> if Assigned(OnMyEvent) then OnMyEvent(...); // correct, checking only Code </Delphi>

Do not use: <Delphi> if OnMyEvent=NewValue then exit; // wrong, because it compares only Code </Delphi>

Because this only compares the Code. Use instead <Delphi> if CompareMem(@FOnMyEvent,@NewValue,SizeOf(TMethod)) then exit; // correct, checking both Data and Code </Delphi>