Slow Prayer List
I have been using Logos 4 for Mac since Beta 1. The prayer list is extremely slow on my computer (a i7 MacBook Pro with 4 GB memory). Just moving the cursor over the prayer list causes a hesitation as you see the little 'delete' icon for each item move through all the items your cursor moved over. I was hoping the release version would fix this, but I hate to say that this feature is nearly unusable for me. If the import feature would have worked, it would be less of an issue, but trying to add my list of a couple hundred items is too painful. I just manually enter a few at a time until I get too frustrated to continue. PLEASE HELP!!!!
Eric Hatfield
Comments
-
Wonder about Prayer List performance with large lists using Logos 4.2a ?
Keep Smiling [:)]
0 -
No change! That's why I am so frustrated.
0 -
Eric,
As several of us have already suggested to you, the developers will need to see logs and more detailed information if they're to get to the bottom of this for you.
Mark
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
No offense here, but if Logos were interested in getting to the bottom of this as you say Mark.... Well Eric would not have been waiting over 4 months for a response, which did not come from Logos, but from one of the incredibly helpful forum members.
I can feel Eric's frustration... While Logos is genuinely working to make a great product, if something is not their priority; whether it is the users' priority or not; it IS pushed to the back burner. This is quite evident by the Logos requested user voice polls and to date we are still without quite a few of the most valued features from V3 that started with Q1 then Q2 then end of 2010 estimates and now a year later are estimated for Q2 of 2011....
If it is a project Logos has decided they want done first and there is an issue with it... They ARE very prompt with updates, corrections and optimizations. If not, well, it just sits around until it gets done...
If I had known from the start we'd be waiting up to 18 months or more depending on when PBB and Sermon File are completed from the start of Beta... I would have never made the investment from Leaders to Silver, may not have stuck around with Logos and that is the feeling of many that goes ignored on the forums or meet with criticism. As good as Logos is with Customer Service, it is also where there is a lot of lack in Customer Response, especially now with all the hassle for those who still have to use V3 for features they paid for that STILL have not been implemented for V4 and the fact that IE 9 brings issues for V3...
Then it is blamed on Microsoft by some.... Sorry it falls on Logos and Logos alone. When you are instructing users who need promised features to continue using an old version of your software that relies on a "fluid" software base like IE that has constant change and evolution to remain compatible with new technology, then you should be sure to assure that you keep the old version compatible with the changes or implement the features in the newest version. However we are instructed to use to Bible Study versions and now to not update our computers to the current manufacturer recommendations because the OS provider broke the Bible software... Logos is becoming a technology headache with all of the work needed and hassle to deal with just to keep promised functionality!
It was one thing during Beta testing, but to still feel like even stable releases are beta due to all the mess involved in trying to use key features is silly. There are a lot of unresolved issues that fall short of users who have invested a lot into this software that takes away features and functionality unless you give up your right to privacy, not update your computer and continue operating at least two bibles study versions....
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Hi Frank,
I'm not trying to suggest that Eric's problem is top priority for Logos Developers. However, the developers have frequently asked for logs and additional information for other users (not Eric) in the past to try and pinpoint problems like these, but often haven't received them. I know there's several minor irritations with L4, and when you rely heavily on a feature that is affected by a minor irritation, that very quickly become a major irritation, and occasionally a deal-breaker.
I'm not going to try and defend Logos, I understand your frustration. But one small correction: IE9 has not yet been officially released, it's still only in RC, and is specifically not recommended if "you get frustrated if software doesn't always behave as you expect it to".
Mark
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Hey Mark,
My point about Eric was that it was never addressed, logs were never requested and fell through the cracks. As for the IE 9 not being recommended, actually it is on the important update list for Microsoft Update, also the issue with IE 9 is not Microsoft Issue.... IE 9 works great, possibly the best IE release since 3.0 IMHO...
It is V3 not being updated or prepared for the release of IE 9. Some may say it is an old and maybe unsupported version (not that I have heard Logos voice that, at least that I remember) BUT Logos is still pushing people to use it for major functionality and features. Considering the Beta Release was public for a long time now and developers are always included then if not before the public again IMHO it should have been taken care of by Logos and not point the finger at Microsoft.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Frank Sauer said:
As for the IE 9 not being recommended, actually it is on the important update list for Microsoft Update,
I know it's on the important update list, but do check the link I posted above. There's mixed messages from Microsoft here.
Frank Sauer said:also the issue with IE 9 is not Microsoft Issue
Frank Sauer said:It is V3 not being updated or prepared for the release of IE 9.
Neither of those things are true, I'm afraid. First, the problem is that IE9 isn't compatible with IE8. To a certain extent that's to be expected, but it's certainly not Logos' fault. Second, Logos have not said that L3 is not being updated for IE9. As you know, there are two bugs in IE9 that are causing the current problems. It's reasonable for Logos to expect MS to fix those bugs, even though it's likely that they'll have to work-around them. But I doubt they're going to waste time trying to work around them until MS have confirmed whether or not they're going to fix them. Bradley reported those bugs on 16th February, and currently MS have yet to respond. I'm sure Bradley gets as frustrated with MS as you get with Logos!This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Have to disagree Mark... Microsoft may have a glitch or two effecting V3, however it is NOT their responsibility to troubleshoot every 3rd party application that relies on IE before they make an update. It is solely the 3rd Party Developers obligation to test and adapt their software to the new IE or OS version and while doing so reports any bugs in the Microsoft system to Microsoft. As for Logos never saying they weren't going to update V3 that was also stated in my post, 2nd portion of that point was that with developers having a head start on releases for testing purposes preparations could have been made... Maybe a blog post, email or something that would notify users who may not go on the forums...
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
And all this is relevant to Mac users because...
tootle pip
Mike
Now tagging post-apocalyptic fiction as current affairs. Latest Logos, MacOS, iOS and iPadOS
0
