2004-12-30 Mike Kestner <mkestner@novell.com>
* glib/Object.cs : mark the Data hashtable obsolete. svn path=/trunk/gtk-sharp/; revision=38201
This commit is contained in:
parent
ecb6c75c26
commit
56a0288b7b
3 changed files with 12 additions and 1 deletions
|
@ -1,3 +1,7 @@
|
|||
2004-12-30 Mike Kestner <mkestner@novell.com>
|
||||
|
||||
* glib/Object.cs : mark the Data hashtable obsolete.
|
||||
|
||||
2004-12-30 Mike Kestner <mkestner@novell.com>
|
||||
|
||||
* gtk/Gtk.metadata : hide TreeView.InsertColumnWith*.
|
||||
|
|
|
@ -87,6 +87,12 @@
|
|||
<summary>Stores and Accesses arbitrary data on the Object.</summary>
|
||||
<returns>a <see cref="T:System.Collections.Hashtable" /></returns>
|
||||
<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>
|
||||
</Docs>
|
||||
</Member>
|
||||
|
@ -383,4 +389,4 @@
|
|||
</Docs>
|
||||
</Member>
|
||||
</Members>
|
||||
</Type>
|
||||
</Type>
|
||||
|
|
|
@ -285,6 +285,7 @@ namespace GLib {
|
|||
return Handle.GetHashCode ();
|
||||
}
|
||||
|
||||
[Obsolete("Can cause instability due to garbage collection of GLib.Objects.")]
|
||||
public Hashtable Data {
|
||||
get {
|
||||
if (data == null)
|
||||
|
|
Loading…
Reference in a new issue