You might want to store the versification alongside it if you're working across
multiple modules.
-Original Message-
From: Troy A. Griffitts scr...@crosswire.org
Sent: 01/03/2015 08:19
To: SWORD Developers' Collaboration Forum sword-devel@crosswire.org;
Daniel Sheffield
Hi Daniel, the most concise way to store an SWKey is to store the string from:
SWKey::getOSISRefRangeText
This should return OSIS (or something close to OSIS) and include any range is
present, as well.
SWKey::Index is certainly not persistable. It might change between API versions
and almost
On March 1, 2015 12:53:25 AM EST, Greg Hellings greg.helli...@gmail.com wrote:
David,
It's most common to pass it around as a pointer, that way you're
guaranteed that there's only a single instance and you don't incur
overhead from allocating on the stack
So can I change my member properties
