Bugs still NOT fixed in Logos 8.3 & Bug tracker ?
Is there some sort of publicly viewable list of known bugs in Logos 8? There are a couple bugs in Logos 8 notes that I have posted on twice since release, with the second post not even receiving an acknowledgement of any sort. These are minor bugs, I admit, and as a Mac user I am probably still a part of a very small percentage of Logos users, but these bugs impact me daily. If there is some place that I can check on them and see that they are on a list to be resolved I would quit being the squeaky hinge here. :-)
Here are the bugs (again) that remain unaddressed in 8.3:
Previous functionality prior to the update included several Mac keyboard shortcuts that are no longer in the app however the wiki still shows these as options:
[cmd] + [.] to form bullet list
[cmd] + [/] to form numbered list
[cmd] + [ [ ] to indent list
[cmd] + [ ] ] to decrease indent
c.f. https://wiki.logos.com/Keyboard_Shortcuts_For_Mac
https://community.logos.com/forums/p/174188/1006236.aspx#1006236
https://community.logos.com/forums/p/177376/1025262.aspx#1025262
*edit: updated title for clarity
Comments
-
Previous functionality prior to the update included several Mac keyboard shortcuts that are no longer in the app however the wiki still shows these as options:
This is not just a mac issue, I also noticed this bug on Windows 10. Some things got fixed, and some things got broken...
0 -
[cmd] + [.] to form bullet list
Just use a "-" followed by a space.
[cmd] + [/] to form numbered list
Type the first number then a "." followed by a space.
[cmd] + [ [ ] to indent list
[cmd] + [ ] ] to decrease indent
c.f. https://wiki.logos.com/Keyboard_Shortcuts_For_Mac
https://community.logos.com/forums/p/174188/1006236.aspx#1006236
https://community.logos.com/forums/p/177376/1025262.aspx#1025262
*edit: updated title for clarity
Not sure about the last two but the wiki does need to be updated.
0 -
David, thank you for taking the time to respond. You remain thus far also the only person apart from Michael now to comment on this issue (now twice) however I am going to have to still disagree with you. This is not simply a matter of updating the wiki. This is a matter of Logos intentionally or unintentionally removing previous long running functionality. For the Mac, for as long as there has been a dedicated Mac Logos client (not counting the Libronix crossover), which I believe is as far back as L4, released in 2010, this keystroke has been the strokes that are on the wiki. That is many years of habit and specific functionality that has been changed/removed without documentation.
There was a similar problem last year when the beta of the faithlife assistant was added to the application where the keystroke for apply default formatting was incorrectly associated with the assistant. https://community.logos.com/forums/p/147230/938718.aspx#938718 When I brought that to their attention they did respond and restore the key command to its original use. It is my hope that there is something similar going on here, and that this is not just a matter of a new developer overturning years of a specific functionality. That is completely aside from the fact that intentionally or unintentionally, the key commands remain mirrored to that of MS PPT on the Mac (which are not the same as MS WORD, so much for consistency on their part) which makes it additionally convenient not to have to have different muscle memory for each application i use. However that is a much more minor argument than the other, that of 9, almost 10 years of continuity.
I will admit a certain amount of disappointment that with three posts across 4 months regarding this issue there has not been a single response from Faithlife's developers or forum moderators either acknowledging the issue or at least indicating that they have intentionally changed the keystrokes, which is why I asked about a bug tracker, a tool used by some other software development companies to help stave off these kinds of questions.
*edited for clarity
0 -
Is there some sort of publicly viewable list of known bugs in Logos 8? There are a couple bugs in Logos 8 notes that I have posted on twice since release, with the second post not even receiving an acknowledgement of any sort. These are minor bugs, I admit, and as a Mac user I am probably still a part of a very small percentage of Logos users, but these bugs impact me daily. If there is some place that I can check on them and see that they are on a list to be resolved I would quit being the squeaky hinge here. :-)
Here are the bugs (again) that remain unaddressed in 8.3:
Previous functionality prior to the update included several Mac keyboard shortcuts that are no longer in the app however the wiki still shows these as options:
[cmd] + [.] to form bullet list
[cmd] + [/] to form numbered list
[cmd] + [ [ ] to indent list
[cmd] + [ ] ] to decrease indent
c.f. https://wiki.logos.com/Keyboard_Shortcuts_For_Mac
https://community.logos.com/forums/p/174188/1006236.aspx#1006236
https://community.logos.com/forums/p/177376/1025262.aspx#1025262
*edit: updated title for clarity
Hi Tim,
We do have a case to add various shortcuts to the Notes Tool. I've added these to the case and a link to this thread. I'm sorry for the lack of response.
0 -
thank you very much for responding. I am very glad to hear that there is still a plan to restore these.
0 -
We do have a case to add various shortcuts to the Notes Tool.
I am still curious as to why this functionality was removed in the 8.3 update. It was working right before that update and now it is not. Was it removed intentionally in 8.3?
0 -
It appears that Logos 8 is a complete rewrite. Therefore it's not that programmers took out working code, but rather that the code for these features has not been written yet. (Just my guess.)
0 -
It appears that Logos 8 is a complete rewrite. Therefore it's not that programmers took out working code, but rather that the code for these features has not been written yet. (Just my guess.)
What I mean is that these things still worked in 8.2. But not in 8.3. In fact I was doing a note just a few hours before the update and I was using the short cut keys mentioned. Then after it they didn't work anymore. I thought I was going crazy, or my keyboard was getting broken...
0 -
Is there any chance we might get an update on the status of this issue? It has been 10 months and several patches both large and small with no fixes incoming.
0 -
[Y]
0 -
Over a year later and many maintenance updates later and still nothing, and no comment. Has this issue been lost over time?
0 -
Over a year later and many maintenance updates later and still nothing, and no comment. Has this issue been lost over time?
It means that the folks who write this software are not using it. Otherwise it would have been fixed long ago.
0 -
It also means that should this issue still be in the bug tracker as indicated 15 months ago by @Philana R Crouch, and approaching 2 years ago from its insertion into Logos, either this problem has been been given absolute bottom priority or abandoned entirely.
I keep posting here in hopes that some day this squeaky wheel might actually get some attention. I agree that there are likely to be few Logos for Mac users at Faithlife who depend upon notes to the degree that so many of us do in our daily work.0 -
It also means that should this issue still be in the bug tracker as indicated 15 months ago by @Philana R Crouch, and approaching 2 years ago from its insertion into Logos, either this problem has been been given absolute bottom priority or abandoned entirely.
Evidence does not support this logic - there are bugs that are much older than two years. It may mean any of the following:
- the fix requires considerably more effort to repair than appears to external users
- the code is rarely modified so there has been no opportunity to fold it into another patch
- the priority is low because (a) the number of users affected is small, or (b) the side effects of the error are minimal, or (c) it's priority is mid-range but it keeps getting pushed down in the queue by new problems that crash the system or render a feature unusable.
- an example of a problem that has absolute bottom priority is the handling of the references to the first verse of Greek Esther in the NJB (IIRC) -- why? because what is a chapter in other translations is a single verse; What are verses in other translations are labeled with letters a, b, c, z, ... Yes, it is annoying at times but in general the system handles the anomaly well but even I don't want FL to squander their resources on such a specific problem ... what I want is for them to have it noted as a problem and should they ever be redesigning the access module, that they given consideration in their new code for translations that have unique issues like the NJB.
So, yes, there is a small possibility that "this problem has been been given absolute bottom priority or abandoned" but it isn't the most likely explanation.
I keep posting here in hopes that some day this squeaky wheel might actually get some attention.
This is exactly the right thing to do ... and encourage others to do so as well.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
I keep posting here in hopes that some day this squeaky wheel might actually get some attention.
[Y]
0
