-
Weird, I just shutdown and restarted Logos and the custom reading plan i made which I couldn't add to the dashboard has now appeared on my dashboard without me adding it to the dashboard!
-
The custom reading plan I created with Logos for Windows does note appear as a reading plan I can add as a card to the dashboard of the windows app but I have already been able to add the same reading plan to the dashboards of both my iPhone and iPad Logos apps.
-
Yep, I have the same problem. I can create a custom reading plan but am unable to add it to the dashboard via the "+" i.e. my custom reading plan does not appear in the list of reading plans to add to the dashboard.
-
more like "Retrograde"
-
TOTALLY AGREE!!! FULL OFFLINE SUPPORT should be a PRIORITY. The new iPad Pros can easily accommodate a full version of the Logos bible app; from the APPLE WEBSITE Video mirroring and video out support: Up to 4K through the USB-C Digital AV Multiport Adapter and USB-C VGA Multiport Adapter (adapters sold separately)
-
Yep same for me. I can no longer see previews of custom highlighting. Surely this is a regression if not it is a major regression and renders custom highlighting next to unusable.
-
Yep I hope they fix this soon.
-
Disabling the Explore section should have been available from day dot. It's a tossup. LOGOS remove the Explore bloat on the home page or my temptation to remove LOGOS might pass the tipping point.
-
Absolutely agree. Having to pay to suck eggs is indicative of a product that has lost the point and purpose of its existence, to make biblical studies enjoyable, quick and productive. These days I use Logos for referencing large data sets but the joy has long gone in Sermon notes that are cumbersome rather than intuitive. Notes that are just a pain
-
Ditto
-
Agreed. And where in the fine print does it mentions this is an online only tool for generating output. When backgrounds for slides are configured they are not pulled down off the internet and stored locally on you computer so you have to be online to export the sermon slides.
-
Ditto for me. OS X 10.10.1 Logos Bible Software 6.0a 6.0.1.0032
-
Here's my PMSET output on Mac OS X 10.8.4 Logos Bible Software 5.1 SR-3 (5.1.0.0979) Active Profiles: Battery Power 1 AC Power -1* Currently in use: womp 1 autorestart 0 halfdim 1 sms 1 hibernatefile /var/vm/sleepimage gpuswitch 2 networkoversleep 0 disksleep 0 sleep 0 hibernatemode 3 ttyskeepawake 1 displaysleep 10 acwake 0 lidwake 1 Have not experienced
-
[quote user="alabama24"] I think how someone would rate Logos attentiveness to "fixing bugs" would depend upon what "bugs" them most, and what bug fixes they notice being fixed. I am a beta tester for the iOS apps and have generally seen things fixed very quickly. Most of the things that I want "fixed" aren't bugs, but things that aren't designed how
-
Yeah design & aesthetics are not the same as stability but they often go hand-in-hand. I.e. Well designed product = good stability.
-
This bug has been reported to Logos in a live hookup with them almost a year ago. In the ensuing discussion the person on the other end of the hookup admitted Logos had been aware of the "problem" for "quite some time". Personally I am more a shade of "disappointed." There have been genuine "improvements" in Logos4Mac. Stability has improved from a
-
Clarification: the images I refer to in my example are the default Logos images supplied under "right click on a style" Edit ➤Image. In any case custom or default images make no difference. The result is the same. The formatting errors also occur when leading label text is added to a style with ➤Label Text. See example below (the three arrowed images
-
Here is another example I cooked up in 5 minutes with a random book selected and a completely new custom palette which has one style. This style has an image set to lead the text being highlighted with this style. The image has been selected from the default image pulldown list under edit style options. As you can see from the test case below this generates
-
Custom highlighting palette.
-
And what is a reasonable time frame for bug resolution, 6 months, 1 year, 2 years, or more......?