doc update
svn path=/trunk/gtk-sharp/; revision=147061
This commit is contained in:
parent
e216baa99f
commit
f1bf740bf5
2 changed files with 5 additions and 8 deletions
|
@ -1,3 +1,7 @@
|
|||
2009-11-28 Mike Kestner <mkestner@novell.com>
|
||||
|
||||
* GLib/Object.xml: remove an out of date remark from the Data prop.
|
||||
|
||||
2009-08-19 Christian Hoff <christian_hoff@gmx.net>
|
||||
|
||||
* glib/MainContext.xml, glib/MainLoop.xml: Add docs for the new API.
|
||||
|
|
|
@ -203,14 +203,7 @@ This method is called by the generated classes by the Gtk# framework.
|
|||
<Docs>
|
||||
<summary>Stores and Accesses arbitrary data on the Object.</summary>
|
||||
<value>a <see cref="T:System.Collections.Hashtable" /></value>
|
||||
<remarks>
|
||||
This property is obsolete and should not be used unless you explicitly retain a reference to the
|
||||
<see cref="T:GLib.Object" />. Otherwise the Data hashtable will be lost when the Garbage Collector
|
||||
releases your managed object wrapper. There are much better alternatives to this anyway. Consider
|
||||
using a Hashtable on your class that is keyed by <see cref="T:GLib.Object" /> or a subclass with
|
||||
an object property for the data you want to store instead. There are many better ways to accompish
|
||||
the role of this property.
|
||||
</remarks>
|
||||
<remarks/>
|
||||
</Docs>
|
||||
</Member>
|
||||
<Member MemberName="Dispose">
|
||||
|
|
Loading…
Add table
Reference in a new issue