Selecting verses to copy

Page 1 of 1 (10 items)
This post has 9 Replies | 1 Follower

Posts 191
Jacques | Forum Activity | Posted: Sun, Feb 8 2015 2:03 PM

I'm trying to highlight to verses using Logos 6 for Mac. Phi. 2:12-13.

When dragging over it, I can select both verses .. but when I let go, it grabs MANY more verses. Surely a bug.

Has anyone figured out a work-around?

thanks

Posts 29373
Forum MVP
JT (alabama24) | Forum Activity | Replied: Sun, Feb 8 2015 2:16 PM

Jacques:
Surely a bug.

Yep.

Jacques:
Has anyone figured out a work-around?

See this thread: https://community.logos.com/forums/t/100360.aspx 

macOS, iOS & iPadOS | Logs |  Install

Posts 191
Jacques | Forum Activity | Replied: Sun, Feb 8 2015 3:20 PM

Thanks, read the thread. For now, until the bug fix populates to stable releases, it's an easy fix. Just set Logos to the beta channel (as the fix is there), then after that upgrade reset the channel back to stable or default.

How to do this here: https://wiki.logos.com/The_Logos_6_Beta_Program

Posts 24665
Forum MVP
Graham Criddle | Forum Activity | Replied: Sun, Feb 8 2015 3:23 PM
For those who are considering joining the beta programme please read the warnings at https://community.logos.com/forums/t/52967.aspx
Posts 24665
Forum MVP
Graham Criddle | Forum Activity | Replied: Sun, Feb 8 2015 3:28 PM
Apologies about the non-active link above, an issue with my iPad browser at the moment
Posts 191
Jacques | Forum Activity | Replied: Sun, Feb 8 2015 3:30 PM

In this case, a few people have gone to the beta channel simply to get this bug fixed. See the thread mentioned above. The user felt it was overall very stable, in this case.

This is why after letting the latest beta download, going straight back to the stable or default channel is suggested. This way, the version does not update until the next stable or default release.

I think the real question is: why would this bug sit fixed in beta channel only? I would imagine it warrants an immediate fix to the stable channel.. this is such a basic feature, copy paste.

I'm glad to have found a solution, thanks for pointing me to the thread alabama24.

Posts 19229
Rosie Perera | Forum Activity | Replied: Sun, Feb 8 2015 4:43 PM

Jacques:
I think the real question is: why would this bug sit fixed in beta channel only? I would imagine it warrants an immediate fix to the stable channel.. this is such a basic feature, copy paste.

The beta channel is essentially the pre-release phase of the stable channel. New releases cannot be pushed out to stable until they've been through the whole beta testing cycle. There is a slight risk that in introducing some of the changes during the beta testing phase (even if it's just to fix bugs), something else might have gotten broken. The point of giving it some time in the beta stage before going "gold" (stable release) is to make sure anything else like that is discovered and to fix any other bugs that were waiting to be fixed in this release before making all the people who are "stable channel ever and only" deal with another program update.

I agree, though, that this one could have warranted doing a Service Release, which is a minor update to implement one or two safe bugfixes, that bypasses the beta phase (or piggybacks off of the parallel testing that's going on in the beta version).

Posts 191
Jacques | Forum Activity | Replied: Sun, Feb 8 2015 6:54 PM

When I permitted the beta update, it asked me many times if I would like to update etc. I think I accepted one too many times.

Turns out my entire Logos install was botched!

I erased all and tried to install from the latest beta 5 engine, it fails for me. So I'm back to installing the default download and I'm going to set the update path back to stable as soon as possible. =)

Go figure, the one time I need the update (I've used Logos betas plenty over the past few years) for a serious bug squash, I simply have no access to it. 

I'll end up waiting this one out, for the stable release fix.

Thanks for the help.

Posts 162
LogosEmployee
Chris Culy (Faithlife) | Forum Activity | Replied: Mon, Feb 9 2015 8:43 AM

Rosie Perera:

The beta channel is essentially the pre-release phase of the stable channel. New releases cannot be pushed out to stable until they've been through the whole beta testing cycle. There is a slight risk that in introducing some of the changes during the beta testing phase (even if it's just to fix bugs), something else might have gotten broken. The point of giving it some time in the beta stage before going "gold" (stable release) is to make sure anything else like that is discovered and to fix any other bugs that were waiting to be fixed in this release before making all the people who are "stable channel ever and only" deal with another program update.

I agree, though, that this one could have warranted doing a Service Release, which is a minor update to implement one or two safe bugfixes, that bypasses the beta phase (or piggybacks off of the parallel testing that's going on in the beta version).

Rosie is correct. We wanted to ship the fix for this issue in a beta to make sure it fixed the issue on users' machines and didn't cause any other issues. We will be shipping this fix in an SR shortly (hopefully later today) to the stable channel. Thanks for your patience with this.

Posts 19229
Rosie Perera | Forum Activity | Replied: Mon, Feb 9 2015 2:47 PM

This fix has been released to the stable channel now in 6.0b SR-3: https://wiki.logos.com/Logos_6.0b_SR-3 

Page 1 of 1 (10 items) | RSS