Lazarus known issues (things that will never be fixed)
From Free Pascal wiki
Interfaces
- Lazarus known issues (things that will never be fixed) - A list of interface compatibility issues
- Win32/64 Interface - The winapi interface for Windows 95/98/Me/2K/XP/Vista, but not CE
- GTK2 Interface - The gtk2 for Unixes, Mac OS X, Windows
- Carbon Interface - The Carbon Interface for Mac OS X
- Qt Interface - The Qt 4 Interface for Unixes, Mac OS X and linux-based PDAs
- Windows CE Interface - For Pocket PC and Smartphones
- fpGUI Interface - A widgetset completely written in Object Pascal
Win32/Win64 issues
- TComboBox.Height - It's impossible to set an arbitrary size of a TComboBox under Windows. Use AutoSize to make sure the size is good on all platforms.
- TButton's and TBitBtn's color cannot be changed. It's impossible to implement without making them owner drawn.
GTK 1 issues
- Inconsistent internationalization support. GTK 1 always uses the default locale encoding to input and draw text and therefore adequate unicode support cannot be implemented for it.
- TTabSheet.TabVisible property. TabSheet under gtk1 can either be fully hiden (with Tab) or fully visible (with Tab). There is no posibility to show TabSheet without it tab. Look at gtk1 sources (gtknotebook.c) for details.
GTK 2 issues
- TForm.ShowInTaskbar is ignored and forms are always shown on the taskbar. Under KDE (and possibly other window managers) if a window isn't on the taskbar it won't also be able to minimize. This is a big problem for the IDE, which has many windows open at the same time, most of which set not to show in the taskbar and which also desires to be able to minimize the windows.
Carbon issues
Go to Carbon_interface_issues.
- Cannot be used to write 64-bits applications. Apple decided not to release a 64-bits version of Carbon. The migration path is writing a new interface in Cocoa.
QT issues
- Cannot be used with proprietary applications unless a Qt license is bought.
- The display filter for TOpenDialog/TSaveDialog will always include the filtered extensions in parenteses. Qt always adds parenteses with the filtered extensions, so if this is already present, the interface will try to remove them. For more information see TQtWSFileDialog.GetQtFilterString on the Qt interface.
