language-servers/slint
1
0
Fork 0
mirror of https://github.com/slint-ui/slint.git synced 2025-10-01 06:11:16 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5

C++ docs: Link to the section of the generated code from the namespace intro

Browse source
This commit is contained in:
Simon Hausmann 2021-07-02 09:56:52 +02:00
parent 4705415642
commit 69bbef529c
1 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

7
api/sixtyfps-cpp/include/sixtyfps.h
View file

@ -37,9 +37,10 @@ struct ItemVTable;
/// There are two ways of loading :code:`.60` markup files in your application: /// There are two ways of loading :code:`.60` markup files in your application:
/// ///
/// #. You could translate them to C++ with the help of the :code:`sixtyfps_target_60_sources` /// #. You could translate them to C++ with the help of the :code:`sixtyfps_target_60_sources`
/// cmake command and use the generated C++ API to instantiate the UI, set or get property /// cmake command and use the :doc:`generated C++ API<../generated_code>` to instantiate the UI,
/// values or callback handlers. That API will use types from the :code:`sixtyfps` namespace, /// set or get property values or callback handlers. That API will use types from the
/// for example :cpp:class:`sixtyfps::SharedString` or :cpp:class:`sixtyfps::Color`. /// :code:`sixtyfps` namespace, for example :cpp:class:`sixtyfps::SharedString` or
/// :cpp:class:`sixtyfps::Color`.
/// #. Alternatively, you can choose to load the :code:`.60` files dynamically at run-time, using /// #. Alternatively, you can choose to load the :code:`.60` files dynamically at run-time, using
/// the SixtyFPS Interpreter from the :code:`sixtyfps::interpreter` namespace, starting at /// the SixtyFPS Interpreter from the :code:`sixtyfps::interpreter` namespace, starting at
/// :cpp:class:`sixtyfps::interpreter::ComponentCompiler`. /// :cpp:class:`sixtyfps::interpreter::ComponentCompiler`.