Followup:
It turns out that this problem is directly related to having opened
the Virtual Volume twice. Folks might be interested in discussing
what the proper solution to this is. My first thought was that if it
turns out that if RS has to make it so that only one copy of the
class has write permission into the virtual volume, then they
probably should add a read/write parameter into the
openAsVirtualVolume method (just like for openAsBinaryStream), and a
similar property for the class itself. That way, when you open the
volume you could check to see if you actually got write permission
you requested.
Thoughts?
-Eric
--
______________________________________________________________________
Eric Harris-Braun eric at glassbead dot com
Glass Bead Software http://www.glassbead.com
---
A searchable archive of this list is available at:
<http://dbserver.realsoftware.com/KBDB/search.php>
Unsubscribe:
<mailto:realbasic-betas-off at lists dot realsoftware dot com>
Subscribe to the digest:
<mailto:realbasic-betas-digest at lists dot realsoftware dot com>
.
|