![]() In Projectfiles as well as in the configfile for render-presets, the render-settings are stored using a string. To know, how to read them, I suggest you to read the Config Variables-docs above. They are documented with values in int/double/string and bitfield. This lists all toggle-actions, who trigger config-variables. ![]() These are fairly complete with only a handful missing(I couldn't trigger them, maybe you can help me with them).Īll Config-Variables, that are triggered by actions. You can set many options, checkboxes and configuration-values with them. The config-variables as used by SNM_GetIntConfigVar(), SNM_SetIntConfigVar(), SNM_GetDoubleConfigVar() and SNM_SetDoubleConfigVar(), as well as the C++-only function get_config_var(). This lists all commandids, that are reserved for ReaScripts, separated into the individual sections.įunfact: About 11997-scripts can be added to each section ) Includes Menu-only-actions as well(those aren't shown in the actionlist). Tutorial for HiDPI/Retina in gfx-scripts ()Ī web-version of Reaper's video-processor-docsĭescriptions for various config-files of Reaperĭescribes the config-file of Cocko's LiceCap-Screenrecording-tool. I wrote a small introduction there on how to use Reaper's defer-function. This is work in progress, but maybe it's useful for you already. ![]() I also added the C++-functions and I structured the index to reflect the individual use-case-areas appearing in the API. This is my own version of the API-docs of Reaper, where I try to add all the information that's missing, like parameter/retval-descriptions, function-descriptions, etc. See also: Tutorials, created by the community () Some are work in progress and some are far from finished, while others are more updated versions of the docs available in Cocko's Wiki.Īll these docs are creative commons cc-by-nc-sa, so feel free to use them, share them and have fun with it. The whole thing is far away from being a proper developer-doc, but you may or may not see use in these docs, so I uploaded them. the textual documentation is very C centric, refers to memory management, skipped arguments.While learning Reaper to develop stuff for Ultraschall.fm, I started to document things for the others in our project, as well as a resource for myself.cross-references to non-introspectable APIs are dead (because the page does not exists).g-ir-doc-tool does not understand gtk-doc sectioning, so the content is structured different than the C API.g-ir-doc-tool sometimes generates wrong documentation for impossible to use boxed types (such as GOptionEntry).g-ir-doc-tool needs to understand gtk-doc Markdown. ![]() In the future we will host documentation for native gjs APIs (Lang, Mainloop, Signals.) The preliminary results of this work are hosted at Īdditional updated documentation hosted at īecause we host also documentation for gjs-specific APIs in GLib, GObject and Gio (so called "overrides"). The module includes a basic Makefile to build the documentation locally, as well as upload it to. It is written in mallard and generated through g-ir-doc-tool. For updated documentation, please see the GJS repository.ĭocumentation for Gjs, and for the GNOME platform libraries as used in gjs, is hosted in the gjs-documentation module in git.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |