~ubuntu-branches/ubuntu/lucid/gconf/lucid

« back to all changes in this revision

Viewing changes to doc/gconf/html/gconf-GConfClient.html

  • Committer: Bazaar Package Importer
  • Author(s): Sebastien Bacher
  • Date: 2009-02-16 14:28:01 UTC
  • mfrom: (1.1.9 upstream)
  • Revision ID: james.westby@ubuntu.com-20090216142801-im569ps1p2mno3ve
Tags: 2.25.1-0ubuntu1
* New upstream version:
  Fixes
  - Missing return in gconftool.c/do_toggle 
  - Fix xml-backend symbol exports on Cygwin 
  - Win32 build fixes 
  - Optimizations in the markup backend 
  - Don't hardcode paths in the defaults mechanism 
  - Fix dbus policy for the defaults mechanism (lp: #318770)

Show diffs side-by-side

added added

removed removed

Lines of Context:
439
439
<a class="link" href="gconf-GConfClient.html#gconf-client-get-default" title="gconf_client_get_default ()"><code class="function">gconf_client_get_default()</code></a>, there is no (legitimate) way to obtain a pointer to the
440
440
underlying <a class="link" href="gconf-gconf-engine.html#GConfEngine" title="GConfEngine"><span class="type">GConfEngine</span></a>. If you create a <span class="type">GConfClient</span> from an existing engine,
441
441
you'll have to be disciplined enough to avoid using that engine directly.
442
 
<sup>[<a name="id2764163" href="#ftn.id2764163" class="footnote">1</a>]</sup>
 
442
<sup>[<a name="id2949331" href="#ftn.id2949331" class="footnote">1</a>]</sup>
443
443
</p>
444
444
</div>
445
445
<p>
2835
2835
</div>
2836
2836
<div class="footnotes">
2837
2837
<br><hr width="100" align="left">
2838
 
<div class="footnote"><p><sup>[<a name="ftn.id2764163" href="#id2764163" class="para">1</a>] </sup>
 
2838
<div class="footnote"><p><sup>[<a name="ftn.id2949331" href="#id2949331" class="para">1</a>] </sup>
2839
2839
This is all a white lie; <span class="emphasis"><em>some</em></span> direct <a class="link" href="gconf-gconf-engine.html#GConfEngine" title="GConfEngine"><span class="type">GConfEngine</span></a>
2840
2840
operations are safe. But it's complicated to know which, and if an operation
2841
2841
isn't safe the resulting bugs will mangle the cache and cause weird bugs at an