Sign in Join
Wiki copytemporary

GTK2 Interface: what changed

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

OldNewLine
1-*(GTK+ only)*
1+[![GTK logo.svg](https://upload.wikimedia.org/wikipedia/commons/thumb/7/71/GTK_logo.svg/50px-GTK_logo.svg.png)](</File:GTK_logo.svg>)
22
3+This article applies to [GTK+ Widgetsets](</Category:GTK_Widgetsets> "Category:GTK Widgetsets") only.
4+
5+See also: [[Multiplatform Programming Guide]]
6+
7+│ **English (en)** │
8+****
9+
10+## Contents
11+
12+ * 1 Introduction
13+ * 2 Other Interfaces
14+ * 2.1 Platform specific Tips
15+ * 2.2 Interface Development Articles
16+ * 3 Road map for the gtk2 interface
17+ * 4 Quick start guide for Linux, FreeBSD, etc
18+ * 4.1 Ubuntu Unity liboverlay
19+ * 4.2 Ubuntu Unity Menuproxy
20+ * 4.3 Raspberry Pi OS
21+ * 5 Using the GTK2 interface under macOS
22+ * 5.1 Installing X11
23+ * 5.2 Installing GTK2-Lazarus with fink
24+ * 5.3 Installing gtk using MacPorts
25+ * 5.4 Using the GTK2 libraries included with Gimp
26+ * 6 Using the Gtk2 interface under Microsoft Windows
27+ * 6.1 Getting the needed Gtk2 libraries
28+ * 6.2 Standalone Application under Windows
29+ * 6.3 Themes
30+ * 6.4 A sample project
31+ * 7 Current issues
32+ * 7.1 Editor Options allows to select incompatible fonts
33+ * 7.2 Moving with keys in the OI sometimes does not move the edit field
34+ * 7.3 Destroying handle during OnKeyDown gives AV
35+ * 7.4 Z-Order of controls
36+ * 7.5 Open Dialog Options
37+ * 7.6 TScrollBox and Scrolling problems
38+ * 7.7 Shortcut keys
39+ * 7.8 Up/Down key navigation between TEdits
40+ * 8 Done issues
41+ * 8.1 Done: ~~Synedit is very slow~~
42+ * 8.2 Done: ~~Small TButton does not center text~~
43+ * 8.3 Done: ~~TOpenPictureDialog does not update the preview~~
44+ * 8.4 Done: ~~Only the main form appears in the window list~~
45+ * 8.5 Done: ~~Slow and visible resizing when creating/resizing a dialog~~
46+ * 8.6 Done: ~~Selecting a TPage in the designer gives the wrong bounds rectangle~~
47+ * 8.7 Done: ~~Sometimes the hint window of the component palette is not resized~~
48+ * 8.8 Done: ~~gtk criticals in IDE codetools options dialog~~
49+ * 8.9 Done: System Colors
50+ * 9 Gtk1/Gtk2 separation roadmap
51+ * 10 Profiling
52+
353## Introduction
454
5-The gtk2 widgetset is stable and all components work. And it needs optimizations.
55+The gtk2 widgetset is stable and all components work. And it needs optimizations.
656
7-The documentation can be found [here](http://www.gtk.org/).
57+The documentation can be found [here](<http://www.gtk.org/>).
858
9-The minimum Gtk 2 version supported is Gtk 2.8
59+The minimum Gtk 2 version supported is Gtk 2.8
1060
61+## Other Interfaces
62+
63+ * [[Lazarus known issues \(things that will never be fixed\|Lazarus known issues (things that will never be fixed)]]> "Lazarus known issues \(things that will never be fixed\)") \- A list of interface compatibility issues
64+ * [[Win32/64 Interface]] \- The Windows API (formerly Win32 API) interface for Windows 95/98/Me/2000/XP/Vista/10, but not CE
65+ * [[Windows CE Interface]] \- For Pocket PC and Smartphones
66+ * [[Carbon Interface]] \- The Carbon 32 bit interface for macOS (deprecated; removed from macOS 10.15)
67+ * [[Cocoa Interface]] \- The Cocoa 64 bit interface for macOS
68+ * [[Qt Interface]] \- The Qt4 interface for Unixes, macOS, Windows, and Linux-based PDAs
69+ * [[Qt5 Interface]] \- The Qt5 interface for Unixes, macOS, Windows, and Linux-based PDAs
70+ * [[GTK1 Interface]] \- The gtk1 interface for Unixes, macOS (X11), Windows
71+ * GTK2 Interface \- The gtk2 interface for Unixes, macOS (X11), Windows
72+ * [[GTK3 Interface]] \- The gtk3 interface for Unixes, macOS (X11), Windows
73+ * [[fpGUI Interface]] \- Based on the fpGUI library, which is a cross-platform toolkit completely written in Object Pascal
74+ * [[Custom Drawn Interface]] \- A cross-platform LCL backend written completely in Object Pascal inside Lazarus. The Lazarus interface to Android.
75+
76+### Platform specific Tips
77+
78+ * [[Android Programming]] \- For Android smartphones and tablets
79+ * [[iPhone/iPod development]] \- About using Objective Pascal to develop iOS applications
80+ * [[FreeBSD Programming Tips]] \- FreeBSD programming tips
81+ * [[Linux Programming Tips]] \- How to execute particular programming tasks in Linux
82+ * [[macOS Programming Tips]] \- Lazarus tips, useful tools, Unix commands, and more...
83+ * [[WinCE Programming Tips]] \- Using the telephone API, sending SMSes, and more...
84+ * [[Windows Programming Tips]] \- Desktop Windows programming tips
85+
86+### Interface Development Articles
87+
88+ * [[Carbon interface internals]] \- If you want to help improving the Carbon interface
89+ * [[Windows CE Development Notes]] \- For Pocket PC and Smartphones
90+ * [[Adding a new interface]] \- How to add a new widget set interface
91+ * [[LCL Defines]] \- Choosing the right options to recompile LCL
92+ * [[LCL Internals]] \- Some info about the inner workings of the LCL
93+ * [[Cocoa Internals]] \- Some info about the inner workings of the Cocoa widgetset
94+
1195## Road map for the gtk2 interface
1296
1397Here: [[Roadmap|Roadmap#Widgetset_dependent_components]]
1498
1599## Quick start guide for Linux, FreeBSD, etc
16100
17-The first thing to do is to install the gtk2 libraries including the development packages. For example: linux/debian systems call them libgtk2.0-dev. There are complete installers for Windows [here](http://www.gtk.org/).
101+The first thing to do is to install the gtk2 libraries including the development packages. For example: linux/debian systems call them libgtk2.0-dev. There are complete installers for Windows [here](<http://www.gtk.org/>).
18102
19-The gtk2 is the default widgetset, so it should work out of the box.
103+The gtk2 is the default widgetset, so it should work out of the box.
20104
21-You can compile the LCL for gtk2. First open your normal compiled Lazarus. Then go on the menu "Tools" --\> "Configure Build Lazarus". Set LCL to "clean+build" and everything else to "None". Now select "gtk2" and click on the "Ok" button. Next go to the menu "Tools" --\> "Build Lazarus". Now the LCL is compiled for gtk2 too.
105+You can compile the LCL for gtk2. First open your normal compiled Lazarus. Then go on the menu "Tools" --> "Configure Build Lazarus". Set LCL to "clean+build" and everything else to "None". Now select "gtk2" and click on the "Ok" button. Next go to the menu "Tools" --> "Build Lazarus". Now the LCL is compiled for gtk2 too.
22106
23-To compile a project for gtk2 just select it as the target widgetset on the Compiler Options dialog.
107+To compile a project for gtk2 just select it as the target widgetset on the Compiler Options dialog.
24108
25109### Ubuntu Unity liboverlay
26110
27-The Ubuntu's Unity LIBOVERLAY override breaks the gtk_grab_add function, so mouse capturing does not work in synedit, treeview and many more LCL controls that descend from TCustomControl. That means dragging or selecting text with the mouse does not work.
28-
29-This is true for many applications, which is why liboverlay has an internal list to disable itself for many famous applications (e.g. gimp).
111+The Ubuntu's Unity LIBOVERLAY override breaks the gtk_grab_add function, so mouse capturing does not work in synedit, treeview and many more LCL controls that descend from TCustomControl. That means dragging or selecting text with the mouse does not work.
30112
31-That's why the gtk2 interface of the LCL disables liboverlay by default. You can enable it by compiling the LCL with -dEnableLibOverlay.
113+This is true for many applications, which is why liboverlay has an internal list to disable itself for many famous applications (e.g. gimp).
32114
33-If it is enabled: The LCL will write a warning with [[DebugLn]] if it spots liboverlay.
115+That's why the gtk2 interface of the LCL disables liboverlay by default. You can enable it by compiling the LCL with -dEnableLibOverlay.
34116
35-To disable liboverlay for a single application set the environment variable LIBOVERLAY_SCROLLBAR to '0' *before* starting the application. There is no way to disable liboverlay when the application is already running. For example:
117+If it is enabled: The LCL will write a warning with [[DebugLn]] if it spots liboverlay.
36118
37-`LIBOVERLAY_SCROLLBAR=0 ./lazarus`
119+To disable liboverlay for a single application set the environment variable LIBOVERLAY_SCROLLBAR to '0' *before* starting the application. There is no way to disable liboverlay when the application is already running. For example:
120+```
121+LIBOVERLAY_SCROLLBAR=0 ./lazarus
122+```
38123
39-You can disable it on a whole machine by uninstalling the package "liboverlay-scrollbar-0.2-0".
124+You can disable it on a whole machine by uninstalling the package "liboverlay-scrollbar-0.2-0".
40125
41-The IDE starter "startlazarus" sets this variable before starting the IDE (since 1.0). startlazarus is called for example when you use the desktop menu item.
126+The IDE starter "startlazarus" sets this variable before starting the IDE (since 1.0). startlazarus is called for example when you use the desktop menu item.
42127
43128### Ubuntu Unity Menuproxy
44129
45-In more recent Ubuntu versions, Ubuntu tries to create a "one menubar" look like macOS has, but this fails miserably with multi window programs like Lazarus. The main problem is not being able to access the menu without first selecting the main lazarus window. (the window that would hold the menubar).
46-
47-Turning off seems to be impossible without massive changes (probably that is because then everybody would turn such features off immediately).
130+In more recent Ubuntu versions, Ubuntu tries to create a "one menubar" look like macOS has, but this fails miserably with multi window programs like Lazarus. The main problem is not being able to access the menu without first selecting the main lazarus window. (the window that would hold the menubar).
48131
49-Turning off manually is possible through setting environment variable UBUNTU_MENUPROXY equal to 0 before starting.
132+Turning off seems to be impossible without massive changes (probably that is because then everybody would turn such features off immediately).
50133
51-UBUNTU_MENUPROXY=0 ./lazarus
134+Turning off manually is possible through setting environment variable UBUNTU_MENUPROXY equal to 0 before starting.
52135
53-or put it in a script like:
136+UBUNTU_MENUPROXY=0 ./lazarus
54137
55-`#!/bin/sh`\
56-`export UBUNTU_MENUPROXY=0`\
57-`./startlazarus`
138+or put it in a script like:
139+```
140+#!/bin/sh
141+ export UBUNTU_MENUPROXY=0
142+ ./startlazarus
143+```
58144
59145### Raspberry Pi OS
60146
61-Note: the following advice is proably not necessary if you have installed libgtk2.0-dev as mentioned further up this page
62-
63-Lazarus GTK2 cannot be compiled by default, because of missing symlinks for libraries. These symlinks are missed:
147+Note: the following advice is proably not necessary if you have installed libgtk2.0-dev as mentioned further up this page
64148
65-- libgdk-x11-2.0.so
66-- libgtk-x11-2.0.so
67-- libX11.so
68-- libgdk_pixbuf-2.0.so
69-- libglib-2.0
70-- libgthread-2.0.so
71-- libgmodule-2.0.so
72-- libpango-1.0.so
73-- libcairo.so
74-- libatk-1.0.so
149+Lazarus GTK2 cannot be compiled by default, because of missing symlinks for libraries. These symlinks are missed:
75150
76-The existing .so files are located in the "/usr/lib/aarch64-linux-gnu". For all mentioned files, you need to make symlinks like this:
151+ * libgdk-x11-2.0.so
152+ * libgtk-x11-2.0.so
153+ * libX11.so
154+ * libgdk_pixbuf-2.0.so
155+ * libglib-2.0
156+ * libgthread-2.0.so
157+ * libgmodule-2.0.so
158+ * libpango-1.0.so
159+ * libcairo.so
160+ * libatk-1.0.so
77161
78-`cd /usr/lib/aarch64-linux-gnu`\
79-`sudo ln -s libatk-1.0.so.0 libatk-1.0.so`
162+The existing .so files are located in the "/usr/lib/aarch64-linux-gnu". For all mentioned files, you need to make symlinks like this:
163+```
164+cd /usr/lib/aarch64-linux-gnu
165+ sudo ln -s libatk-1.0.so.0 libatk-1.0.so
166+```
80167
81168## Using the GTK2 interface under macOS
82169
83170### Installing X11
84171
85-If you want to use the gtk widgetset instead of the default Carbon widgetset, then make sure **X11** is installed. X11 is no longer included with Mac, but X11 server and client libraries are available from the [XQuartz project](https://www.xquartz.org/). The last XQuartz release was version 2.7.11 on 2016-10-29 for Snow Leopard 10.6.3 or later.
172+If you want to use the gtk widgetset instead of the default Carbon widgetset, then make sure **X11** is installed. X11 is no longer included with Mac, but X11 server and client libraries are available from the [XQuartz project](<https://www.xquartz.org/>). The last XQuartz release was version 2.7.11 on 2016-10-29 for Snow Leopard 10.6.3 or later.
86173
87-How do you know whether X11 is installed? Look in the /Applications/Utilities folder for an application named XQuartz.app. All further details are in /opt/X11/ (soft linked from /usr/X11).
174+How do you know whether X11 is installed? Look in the /Applications/Utilities folder for an application named XQuartz.app. All further details are in /opt/X11/ (soft linked from /usr/X11).
88175
89-**Tip** - Drag and drop X11 onto the dock so you'll have a one-click way of opening an X11 window.
176+**Tip** \- Drag and drop X11 onto the dock so you'll have a one-click way of opening an X11 window.
90177
91178### Installing GTK2-Lazarus with fink
92179
93-Install [Fink](http://www.finkproject.org/), the package manager for macOS. Install the GTK2 version of Lazarus with the following command:
94-
95-` fink install lazarus-gtk2`
180+Install [Fink](<http://www.finkproject.org/>), the package manager for macOS. Install the GTK2 version of Lazarus with the following command:
181+```
182+fink install lazarus-gtk2
183+```
96184
97-You will be asked to install a number of other packages. Simply answer yes. The installation takes quite a while. After it has finished, the GTK2 application can be started with a double click on /Applications/Fink/lazarus.
185+You will be asked to install a number of other packages. Simply answer yes. The installation takes quite a while. After it has finished, the GTK2 application can be started with a double click on /Applications/Fink/lazarus.
98186
99-Note: Projects using GTK2 can equally be created using the Aqua version of Lazarus, which is installed with "fink install lazarus-aqua".
187+Note: Projects using GTK2 can equally be created using the Aqua version of Lazarus, which is installed with "fink install lazarus-aqua".
100188
101189### Installing gtk using MacPorts
102190
103-Follow these steps to install the libraries using MacPorts. Install MacPorts from [**www.macports.org**](http://www.macports.org/). When MacPorts is set up, you need to install two library sets using the following commands:
104-
105-`sudo /opt/local/bin/port install gtk1`\
106-`sudo /opt/local/bin/port install gdk-pixbuf`
107-
108-Then make sure that Lazarus can find the library by using the command below before running Lazarus. Alternatively you can add this command to your bash startup script (`/etc/profile` or `~/.bash_profile`) before you start the shell to run Lazarus:
109-
110-`export DYLD_FALLBACK_LIBRARY_PATH="/opt/local/lib:$DYLD_FALLBACK_LIBRARY_PATH"`
191+Follow these steps to install the libraries using MacPorts. Install MacPorts from [**www.macports.org**](<http://www.macports.org/>). When MacPorts is set up, you need to install two library sets using the following commands:
192+```
193+sudo /opt/local/bin/port install gtk1
194+ sudo /opt/local/bin/port install gdk-pixbuf
195+```
111196
112-If this doesn't work, simply do
197+Then make sure that Lazarus can find the library by using the command below before running Lazarus. Alternatively you can add this command to your bash startup script (`/etc/profile` or `~/.bash_profile`) before you start the shell to run Lazarus:
198+```
199+export DYLD_FALLBACK_LIBRARY_PATH="/opt/local/lib:$DYLD_FALLBACK_LIBRARY_PATH"
200+```
113201
114-`sudo ln -s /opt/local /sw`
202+If this doesn't work, simply do
203+```
204+sudo ln -s /opt/local /sw
205+```
115206
116207### Using the GTK2 libraries included with Gimp
117208
118-Now that the Cocoa widgetset is the default for Lazarus on macOS, there probably isn't much need for developing or distributing GTK2-based apps on macOS. However, you might want to test your apps with the GTK2 widgetset to see how well the graphical portion will work under Linux, where GTK2 is likely to be the default. You can also compile Lazarus itself against the GTK2 widgetset if you're curious about how Lazarus looks with GTK2.
119-
120-An easy way to obtain recent GTK2 libraries is to download and install Gimp from <http://www.gimp.org/macintosh/>. Gimp is not only a useful image editor in its own right, but it also installs GTK2 version **2.16.6** libraries that you can link your apps against.
209+Now that the Cocoa widgetset is the default for Lazarus on macOS, there probably isn't much need for developing or distributing GTK2-based apps on macOS. However, you might want to test your apps with the GTK2 widgetset to see how well the graphical portion will work under Linux, where GTK2 is likely to be the default. You can also compile Lazarus itself against the GTK2 widgetset if you're curious about how Lazarus looks with GTK2.
121210
122-Copy and paste the files given below into a text editor and save them as **gimplib.cfg** and **glaunch.sh**. File gimplib.cfg tells FPC how to link against the GTK2 libraries; file glaunch.sh initializes GTK2 and starts a GTK2-compiled executable specified on the command line.
211+An easy way to obtain recent GTK2 libraries is to download and install Gimp from <http://www.gimp.org/macintosh/>. Gimp is not only a useful image editor in its own right, but it also installs GTK2 version **2.16.6** libraries that you can link your apps against.
123212
124-To compile an app against the GTK2 widgetset and link it with the Gimp GTK2 libraries, do the following:
213+Copy and paste the files given below into a text editor and save them as **gimplib.cfg** and **glaunch.sh**. File gimplib.cfg tells FPC how to link against the GTK2 libraries; file glaunch.sh initializes GTK2 and starts a GTK2-compiled executable specified on the command line.
125214
126-- In the Lazarus Compiler Options dialog, on the Other tab, check Use Additional Compiler Config File and enter the path to gimplib.cfg in the text box (for example, ~/tools/scripts/gimplib.cfg).
127-- In the Lazarus Compiler Options dialog, on the Paths tab, select GTK2 as the LCL Widget Type.
128-- Choose Run \| Build.
215+To compile an app against the GTK2 widgetset and link it with the Gimp GTK2 libraries, do the following:
129216
130-To run a GTK2-compiled executable, open an X11 window, change to your app's folder, and enter the following (which assumes glaunch.sh is in ~/tools/scripts):
217+ * In the Lazarus Compiler Options dialog, on the Other tab, check Use Additional Compiler Config File and enter the path to gimplib.cfg in the text box (for example, ~/tools/scripts/gimplib.cfg).
218+ * In the Lazarus Compiler Options dialog, on the Paths tab, select GTK2 as the LCL Widget Type.
219+ * Choose Run | Build.
131220
132-- ~/tools/scripts/glaunch.sh myexec
221+To run a GTK2-compiled executable, open an X11 window, change to your app's folder, and enter the following (which assumes glaunch.sh is in ~/tools/scripts):
133222
134-To compile Lazarus itself, do the following:
223+ * ~/tools/scripts/glaunch.sh myexec
135224
136-- Open an X11 window and change to your Lazarus source folder.
137-- Make a copy of your Carbon-based Lazarus, in case something goes wrong (cp -p lazarus lazarus-carb).
138-- make clean all LCL_PLATFORM=gtk2 FPC=fpc OPT="@~/tools/scripts/gimplib.cfg -dHasX"
225+To compile Lazarus itself, do the following:
139226
140-This will rebuild lazarus, lazbuild and startlazarus. You'll probably want to rename your lazarus executables:
227+ * Open an X11 window and change to your Lazarus source folder.
228+ * Make a copy of your Carbon-based Lazarus, in case something goes wrong (cp -p lazarus lazarus-carb).
229+ * make clean all LCL_PLATFORM=gtk2 FPC=fpc OPT="@~/tools/scripts/gimplib.cfg -dHasX"
141230
142-- mv lazarus lazarus-gtk2
143-- mv lazarus-carb lazarus
231+This will rebuild lazarus, lazbuild and startlazarus. You'll probably want to rename your lazarus executables:
144232
145-To run the GTK2-compiled Lazarus:
233+ * mv lazarus lazarus-gtk2
234+ * mv lazarus-carb lazarus
146235
147-- ~/tools/scripts/glaunch.sh lazarus-gtk2
236+To run the GTK2-compiled Lazarus:
148237
149-Here is the gimplib.cfg config file. Note that this assumes you installed Gimp in your Applications folder.
238+ * ~/tools/scripts/glaunch.sh lazarus-gtk2
150239
151- -k'-headerpad_max_install_names'
240+Here is the gimplib.cfg config file. Note that this assumes you installed Gimp in your Applications folder.
241+```
242+-k'-headerpad_max_install_names'
152243 -k'-L/usr/lib'
153244 -k'-L/usr/X11R6/lib'
154245 -k'-L/Applications/Gimp.app/Contents/Resources/lib'
155246 -k'-lgthread-2.0'
156-
247+
157248 -k'-dylib_file'
158249 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libpangoft2-1.0.0.dylib:/Applications/Gimp.app/Contents/Resources/lib/libpangoft2-1.0.0.dylib'
159250 -k'-dylib_file'
160251 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libz.1.dylib:/Applications/Gimp.app/Contents/Resources/lib/libz.1.dylib'
161252 -k'-dylib_file'
162253 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libpangocairo-1.0.0.dylib:/Applications/Gimp.app/Contents/Resources/lib/libpangocairo-1.0.0.dylib'
163254 -k'-dylib_file'
164255 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libgmodule-2.0.0.dylib:/Applications/Gimp.app/Contents/Resources/lib/libgmodule-2.0.0.dylib'
165256 -k'-dylib_file'
166257 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libintl.8.dylib:/Applications/Gimp.app/Contents/Resources/lib/libintl.8.dylib'
167258 -k'-dylib_file'
168259 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libiconv.2.dylib:/Applications/Gimp.app/Contents/Resources/lib/libiconv.2.dylib'
169260 -k'-dylib_file'
170261 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libcairo.2.dylib:/Applications/Gimp.app/Contents/Resources/lib/libcairo.2.dylib'
171262 -k'-dylib_file'
172263 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libfreetype.6.dylib:/Applications/Gimp.app/Contents/Resources/lib/libfreetype.6.dylib'
173264 -k'-dylib_file'
174265 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libfontconfig.1.dylib:/Applications/Gimp.app/Contents/Resources/lib/libfontconfig.1.dylib'
175266 -k'-dylib_file'
176267 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libexpat.1.dylib:/Applications/Gimp.app/Contents/Resources/lib/libexpat.1.dylib'
177268 -k'-dylib_file'
178269 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libXrender.1.dylib:/Applications/Gimp.app/Contents/Resources/lib/libXrender.1.dylib'
179270 -k'-dylib_file'
180271 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libtiff.3.dylib:/Applications/Gimp.app/Contents/Resources/lib/libtiff.3.dylib'
181272 -k'-dylib_file'
182273 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libjpeg.62.dylib:/Applications/Gimp.app/Contents/Resources/lib/libjpeg.62.dylib'
183274 -k'-dylib_file'
184275 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libpng12.0.dylib:/Applications/Gimp.app/Contents/Resources/lib/libpng12.0.dylib'
185276 -k'-dylib_file'
186277 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libXinerama.1.dylib:/Applications/Gimp.app/Contents/Resources/lib/libXinerama.1.dylib'
187278 -k'-dylib_file'
188279 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libpixman-1.0.dylib:/Applications/Gimp.app/Contents/Resources/lib/libpixman-1.0.dylib'
189280 -k'-dylib_file'
190281 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libgio-2.0.0.dylib:/Applications/Gimp.app/Contents/Resources/lib/libgio-2.0.0.dylib'
191282 -k'-dylib_file'
192283 -k'/tmp/skl/Gimp.app/Contents/Resources/lib/libjasper.1.dylib:/Applications/Gimp.app/Contents/Resources/lib/libjasper.1.dylib'
193-
194-Here is the glaunch.sh script file:
195-
196- #!/bin/sh
284+```
197285
286+Here is the glaunch.sh script file:
287+```
288+#!/bin/sh
289+
198290 TMP="/tmp/$UID/TemporaryItems"
199291 GRES="Gimp.app/Contents/Resources"
200292 GIMP="/Applications/$GRES"
201- if ! [ -e "$GIMP" ]
293+ if ! [ -e "$GIMP" ]
202294 then
203295 GIMP="~/Desktop/$GRES"
204- if ! [ -e "$GIMP" ]
296+ if ! [ -e "$GIMP" ]
205297 then
206298 GIMP="~/$GRES"
207- if ! [ -e "$GIMP" ]
299+ if ! [ -e "$GIMP" ]
208300 then
209301 GIMP="~/Applications/$GRES"
210- if ! [ -e "$GIMP" ]
302+ if ! [ -e "$GIMP" ]
211303 then
212304 GIMP=""
213305 fi
214306 fi
215307 fi
216308 fi
217-
309+
218310 if [ "$GIMP" = "" ]
219311 then
220312 echo "Can't locate Gimp"
221313 else
222314 export "DYLD_FORCE_FLAT_NAMESPACE=1"
223315 export "DYLD_INSERT_LIBRARIES=/usr/lib/libiconv.dylib"
224316 export "DYLD_LIBRARY_PATH=/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources:$GIMP/lib"
225317 export "PANGO_RC_FILE=$TMP/pangorc"
226318 export "FONTCONFIG_PATH=$GIMP/etc/fonts"
227319 export "GTK_IM_MODULE_FILE=$TMP/gtk.immodules"
228320 export "GDK_PIXBUF_MODULE_FILE=$TMP/gdk-pixbuf.loaders"
229321 export "GTK_DATA_PREFIX=$GIMP"
230322 export "GTK_EXE_PREFIX=$GIMP"
231-
323+
232324 mkdir -p "$TMP"
233325 sed 's|/tmp/skl/Gimp.app/Contents/Resources/etc/pango|'"$TMP|g" "$GIMP/etc/pango/pangorc" > "$TMP/pangorc"
234326 sed 's|/tmp/skl/Gimp.app/Contents/Resources|'"$GIMP|g" "$GIMP/etc/pango/pango.modules" > "$TMP/pango.modules"
235327 cp -f "$GIMP/etc/pango/pangox.aliases" "$TMP"
236328 sed 's|/tmp/skl/Gimp.app/Contents/Resources|'"$GIMP|g" "$GIMP/etc/gtk-2.0/gtk.immodules" > "$TMP/gtk.immodules"
237329 sed 's|/tmp/skl/Gimp.app/Contents/Resources|'"$GIMP|g" "$GIMP/etc/gtk-2.0/gdk-pixbuf.loaders" > "$TMP/gdk-pixbuf.loaders"
238-
330+
239331 ./$1
240332 fi
333+```
241334
242335## Using the Gtk2 interface under Microsoft Windows
243336
244337### Getting the needed Gtk2 libraries
245338
246-Using the Gtk2 libraries from gtk.org:
339+Using the Gtk2 libraries from gtk.org:
247340
248-- <http://www.gtk.org/download>
341+ * <http://www.gtk.org/download>
249342
250-or using the GTK-Runtime project:
343+or using the GTK-Runtime project:
251344
252-- <https://gtk-win.sourceforge.io>
345+ * <https://gtk-win.sourceforge.io>
253346
254-or using the Gtk2 libraries provided by Gimp:
347+or using the Gtk2 libraries provided by Gimp:
255348
256-- <http://gimp-win.sourceforge.net/stable.html>
349+ * <http://gimp-win.sourceforge.net/stable.html>
257350
258351### Standalone Application under Windows
259352
260-You may prefer a standalone application to avoid versions conflicts. All needed libraries are in the packages mentioned above. They should be placed in the same folder of your executable. You will need all these libraries:
353+You may prefer a standalone application to avoid versions conflicts. All needed libraries are in the packages mentioned above. They should be placed in the same folder of your executable. You will need all these libraries:
261354
262-- libcairo-2.dll
263-- libglib-2.0-0.dll
264-- libpangocairo-1.0-0.dll
265-- libpng12.dll
266-- libgdk-win32-2.0-0.dll
267-- libgmodule-2.0-0.dll
268-- libgtk-win32-2.0-0.dll
269-- libatk-1.0-0.dll
270-- libgdk_pixbuf-2.0-0.dll
271-- libgobject-2.0-0.dll
272-- libpango-1.0-0.dll
273-- libpangowin32-1.0-0.dll
274-- libgio-2.0-0.dll
275-- zlib1.dll
355+ * libcairo-2.dll
356+ * libglib-2.0-0.dll
357+ * libpangocairo-1.0-0.dll
358+ * libpng12.dll
359+ * libgdk-win32-2.0-0.dll
360+ * libgmodule-2.0-0.dll
361+ * libgtk-win32-2.0-0.dll
362+ * libatk-1.0-0.dll
363+ * libgdk_pixbuf-2.0-0.dll
364+ * libgobject-2.0-0.dll
365+ * libpango-1.0-0.dll
366+ * libpangowin32-1.0-0.dll
367+ * libgio-2.0-0.dll
368+ * zlib1.dll
276369
277370### Themes
278371
279-The default GTK2 interface is quite ugly and not very integrated with the Windows Desktop. Your GTK2 application may use the Windows Theme if you use the [gtk-wimp project](http://gtk-wimp.sourceforge.net/). Into your application's folder you should add the following files ([Available here](http://sourceforge.net/project/showfiles.php?group_id=76416)):
372+The default GTK2 interface is quite ugly and not very integrated with the Windows Desktop. Your GTK2 application may use the Windows Theme if you use the [gtk-wimp project](<http://gtk-wimp.sourceforge.net/>). Into your application's folder you should add the following files ([Available here](<http://sourceforge.net/project/showfiles.php?group_id=76416>)):
280373
281-- .\lib\gtk-2.0\engines\libwimp.dll
282-- .\share\themes\Raleigh\gtk-2.0\gtkrc
374+ * .\lib\gtk-2.0\engines\libwimp.dll
375+ * .\share\themes\Raleigh\gtk-2.0\gtkrc
283376
284377### A sample project
285378
286-A complete and working "Hello world" project (with sources) is available [here](http://www.lazarusforum.de/lazwiki/winGTK2_Demo.zip).
379+A complete and working "Hello world" project (with sources) is available [here](<http://www.lazarusforum.de/lazwiki/winGTK2_Demo.zip>).
287380
288-<figure>
289-<img src="WinGTK2.png" title="WinGTK2.png" />
290-<figcaption>WinGTK2.png</figcaption>
291-</figure>
381+[![WinGTK2.png](/wiki-images/b/b1/WinGTK2.png)](</File:WinGTK2.png>)
292382
293383## Current issues
294384
295-Here are some notes about some of the current issues. It is not a complete list, but mainly a collection of the information about some of the most annoying problems, that can not be solved simply.
385+Here are some notes about some of the current issues. It is not a complete list, but mainly a collection of the information about some of the most annoying problems, that can not be solved simply.
296386
387+
388+
297389### Editor Options allows to select incompatible fonts
298390
299-TFontDialog must be extended to show only monospace fonts by default and only if the users insists show all fonts.
391+TFontDialog must be extended to show only monospace fonts by default and only if the users insists show all fonts.
300392
393+
394+
301395### Moving with keys in the OI sometimes does not move the edit field
302396
303-ToDo
397+ToDo
304398
305399### Destroying handle during OnKeyDown gives AV
306400
307-This is a more general problem, not only KeyDown. There are two solutions:
401+This is a more general problem, not only KeyDown. There are two solutions:
308402
309-- Increase reference counters of all used widgets during events. Difficult to maintain and we will never be sure to ref count every used widget.
310-- Instead of destroying widgets immediately, hide them, untie them and put them into a queue. The widgets will then be destroyed in the message loop and on gtk intf shut down.
403+ * Increase reference counters of all used widgets during events. Difficult to maintain and we will never be sure to ref count every used widget.
404+ * Instead of destroying widgets immediately, hide them, untie them and put them into a queue. The widgets will then be destroyed in the message loop and on gtk intf shut down.
311405
312406### Z-Order of controls
313407
314-In Gtk2 many controls don't have a window, so they are just painted on their parent. This makes they be painted before controls with a window, so we get a wrong Z-Order.
408+In Gtk2 many controls don't have a window, so they are just painted on their parent. This makes they be painted before controls with a window, so we get a wrong Z-Order.
315409
316410Here is a list of gtk widgets that don't have windows: <https://developer.gnome.org/gtk-tutorial/stable/x481.html>
317411
318412The solution is adding a GtkEventBox under each of these widgets: <https://developer.gnome.org/gtk-tutorial/stable/c1226.html#SEC-EVENTBOX>
319413
320414**Bug reports**
321415
322-- <http://bugs.freepascal.org/view.php?id=964>
323-- <http://bugs.freepascal.org/view.php?id=8346>
416+ * <http://bugs.freepascal.org/view.php?id=964>
417+ * <http://bugs.freepascal.org/view.php?id=8346>
324418
325419### Open Dialog Options
326420
327-TOpenDialog has several options to control the dialog. When implementing these options in Gtk2, however, one needs to watch out because of the vast amount of bugs in Gtk 2, which may prevent the options from working. For example, ofForceShowHidden doesn't work because of Gtk 2 bugs, althougth it is implemented correctly.
421+TOpenDialog has several options to control the dialog. When implementing these options in Gtk2, however, one needs to watch out because of the vast amount of bugs in Gtk 2, which may prevent the options from working. For example, ofForceShowHidden doesn't work because of Gtk 2 bugs, althougth it is implemented correctly.
328422
329423**Bug reports**
330424
331-- ofForceShowHidden - <http://bugs.freepascal.org/view.php?id=8473>
425+ * ofForceShowHidden - <http://bugs.freepascal.org/view.php?id=8473>
332426
333427### TScrollBox and Scrolling problems
334428
335-TScrollBox and Scrolling seems deeply broken in Gtk 2.
429+TScrollBox and Scrolling seems deeply broken in Gtk 2.
336430
337431**Bug reports**
338432
339-- <http://bugs.freepascal.org/view.php?id=10779>
340-- <http://bugs.freepascal.org/view.php?id=10952>
341-- <http://bugs.freepascal.org/view.php?id=9049>
342-- <http://bugs.freepascal.org/view.php?id=11010>
433+ * <http://bugs.freepascal.org/view.php?id=10779>
434+ * <http://bugs.freepascal.org/view.php?id=10952>
435+ * <http://bugs.freepascal.org/view.php?id=9049>
436+ * <http://bugs.freepascal.org/view.php?id=11010>
343437
344438### Shortcut keys
345439
346440**Bug reports**
347441
348-- <http://bugs.freepascal.org/view.php?id=1946>
349-- <http://bugs.freepascal.org/view.php?id=7249>
350-- <http://bugs.freepascal.org/view.php?id=10282>
442+ * <http://bugs.freepascal.org/view.php?id=1946>
443+ * <http://bugs.freepascal.org/view.php?id=7249>
444+ * <http://bugs.freepascal.org/view.php?id=10282>
351445
352446### Up/Down key navigation between TEdits
353447
354-<s>A standard Gtk 2 feature allows the use of up/down key to navigate between GtkEntry widgets (like TEdits), but this is undesirable if the user implements a dropdrow list to be attached to the TEdit. As we cannot know what code the user has written, the best option is to disable this feature. Possible ways to do that are:
448+~~A standard Gtk 2 feature allows the use of up/down key to navigate between GtkEntry widgets (like TEdits), but this is undesirable if the user implements a dropdrow list to be attached to the TEdit. As we cannot know what code the user has written, the best option is to disable this feature. Possible ways to do that are:~~
355449
356-- Listen to key press events of GtkEntry and for Up/Down events shift the focus to implemented widget.
357-- Don't propagate Up/Down key press events to GtkEntry.</s>
450+~~~~
358451
452+~~
453+ * Listen to key press events of GtkEntry and for Up/Down events shift the focus to implemented widget.
454+~~
455+ * ~~Don't propagate Up/Down key press events to GtkEntry.~~
456+
359457**As of lazarus 0.9.31 r31562 GtkEntry behaviour is same as under other widgetsets - NO FOCUS CHANGING BY VK_UP or VK_DOWN.**
360458
361459**Bug reports**
362460
363-- <http://bugs.freepascal.org/view.php?id=11115>
461+ * <http://bugs.freepascal.org/view.php?id=11115>
364462
365463## Done issues
366464
367465### Done: ~~Synedit is very slow~~
368466
369-Actually this is not a bug of the gtk2 intf, but a problem of gtk2 and some video drivers. On some systems SynEdit is as fast as any other text editor. Some bugs were fixed with gtk 2.12. SynEdit already paints every token with the ExtTextOut function. It does not use a TCanvas text function, which would be even slower.
467+Actually this is not a bug of the gtk2 intf, but a problem of gtk2 and some video drivers. On some systems SynEdit is as fast as any other text editor. Some bugs were fixed with gtk 2.12. SynEdit already paints every token with the ExtTextOut function. It does not use a TCanvas text function, which would be even slower.
370468
371469Bug Tracker item: <http://www.freepascal.org/mantis/view.php?id=7717>
372470
373-For people using the Nvidia drivers, setting GlyphCache=1 may speed up SynEdit. You will need the beta-drivers: <http://www.nvnews.net/vbulletin/showthread.php?s=399832e3761a522d34db6faaf8423ad9&t=118088>
471+For people using the Nvidia drivers, setting GlyphCache=1 may speed up SynEdit. You will need the beta-drivers: [http://www.nvnews.net/vbulletin/showthread.php?s=399832e3761a522d34db6faaf8423ad9&t=118088](<http://www.nvnews.net/vbulletin/showthread.php?s=399832e3761a522d34db6faaf8423ad9&t=118088>)
374472
473+
474+
375475### Done: ~~Small TButton does not center text~~
376476
377-Actually the text is centered, but some themes (like the default under ubuntu) define a big minimum space above and below the label. The gtk2 default is not that big. So, it is a user setting.
477+Actually the text is centered, but some themes (like the default under ubuntu) define a big minimum space above and below the label. The gtk2 default is not that big. So, it is a user setting.
378478
379-- a\) It might be possible to override this setting and set the space to 0.
380- - Pro: Most small autosize buttons would look better.
381- - Cons: the AutoSize would be incorrect. And the bug is still there for themes with big text.
382-- b\) set the interface constraint to the gtk_button normal height.
383- - Pro: there are no small buttons.
384- - Con: Enlarging a button requires autosizing all surrounding controls too. And you need a nice auto shrink feature, which does not exist yet.
385-- c\) Set the space to 0 and when calculating the preferred size, restore temporarily the space size.
386- - Pro: Most small buttons will look better, autosize will still work.
387- - Con: Most difficult solution to implement. Maybe not possible without a hack.
479+ * a) It might be possible to override this setting and set the space to 0.
480+ * Pro: Most small autosize buttons would look better.
481+ * Cons: the AutoSize would be incorrect. And the bug is still there for themes with big text.
482+ * b) set the interface constraint to the gtk_button normal height.
483+ * Pro: there are no small buttons.
484+ * Con: Enlarging a button requires autosizing all surrounding controls too. And you need a nice auto shrink feature, which does not exist yet.
485+ * c) Set the space to 0 and when calculating the preferred size, restore temporarily the space size.
486+ * Pro: Most small buttons will look better, autosize will still work.
487+ * Con: Most difficult solution to implement. Maybe not possible without a hack.
388488
389489**Bug Reports**
390490
391-- <http://bugs.freepascal.org/view.php?id=11120>
392-- <http://bugs.freepascal.org/view.php?id=8765>
491+ * <http://bugs.freepascal.org/view.php?id=11120>
492+ * <http://bugs.freepascal.org/view.php?id=8765>
393493
394494### Done: ~~TOpenPictureDialog does not update the preview~~
395495
396496### Done: ~~Only the main form appears in the window list~~
397497
398-Probably a bug in the window hints parameters.
498+Probably a bug in the window hints parameters.
399499
400500### Done: ~~Slow and visible resizing when creating/resizing a dialog~~
401501
402-This has several reasons, which fall into 3 categories:
502+This has several reasons, which fall into 3 categories:
403503
404-1\. Too many resizes. Status: Acceptable.
504+1\. Too many resizes. Status: Acceptable.
405505
406-2\. Slow painting. Status: It seems other gtk2 apps are as slow, so maybe it is a gtk2 issue.
506+2\. Slow painting. Status: It seems other gtk2 apps are as slow, so maybe it is a gtk2 issue.
407507
408-3\. Some resizes happen after painting. Status: Acceptable.
508+3\. Some resizes happen after painting. Status: Acceptable.
409509
410-- The application does not resize the controls in one step, but in many small steps. For example: It resizes a control in several small steps SetBounds, AnchorParallel, ... . Or first the the Form is resized, then the a TPageControl, then a TButton, ... . Solution: The LCL sets BeginAlign/EndAlign during loading/creation.
411-- If there are anchored or autosized controls, every resize triggers the resize system of the the LCL. The LCL tries to combine many resizes during csLoading and Begin/EndAlign. During creation the LCL still sends several times the bounds to the interface. ToDo Solution: Send bounds not during BeginAlign (including parents), but send them all in EndAlign.
412-- The hen-egg problem. In order to autosize, the LCL needs the current gtk theme sizes. The current gtk theme sizes can only be calculated by creating a handle. When you create a handle you need the size. Solution: Create some hidden widgets to test the current gtk sizes. This already works for TCustomGroupBox and descendants. ToDo: the other controls.
413-- The gtk does not resize immediately, but puts resizes on a queue and resizes later. These values are stored in private, hidden variables. Especially if you resize a TGroupBox, the inner borders are updated later by the gtk. That means the GetClientRect function is not reliable during resizing. That's why the LCL first works with the wrong ClientRect. Solution: The LCL anticipates the new ClientRect based on the old. And there is now a GetDefaultClientRect function to ask the interface for an estimation of the ClientRect.
414-- The gtk1 intf caches LCL resize requests. This accelerates many typical overhead, but it only works with delayed painting and creates flicker during creation and resizing a form never works smooth. The delayed painting breaks the gtk2 double buffering and special paint contexts (opengl), so this trick is disabled under gtk2 and therefore the delayed resize does not work under gtk2.
415-- Top level controls, like TForm can not move/resize freely. The window manager decides, what is possible. Often they take only the first position/size request and ignores the later changes. And even worse: first the window is created, realized, then resized, then mapped and 'shown' and finally moved to the final position. So, if the gtk intf asks the gtk where a form is during creation, it will most of the time get 0,0, even though it told the gtk to move the window long ago. Because this is a more general problem (not gtk specific, but X), the LCL tries avoids asking the interface for coords and only asks on rare occasions like LM_SIZE, LM_MOVE messages coming from the interface or if told to do so.
416-- The LCL expects a LM_SIZE message on resize, including window state changes like iconify/maximize. But the gtk first notifies about the change and then resizes. ToDo: 1. Maybe: Omit the message, if the state does not change (is this Delphi compatible?). 2. Send the current window state with the normal resizes (Should work for maximize and restore from maximize). 3. Find a solution for iconify and restore from iconify.
510+ * The application does not resize the controls in one step, but in many small steps. For example: It resizes a control in several small steps SetBounds, AnchorParallel, ... . Or first the the Form is resized, then the a TPageControl, then a TButton, ... . Solution: The LCL sets BeginAlign/EndAlign during loading/creation.
511+ * If there are anchored or autosized controls, every resize triggers the resize system of the the LCL. The LCL tries to combine many resizes during csLoading and Begin/EndAlign. During creation the LCL still sends several times the bounds to the interface. ToDo Solution: Send bounds not during BeginAlign (including parents), but send them all in EndAlign.
512+ * The hen-egg problem. In order to autosize, the LCL needs the current gtk theme sizes. The current gtk theme sizes can only be calculated by creating a handle. When you create a handle you need the size. Solution: Create some hidden widgets to test the current gtk sizes. This already works for TCustomGroupBox and descendants. ToDo: the other controls.
513+ * The gtk does not resize immediately, but puts resizes on a queue and resizes later. These values are stored in private, hidden variables. Especially if you resize a TGroupBox, the inner borders are updated later by the gtk. That means the GetClientRect function is not reliable during resizing. That's why the LCL first works with the wrong ClientRect. Solution: The LCL anticipates the new ClientRect based on the old. And there is now a GetDefaultClientRect function to ask the interface for an estimation of the ClientRect.
514+ * The gtk1 intf caches LCL resize requests. This accelerates many typical overhead, but it only works with delayed painting and creates flicker during creation and resizing a form never works smooth. The delayed painting breaks the gtk2 double buffering and special paint contexts (opengl), so this trick is disabled under gtk2 and therefore the delayed resize does not work under gtk2.
515+ * Top level controls, like TForm can not move/resize freely. The window manager decides, what is possible. Often they take only the first position/size request and ignores the later changes. And even worse: first the window is created, realized, then resized, then mapped and 'shown' and finally moved to the final position. So, if the gtk intf asks the gtk where a form is during creation, it will most of the time get 0,0, even though it told the gtk to move the window long ago. Because this is a more general problem (not gtk specific, but X), the LCL tries avoids asking the interface for coords and only asks on rare occasions like LM_SIZE, LM_MOVE messages coming from the interface or if told to do so.
516+ * The LCL expects a LM_SIZE message on resize, including window state changes like iconify/maximize. But the gtk first notifies about the change and then resizes. ToDo: 1. Maybe: Omit the message, if the state does not change (is this Delphi compatible?). 2. Send the current window state with the normal resizes (Should work for maximize and restore from maximize). 3. Find a solution for iconify and restore from iconify.
417517
418-Things done to handle the above issues:
518+Things done to handle the above issues:
419519
420-- The gtk2 intf now calls gtk_widget_size_allocate when resizing widgets. This initializes the Widget^.allocation, so that further reads by the LCL no longer give old values.
421-- Resizes of child widgets (not gtkwindow or not top level) are now given to the gtk immediately. This does not resize immediately, but together with other changes this resizes earlier, reducing the total number of resizes.
422-- gtk resize events are now given almost always directly to the LCL. The only exception is gtkwindow and the client areas (gtk_fixed). The gtk resize events come bottom up, so the client areas are always triggered before the widget itself is resized.
423-- The gtk intf now checks the mapped attribute for gtkwindow, which seems finally to work reliable under gtk2. This means the gtk intf no longer send window positions to the LCL, before the window is really moved.
424-- In order to let the LCL resize during component/handle creation, the new function GetDefaultClientRect allows every widget class to provide a nice clientrect even before the handle is created. This is done by using the hidden style widgets of the gtk intf.
520+ * The gtk2 intf now calls gtk_widget_size_allocate when resizing widgets. This initializes the Widget^.allocation, so that further reads by the LCL no longer give old values.
521+ * Resizes of child widgets (not gtkwindow or not top level) are now given to the gtk immediately. This does not resize immediately, but together with other changes this resizes earlier, reducing the total number of resizes.
522+ * gtk resize events are now given almost always directly to the LCL. The only exception is gtkwindow and the client areas (gtk_fixed). The gtk resize events come bottom up, so the client areas are always triggered before the widget itself is resized.
523+ * The gtk intf now checks the mapped attribute for gtkwindow, which seems finally to work reliable under gtk2. This means the gtk intf no longer send window positions to the LCL, before the window is really moved.
524+ * In order to let the LCL resize during component/handle creation, the new function GetDefaultClientRect allows every widget class to provide a nice clientrect even before the handle is created. This is done by using the hidden style widgets of the gtk intf.
425525
426526### Done: ~~Selecting a TPage in the designer gives the wrong bounds rectangle~~
427527
428-GetClientOrigin needed extra code for TNotebook, which does not have a normal client area.
528+GetClientOrigin needed extra code for TNotebook, which does not have a normal client area.
429529
430530### Done: ~~Sometimes the hint window of the component palette is not resized~~
431531
432-Sometimes the gtk does not resize the gdkwindow. This is now forced and it seems to fix this problem.
532+Sometimes the gtk does not resize the gdkwindow. This is now forced and it seems to fix this problem.
433533
434534### Done: ~~gtk criticals in IDE codetools options dialog~~
435535
436-Empty comboboxes do not have all private structures, so you can not set callbacks.
536+Empty comboboxes do not have all private structures, so you can not set callbacks.
437537
438538### Done: System Colors
439539
440-The system colors depend on the theme, but many themes don't give adequate colors and many controls use system colors, so we need them to have a correct value. To solve this, a list of ignored system colors was constructed, and in case the user sets any of these colors, it is ignored and the default theme color is used instead.
540+The system colors depend on the theme, but many themes don't give adequate colors and many controls use system colors, so we need them to have a correct value. To solve this, a list of ignored system colors was constructed, and in case the user sets any of these colors, it is ignored and the default theme color is used instead.
441541
442-List of colors which were tested and need to be ignored for the correct functioning of programs:
542+List of colors which were tested and need to be ignored for the correct functioning of programs:
443543
444-- clBtnFace - Otherwise Notebooks and Buttons look bad
544+ * clBtnFace - Otherwise Notebooks and Buttons look bad
445545
446546**Bug reports**
447547
448-- <http://bugs.freepascal.org/view.php?id=8684>
548+ * <http://bugs.freepascal.org/view.php?id=8684>
449549
450550## Gtk1/Gtk2 separation roadmap
451551
452-List of already separated elements:
552+List of already separated elements:
453553
454-- gtk2wscomctrls --- gtkwscomctrls
455-- gtk2wsdialogs --- gtkwsdialogs
456-- gtk2wsspin --- gtkwsspin
457-- gtk2wscalendar --- gtkwscalendar
554+ * gtk2wscomctrls --- gtkwscomctrls
555+ * gtk2wsdialogs --- gtkwsdialogs
556+ * gtk2wsspin --- gtkwsspin
557+ * gtk2wscalendar --- gtkwscalendar
458558
459-Next tasks:
559+Next tasks:
460560
461-- Rework of the events system
462-- Rework of private classes
561+ * Rework of the events system
562+ * Rework of private classes
463563
464564## Profiling
465565
466-There are various compiler switches:
566+There are various compiler switches:
467567
468-- VerboseSizeMsg - This will show you all changes and messages, with coords and reasons. Even for simple forms this gives a lot of output.
469-- DisableLoadedClientSize - This will ignore the ClientWidth/Height stored in the .lfm/.lrs files. This way you can somehow simulate, what happens, if you start an application under a different theme.
568+ * VerboseSizeMsg - This will show you all changes and messages, with coords and reasons. Even for simple forms this gives a lot of output.
569+ * DisableLoadedClientSize - This will ignore the ClientWidth/Height stored in the .lfm/.lrs files. This way you can somehow simulate, what happens, if you start an application under a different theme.
470570
471571---
472-*From the Free Pascal wiki, page "GTK2 Interface", as it stood on 2022-11-25 after a change by Dbannon, 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).*
572+*From the Free Pascal wiki, page "GTK2 Interface", as the Internet Archive kept it on 2023-01-31. 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