callisto-debian/gimp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Imported Upstream version 2.4.2

Browse Source
This commit is contained in:
Ari Pollak
2010-08-11 01:23:49 -04:00
parent 69250d2dd6
commit 12749080f0
194 changed files with 28480 additions and 21925 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
devel-docs/libgimpwidgets/html/libgimpwidgets-GimpHelpUI.html
View File

@ -129,11 +129,11 @@ All these dialog constructors functions call <a class="link" href="libgimpwidget
<p>
In most cases it will be ok to use <a class="link" href="libgimpwidgets-GimpHelpUI.html#gimp-standard-help-func"><code class="function">gimp_standard_help_func()</code></a> which does
nothing but passing the <em class="parameter"><code>help_id</code></em> string to <a
href="../libgimp/libgimp-gimphelp.html#gimp-help"
href="../app/app-Gimp-gui.html#gimp-help"
><code class="function">gimp_help()</code></a>. If your
plug-in needs some more sophisticated help handling you can provide
your own <em class="parameter"><code>help_func</code></em> which has to call <a
href="../libgimp/libgimp-gimphelp.html#gimp-help"
href="../app/app-Gimp-gui.html#gimp-help"
><code class="function">gimp_help()</code></a> to actually display
the help.
</p>
@ -204,7 +204,7 @@ href="../glib/glib-Basic-Types.html#gpointer"
<p>
This is the standard GIMP help function which does nothing but calling
<a
href="../libgimp/libgimp-gimphelp.html#gimp-help"
href="../app/app-Gimp-gui.html#gimp-help"
><code class="function">gimp_help()</code></a>. It is the right function to use in almost all cases.</p>
<p>