CRASH: 5.1b: Press down-arrow in Program Settings when dropdown has focus

Rosie Perera

Open Program Settings

Press <Tab> twice (to get focus into "At startup open to" dropdown.

Press <Down Arrow>

Result: Logos Crashes

Log files attached.

LogosCrash L5.1b 20130927.zip

Find more posts tagged with

Comments

Jack Caviness

Could not confirm this in L5 Mac.

Selected "At startup open to" manually, then pressed the down arrow. Nothing happened. Apparently, the tab and arrow keys are disabled in Program Settings of the Mac version.

Ben

https://community.logos.com/discussion/comment/529984#Comment_529984

my works fine. l5.1b running on windows 8.

Martin Grainger Dean

https://community.logos.com/discussion/comment/529988#Comment_529988

I can confirm the bug (Win 7, 5.1b (5.1.2.0020) when trying multiple times to switch from Home to Most recent layout - local. Error ID: 2842
Error detail: WpfBindingException: System.Windows.Data Error: 8 : Cannot save value from target back to source. BindingExpression:Path=Value; DataItem='StartupLayoutOptionPreference' (HashCode=60599278); target element is 'ComboBox' (Name=''); target property is 'SelectedItem' (type 'Object') ArgumentException:'System.ArgumentException: exactly one of startupLayoutOption or namedLayoutTitle must be null, and exactly one must be non null ~ at LDLS4.StartupLayoutOptionSetting..ctor(Nullable`1 startupLayoutOption, String namedLayoutTitle) ~ at LDLS4.NamedPreferences.StartupLayoutOptionPreference.SetValueCore(String value) ~ at LDLS4.NamedPreference.set_Value(String value)'

Angela Murashov

Result: Logos Crashes

I can reproduce this on Windows in 5.1b, and I have created a case for Development.

fgh

https://community.logos.com/discussion/comment/529984#Comment_529984

Angela, did you also notice the feature parity issues?:

Could not confirm this in L5 Mac.

Selected "At startup open to" manually, then pressed the down arrow. Nothing happened. Apparently, the tab and arrow keys are disabled in Program Settings of the Mac version.

Angela Murashov

https://community.logos.com/discussion/comment/530206#Comment_530206

Angela, did you also notice the feature parity issues?:

Yes I did notice the feature parity issue, however it is by design for Mac because Mac does not support it.

fgh

https://community.logos.com/discussion/comment/530212#Comment_530212

Ah! Thanks for letting us know.

Rosie Perera

https://community.logos.com/discussion/comment/530019#Comment_530019

my works fine. l5.1b running on windows 8.

I can confirm the bug (Win 7, 5.1b (5.1.2.0020)

Yes, I should have mentioned that I was running Win 7. Apparently it doesn't happen on Win 8, but I'm glad to see it confirmed on Win 7. This sort of thing is why using different configurations is important in internal testing.

I can reproduce this on Windows in 5.1b, and I have created a case for Development.

Thanks, Angela.

Dylan Rondeau

https://community.logos.com/discussion/comment/530230#Comment_530230

This should be fixed in 5.2 Beta 1.