Copy Verses no longer allowing separate verses - A request for the old behavior

Page 1 of 1 (3 items)
This post has 2 Replies | 1 Follower

Posts 73
Paul Johnson | Forum Activity | Posted: Thu, Jul 1 2010 8:46 PM

There were two recent posts that objected to Copy Verses rearranging verses in canonical order rather than in the order in which they are entered. My issue may be related to that one; however, I thought it worthwhile to make my specific request as well. (BTW, if there is a better way to communicate feature requests, please let me know.)

My issue is this. Prior to 4.0d, I could enter the following in the entry field for Copy Verses: 1 Pet 2:19, 20-23, and Copy Verses would give me two results: (1) 1 Pet. 2:19 by itself, and (2) 1 Pet. 2:20-23 as a separate result. (This was my intention by entering it the way I did, with the comma between vv. 19 and 20.)

Now, the same entry as above yields only one result: 1 Pet 2:19-23 as a combined entry.

Further, if I enter 1 Pet 2:19; John 14:6; 1 Pet 2:20-23 (trying to break up the 1 Pet. entries) I still only get two results: (1) John 14:6 (note canonical order), and (2) 1 Pet 2:19-23 (note combined result, rather than separate as entered).

In my opinion, the new behavior is not an improvement. Strange as it may be, we users might have reasons for entering things the way we do, and it would be nice if the software let us do it, rather than second guessing what we really want. At a minimum, it would be nice if we had the option of choosing how we wanted Copy Verses to work---the way it now does or the way it used to.

(BTW, over all, I am pleased with the other changes brought in with 4.0d!)

Posts 32926
Forum MVP
MJ. Smith | Forum Activity | Replied: Thu, Jul 1 2010 8:53 PM

BTW, if there is a better way to communicate feature requests, please let me know.)

Suggestions does have its own forum and its own site

Orthodox Bishop Hilarion Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."

Posts 9134

This will be fixed in version 4.1 (and, specifically, the fix will be in the next beta).

Page 1 of 1 (3 items) | RSS