Difference between revisions of "Cocoa Interface"

From Free Pascal wiki
(FPC 3.2.0 for older macOS)
(External links: New section)
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{Cocoa Interface}}
 
{{Cocoa Interface}}
 
{{Platform only|macOS|macOS|macOS}}
 
{{Platform only|macOS|macOS|macOS}}
{{Other Interfaces}}
 
  
=Cocoa bindings=
+
== Cocoa bindings ==
  
 
The Cocoa interface uses the native support in Free Pascal for direct communication with Objective-C which was added through the [[FPC PasCocoa|Objective Pascal]] dialect.
 
The Cocoa interface uses the native support in Free Pascal for direct communication with Objective-C which was added through the [[FPC PasCocoa|Objective Pascal]] dialect.
  
=Compiling=
+
== Compiling ==
  
==Use FPC 3.0.4a==
+
For macOS 10.14 Mojave and later you should be installing FPC 3.2.0 available from the official [https://sourceforge.net/projects/lazarus/files/ Lazarus IDE file area].
  
For macOS 10.14 Mojave and later you should be installing FPC 3.0.4a available at the official site.
+
=== FPC 3.2.0 for macOS 10.10 and earlier ===
==FPC 3.2.0 for macOS 10.10 and earlier==
 
It's likely you will not encounter ANY problems using FPC 3.2.0 on macOS 10.11 and later.
 
  
 +
The precompiled CocoaAll header comes with an instruction to link the CoreImage framework. The framework was introduced in macOS 10.11 and later. (The CoreImage APIs were available since 10.4, BUT there was a stand-alone CoreImage framework. They were all part of QuartzCore framework).
 +
Compiling any unit using CocoaAll will likely cause the linking stage to fail on macOS 10.10 and earlier, as the framework doesn't exist.
  
The precompiled CocoaAll header comes with the instruction to link CoreImage framework. The framework was introduced in macOS10.11 and later.
+
In order to fix that one might want to update headers and recompile them from the sources.
Compiling any unit using CocoaAll will likely cause the linking stage to fail on macOS 10.10 and earlier, as the framework doesn't exist.
+
 
 +
1. Get the FPC sources (you might have them already installed with Lazarus, as it's a prerequisite for the IDE).
 +
 
 +
2. Go to %sourcesdir%/packages/cocoaint/src
  
In order to fix that one might want to update headers and recompile them from sources.
+
3. Edit CocoaAll.pas and comment out or remove The CoreImage linking line:
  
1. Get FPC sources. (you might have it already installed with Lazarus, as it's the IDE prerequisite)
+
<syntaxhighlight lang=pascal>
2. Go to %sourcesdir%/packages/cocoaint
 
3. edit CocoaAll and comment out or remove CoreImage linking line
 
 
  unit CocoaAll;
 
  unit CocoaAll;
 
  interface
 
  interface
Line 29: Line 29:
 
  {$linkframework Cocoa}
 
  {$linkframework Cocoa}
 
  {$linkframework Foundation}
 
  {$linkframework Foundation}
  //{$linkframework CoreImage} // commented out
+
  //{$linkframework CoreImage} comment out this line
 
  {$linkframework QuartzCore}
 
  {$linkframework QuartzCore}
 
  {$linkframework CoreData}
 
  {$linkframework CoreData}
 
  {$linkframework AppKit}
 
  {$linkframework AppKit}
4. headers now needs to be recompiled.  
+
</syntaxhighlight>
5. go back to the root directory of the sources
+
 
6. compile RTL packages.  
+
4. Headers now needs to be recompiled.
 +
 
 +
5. Go back to the root directory of the sources.
 +
 
 +
6. Compile the RTL packages.  
 
  make rtl
 
  make rtl
This should compile 64-bit version of RTL. The RTL is needed to compile packages in the next step
+
This should compile a 64-bit version of the RTL. The RTL is needed to compile packages in the next step.
7. compile packages  
+
 
  make pacakges
+
7. Compile the packages:
Thie should compile 64-bit version of FPC packages.
+
  make packages
8. Go to %sourcesdir%/packages/cocoaint  
+
This should compile A 64-bit version of the FPC packages.
9. run the command to install the package (to the default system location). (don't forget to add OPT=" if you're on 10.7 or earlier)
+
 
 +
8. Go to %sourcesdir%/packages/cocoaint
 +
 
 +
9. Run the command to install the package (to the default system location). Do not forget to add OPT=" if you're on 10.7 or earlier:
 
  sudo make install
 
  sudo make install
  
==Prepare your Lazarus project for using Cocoa==
+
=== Prepare your Lazarus project for using Cocoa ===
  
 
You may need to set the Target to the 64bit processor and select the Cocoa Widget set:
 
You may need to set the Target to the 64bit processor and select the Cocoa Widget set:
Line 55: Line 62:
 
*Now compile your project - with any luck it will work OK.
 
*Now compile your project - with any luck it will work OK.
  
==Error ATSUFindFontFromName==
+
=== Error ATSUFindFontFromName ===
  
 
If you're getting the error:
 
If you're getting the error:
Line 61: Line 68:
 
  carbonproc.pp(563,13) Error: Identifier not found "ATSUFindFontFromName"
 
  carbonproc.pp(563,13) Error: Identifier not found "ATSUFindFontFromName"
  
when compiling a project for macOS using FPC 3.0.4, you either:
+
when compiling a project for macOS using FPC, you either:
  
* set the CPU target explicitly to i386. (FPC 3.0.4 compiles to x86_64 for the Darwin target by default. This is done due Apple having dropped support for 32-bit target in macOS 10.15 Catalina released in October 2019.)
+
* set the CPU target explicitly to i386. (FPC 3.2.0 compiles to x86_64 for the Darwin target by default. This is done due Apple having dropped support for 32-bit target in macOS 10.15 Catalina released in October 2019.)
 
:*by setting the target in Project options (switching it from default to i386)
 
:*by setting the target in Project options (switching it from default to i386)
 
:*by setting the ''CPU_TARGET=i386'' parameter for the make command if compiling from the command line.
 
:*by setting the ''CPU_TARGET=i386'' parameter for the make command if compiling from the command line.
 
* or set the LCL target (widgetset) to "Cocoa".
 
* or set the LCL target (widgetset) to "Cocoa".
  
= Cocoa Debugging =
+
=== Cocoa Debugging ===
  
 
See the [[Cocoa_Debugging|Cocoa Debugging]] article.
 
See the [[Cocoa_Debugging|Cocoa Debugging]] article.
  
=Cocoa FAQ=
+
== Cocoa FAQ ==
  
==DPI and scaling issues==
+
=== DPI and scaling issues ===
  
 
See the [[Cocoa_DPI|Cocoa DPI]] article.
 
See the [[Cocoa_DPI|Cocoa DPI]] article.
  
==TButton looks too small!==
+
=== TButton looks too small! ===
  
 
If you design a button in another widgetset with Autosize=False it might happen that the button looks too small in Cocoa, and a number of people have complained about this, such as in [https://bugs.freepascal.org/view.php?id=31185 this bug report].  
 
If you design a button in another widgetset with Autosize=False it might happen that the button looks too small in Cocoa, and a number of people have complained about this, such as in [https://bugs.freepascal.org/view.php?id=31185 this bug report].  
Line 87: Line 94:
 
* Constrains.MinWidth = Constrains.MaxWidth = your desired width.
 
* Constrains.MinWidth = Constrains.MaxWidth = your desired width.
  
==Overlapping Widgets==
+
=== Overlapping Widgets ===
  
 
Lazarus allows you to set the depth of different widgets, such that when two widgets overlap, the "closer" object blocks the view of the more "distant" object. You can do this at design time (right-click on object and click "Z-order") or at run time with functions like "BringToFront" and "SendToBack". Be aware that this may not always work with Cocoa. This is a 'feature' of Cocoa, as clipping is optimized for performance. Therefore, if you plan to compile your projects for Cocoa it is a good strategy to avoid overlapping widgets or to place them on different panels to provide explicit control of Z-order. For more details [https://bugs.freepascal.org/view.php?id=32991 see this bug report].
 
Lazarus allows you to set the depth of different widgets, such that when two widgets overlap, the "closer" object blocks the view of the more "distant" object. You can do this at design time (right-click on object and click "Z-order") or at run time with functions like "BringToFront" and "SendToBack". Be aware that this may not always work with Cocoa. This is a 'feature' of Cocoa, as clipping is optimized for performance. Therefore, if you plan to compile your projects for Cocoa it is a good strategy to avoid overlapping widgets or to place them on different panels to provide explicit control of Z-order. For more details [https://bugs.freepascal.org/view.php?id=32991 see this bug report].
  
=Roadmap=
+
== Roadmap ==
  
 
[[Roadmap|Roadmap: Status of Features in each Widget set]]
 
[[Roadmap|Roadmap: Status of Features in each Widget set]]
 +
 +
== See also ==
 +
 +
* [[Cocoa Internals]]
 +
 +
== External links ==
 +
 +
* [https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/EventOverview/Introduction/Introduction.html Apple: Cocoa Event Handling]
 +
* [https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/Button/Button.html Apple: Button Programming Topics]
 +
* [https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/CocoaBindings/CocoaBindings.html Apple: Cocoa Bindings Programming Topics]
 +
* [https://developer.apple.com/library/archive/documentation/TextFonts/Conceptual/CocoaTextArchitecture/Introduction/Introduction.html Apple: Cocoa Text Architecture Guide]
 +
 +
{{Other Interfaces}}

Latest revision as of 02:39, 24 February 2021

English (en)

macOSlogo.png

This article applies to macOS only.

See also: Multiplatform Programming Guide

Cocoa bindings

The Cocoa interface uses the native support in Free Pascal for direct communication with Objective-C which was added through the Objective Pascal dialect.

Compiling

For macOS 10.14 Mojave and later you should be installing FPC 3.2.0 available from the official Lazarus IDE file area.

FPC 3.2.0 for macOS 10.10 and earlier

The precompiled CocoaAll header comes with an instruction to link the CoreImage framework. The framework was introduced in macOS 10.11 and later. (The CoreImage APIs were available since 10.4, BUT there was a stand-alone CoreImage framework. They were all part of QuartzCore framework). Compiling any unit using CocoaAll will likely cause the linking stage to fail on macOS 10.10 and earlier, as the framework doesn't exist.

In order to fix that one might want to update headers and recompile them from the sources.

1. Get the FPC sources (you might have them already installed with Lazarus, as it's a prerequisite for the IDE).

2. Go to %sourcesdir%/packages/cocoaint/src

3. Edit CocoaAll.pas and comment out or remove The CoreImage linking line:

 unit CocoaAll;
 interface
 
 {$linkframework Cocoa}
 {$linkframework Foundation}
 //{$linkframework CoreImage} comment out this line
 {$linkframework QuartzCore}
 {$linkframework CoreData}
 {$linkframework AppKit}

4. Headers now needs to be recompiled.

5. Go back to the root directory of the sources.

6. Compile the RTL packages.

make rtl

This should compile a 64-bit version of the RTL. The RTL is needed to compile packages in the next step.

7. Compile the packages:

make packages

This should compile A 64-bit version of the FPC packages.

8. Go to %sourcesdir%/packages/cocoaint

9. Run the command to install the package (to the default system location). Do not forget to add OPT=" if you're on 10.7 or earlier:

sudo make install

Prepare your Lazarus project for using Cocoa

You may need to set the Target to the 64bit processor and select the Cocoa Widget set:

  • Open your project with Lazarus and click Project/Project Options
  • In the "Config and Target" panel set the "Target CPU family" to be "x86_64"
  • In the "Additions and Overrides" panel click on "Set LCLWidgetType" pulldown and set the value to "Cocoa"
  • In the past, for some reason Lazarus kept setting the compiler to "/usr/local/bin/ppc386" - which results in 32 bit apps. Make sure under Tools->Options that "Compiler Executable" is set to "/usr/local/bin/fpc" to get 64 bit apps.
  • Now compile your project - with any luck it will work OK.

Error ATSUFindFontFromName

If you're getting the error:

carbonproc.pp(563,13) Error: Identifier not found "ATSUFindFontFromName"

when compiling a project for macOS using FPC, you either:

  • set the CPU target explicitly to i386. (FPC 3.2.0 compiles to x86_64 for the Darwin target by default. This is done due Apple having dropped support for 32-bit target in macOS 10.15 Catalina released in October 2019.)
  • by setting the target in Project options (switching it from default to i386)
  • by setting the CPU_TARGET=i386 parameter for the make command if compiling from the command line.
  • or set the LCL target (widgetset) to "Cocoa".

Cocoa Debugging

See the Cocoa Debugging article.

Cocoa FAQ

DPI and scaling issues

See the Cocoa DPI article.

TButton looks too small!

If you design a button in another widgetset with Autosize=False it might happen that the button looks too small in Cocoa, and a number of people have complained about this, such as in this bug report.

If you don't care about the button size, just set AutoSize=True. If you want to have a custom width for the button, but want to allow the LCL to choose the right Height so that the button will look good in Cocoa, then the solution in this case is to set the following properties in the Object Inspector:

  • AutoSize=True
  • Constrains.MinWidth = Constrains.MaxWidth = your desired width.

Overlapping Widgets

Lazarus allows you to set the depth of different widgets, such that when two widgets overlap, the "closer" object blocks the view of the more "distant" object. You can do this at design time (right-click on object and click "Z-order") or at run time with functions like "BringToFront" and "SendToBack". Be aware that this may not always work with Cocoa. This is a 'feature' of Cocoa, as clipping is optimized for performance. Therefore, if you plan to compile your projects for Cocoa it is a good strategy to avoid overlapping widgets or to place them on different panels to provide explicit control of Z-order. For more details see this bug report.

Roadmap

Roadmap: Status of Features in each Widget set

See also

External links

Other Interfaces

Platform specific Tips

Interface Development Articles