CRASH Logos 8.2 Beta 3
Improvement in Notes means persistent crash in L8.2 Beta 3 when trying to add a note:
After upgrading to B3 I made a note and selected a blue-colored note marker to see the change advertised in the change notes: I expected this blue note marker to be used in the subsequent notes. Instead, I now have a persistent crash whenever I try to add a note.
This error will occur everytime I
- select text,
- hit right click and
- hit add a note
(I tried selected surface text in two or three resources as well as reference in a NIV bible), it always shows this error:
Error ID: 5053
Error detail: ServiceException: 'style' is invalid: 'indicator' is missing or empty.
ServiceException: 'style' is invalid: 'indicator' is missing or empty. (InvalidRequest)
at Facility.Core.ServiceResult.Verify()
at LDLS4.Panels.NotesTool.NotesToolViewModel.<CreateNotes>d__72.MoveNext()
Highlighting with a keyboard shortcut works, but doesn't break the above sequence.
Logs:
Have joy in the Lord! 
Comments
-
Hi NB.Mick,
I'm sorry your crashing. I'm not able to reproduce this, but I'm letting the team know so they can take a look.
0 -
I'm also getting consistent crashes when trying to create notes after the update.
0 -
Hi Jeromy,
Can you post your logs? I just want to make certain this is the same crash. Also what Note indicator and color are you trying to use?
0 -
Same thing is happening to me as well, right when I need my notes the most.
I hope I did this right.
Cliff
My Blog: Theological Musings
0 -
I can also confirm. Here's my log file: 3755.Logos.log
The error is:
Error ID: 7913
Error detail: ServiceException: 'style' is invalid: 'color' is missing or empty.This happens for me both when adding a note from the context menu as well as from the New Note button in the Notes Tool.
Clumsy Workaround:
Create a highlight (at least it works via a hotkey), then change the style/icon/anchors.
0 -
I've just tried this and it works fine for me.
I'm running on Windows 10 and I note that the two logs submitted are on Mac - so could be a Mac-specific problem.
0 -
After switching layouts (as well as creating a note from a WF (which didn't get the most recently used icon)) it's working for me!
0 -
Graham, NB.Mick also submitted logs and he's on Windows 10 so I don't think it's platform specific.
0 -
Reuben Helmuth said:
After switching layouts (as well as creating a note from a WF (which didn't get the most recently used icon)) it's working for me!
I don't really understand what you did with regards to layouts, but after testing I think I can add some more detail to it - and thus a way to solve the crash. The detailed error messages shared in this thread brought me to the solution.
I had changed the default note color, and got a crash message about an undefined indicator. Someone else got a crash message about an undefined color. However, the functionality works for a third person. So I deliberately changed color AND indicator in my last recent note - voila, now it works to add a new one!
It seems the developer forgot to initialize the variables that store the last-used-note-configuration - if someone then changes the note color and/or the note indicator icon, the respective variable is filled. However, if they change only one of those, the other one is left at default, i.e. the variable is undefined and Beta 3 crashes when the next "Add a note" is executed.
Once a change has filled both of the variables, the issue is over - noting that workflows add a note by pushing the default icon and default color, but not updating the variables for last-used-note-configuration. I suspect that you, Reuben, at one point changed both values and thus filed the variables.
EDIT: @Clifford B. Kvidahl, this should probably help you - at least if it works as I think it does.
Have joy in the Lord!
0 -
Reuben Helmuth said:
Graham, NB.Mick also submitted logs and he's on Windows 10 so I don't think it's platform specific.
Sorry - I missed that
0 -
NB.Mick said:
It seems the developer forgot to initialize the variables that store the last-used-note-configuration - if someone then changes the note color and/or the note indicator icon, the respective variable is filled. However, if they change only one of those, the other one is left at default, i.e. the variable is undefined and Beta 3 crashes when the next "Add a note" is executed.
Nice analysis[:)]
0 -
NB.Mick said:Reuben Helmuth said:
After switching layouts (as well as creating a note from a WF (which didn't get the most recently used icon)) it's working for me!
I don't really understand what you did with regards to layouts, but after testing I think I can add some more detail to it - and thus a way to solve the crash. The detailed error messages shared in this thread brought me to the solution.
I had changed the default note color, and got a crash message about an undefined indicator. Someone else got a crash message about an undefined color. However, the functionality works for a third person. So I deliberately changed color AND indicator in my last recent note - voila, now it works to add a new one!
It seems the developer forgot to initialize the variables that store the last-used-note-configuration - if someone then changes the note color and/or the note indicator icon, the respective variable is filled. However, if they change only one of those, the other one is left at default, i.e. the variable is undefined and Beta 3 crashes when the next "Add a note" is executed.
Once a change has filled both of the variables, the issue is over - noting that workflows add a note by pushing the default icon and default color, but not updating the variables for last-used-note-configuration. I suspect that you, Reuben, at one point changed both values and thus filed the variables.
EDIT: @Clifford B. Kvidahl, this should probably help you - at least if it works as I think it does.
Hi NB.Mick,
Thanks for the additional information, I've updated our case.
0 -
-
Changing the note color & icon of my last created not solved my crashing issue. Thanks0
-
Jeromy Waunch said:
Changing the note color & icon of my last created not solved my crashing issue. Thanks
Does creating a note by filling in a workflow observation field work for you?
if so, does it help changing this note's color and icon and then adding a new one?
Have joy in the Lord!
0 -
Sorry, that was a typo. Should have read "creating a note solved my crashing issue" [:$] It's working now.
0 -
-
I am crashing when trying to scroll down in a Bible.
0 -
John Brumett said:
I am crashing when trying to scroll down in a Bible.
Hi John,
I'm sorry you are crashing. Please create a new thread, provide steps on how to reproduce this. Please inlcude information like what Bible and reference you are at. It also helps to know what your program scaling is set to and if you have anything else in a link set. We also need your logs.
Thanks,
Philana
0 -
-
0
-
0
-
NB.Mick said:
Improvement in Notes means persistent crash in L8.2 Beta 3 when trying to add a note:
After upgrading to B3 I made a note and selected a blue-colored note marker to see the change advertised in the change notes: I expected this blue note marker to be used in the subsequent notes. Instead, I now have a persistent crash whenever I try to add a note.
This error will occur everytime I
- select text,
- hit right click and
- hit add a note
(I tried selected surface text in two or three resources as well as reference in a NIV bible), it always shows this error:
Error ID: 5053
Error detail: ServiceException: 'style' is invalid: 'indicator' is missing or empty.ServiceException: 'style' is invalid: 'indicator' is missing or empty. (InvalidRequest)
at Facility.Core.ServiceResult.Verify()
at LDLS4.Panels.NotesTool.NotesToolViewModel.<CreateNotes>d__72.MoveNext()Highlighting with a keyboard shortcut works, but doesn't break the above sequence.
Logs:
This crash should be fixed in 8.2 RC 1.
0 -
Philana R. Crouch said:NB.Mick said:
Improvement in Notes means persistent crash in L8.2 Beta 3 when trying to add a note (...)
This crash should be fixed in 8.2 RC 1.
Thanks! I won't be able to test that, but appreciate the fix.
Have joy in the Lord!
0
