- 1 Introduction
- 2 Guide rapide de démarrage
- 3 Road map for the gtk2 interface
- 4 Current issues
- 4.1 Synedit is very slow
- 4.2 Editor Options allows to select incompatible fonts
- 4.3 TOpenPictureDialog does not update the preview
- 4.4 Only the main form appears in the window list
- 4.5 Small TButton does not center text
- 4.6 Done: Slow and visible resizing when creating/resizing a dialog
- 4.7 Done: Selecting a TPage in the designer gives the wrong bounds rectangle
- 4.8 Moving with keys in the OI sometimes does not move the edit field
- 4.9 Done: Sometimes the hint window of the component palette is not resized
- 4.10 Destroying handle during OnKeyDown gives AV
- 4.11 Done: gtk criticals in IDE codetools options dialog
- 5 Profiling
L'ensemble de composants graphiques gtk2 est en cours de développement . La plupart de composants fonctionnent déjà, mais il reste beaucoup de bogues et des propriétés manquantes. Et cela manque d'optimisations .
La documentation peut être trouvée ici .
Guide rapide de démarrage
La première chose à faire est d'installer les bibliothèques gtk2 y compris les paquets de développement .Par exemple : les systèmes d'exploitation linux/debian les appelent: libgtk2.0-dev. Ce sont des installateurs complets pour windows et MacsOSX ici .
Compiler maintenant LCL pour gtk2.Ouvrir d'abord votre version compilée normale de Lazarus. Aller alors au 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. (Note: the default widgetset is still there and not overwritten).
To compile a project for gtk2 just select it as the target widgetset on the Compiler Options dialog.
At this moment the Lazarus IDE can be compiled for gtk2, but it is slow and it can crash on some window managers.
Road map for the gtk2 interface
Moved here: Roadmap#Widgetset_dependent_components
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.
Synedit is very slow
SynEdit paints every token with the ExtTextOut function. It does not use a TCanvas text function. ToDo: find a fast gdk or pango function to paint a single token.
Bug Tracker item: http://www.freepascal.org/mantis/view.php?id=7717
Editor Options allows to select incompatible fonts
TFontDialog must be extended to show only monospace fonts by default and only if the users insists show all fonts.
TOpenPictureDialog does not update the preview
Only the main form appears in the window list
Probably a bug in the window hints parameters.
Small TButton does not center text
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.
- a) It might be possible to override this setting and set the space to 0.
- Pro: Most small autosize buttons would look better.
- Cons: the AutoSize would be incorrect. And the bug is still there for themes with big text.
- b) set the interface constraint to the gtk_button normal height.
- Pro: there are no small buttons.
- Con: Enlarging a button requires autosizing all surrounding controls too. And you need a nice auto shrink feature, which does not exist yet.
- c) Set the space to 0 and when calculating the preferred size, restore temporarily the space size.
- Pro: Most small buttons will look better, autosize will still work.
- Con: Most difficult solution to implement. Maybe not possible without a hack.
Slow and visible resizing when creating/resizing a dialog
This has several reasons, which fall into 3 categories:
1. Too many resizes. Status: Acceptable.
2. Slow painting. Status: It seems other gtk2 apps are as slow, so maybe it is a gtk2 issue.
3. Some resizes happen after painting. Status: Acceptable.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Things done to handle the above issues:
- 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.
- 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.
- 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.
- 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.
- 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.
Selecting a TPage in the designer gives the wrong bounds rectangle
GetClientOrigin needed extra code for TNotebook, which does not have a normal client area.
Moving with keys in the OI sometimes does not move the edit field
Sometimes the hint window of the component palette is not resized
Sometimes the gtk does not resize the gdkwindow. This is now forced and it seems to fix this problem.
Destroying handle during OnKeyDown gives AV
This is a more general problem, not only KeyDown. There are two solutions:
- Increase reference counters of all used widgets during events. Difficult to maintain and we will never be sure to ref count every used widget.
- 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.
gtk criticals in IDE codetools options dialog
Empty comboboxes do not have all private structures, so you can not set callbacks.
There are various compiler switches:
- VerboseSizeMsg - This will show you all changes and messages, with coords and reasons. Even for simple forms this gives a lot of output.
- 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.