realbasic-plugins
[Top] [All Lists]

Locking objects

To: REALbasic Plugins <realbasic-plugins at lists dot realsoftware dot com>
Subject: Locking objects
From: Phil M <phil at mobleybros dot com>
Date: Mon, 17 Jul 2006 19:37:22 -0400
Delivered-to: listarchive at realsoftware dot com
Delivered-to: realbasic-plugins at lists dot realsoftware dot com
When you lock an object, does it *only* mean that the plugin is requesting REALbasic to increment the reference counting for that object? Or does it mean that the object is locked for further editing by other methods/controls while the Plugin retains the lock?

Also I assume that if you lock a local variable without an unlock that this is potentially a memory leak?

Is there any runtime method that you can do to detect a missing unlock?

What happens if you accidently unlock an object which was already unlocked?

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>