BUG: Layout and layout name don't match when launching Logos after a crash. WIN 6.10 Beta 3 (6.10.0.0017)

Page 1 of 1 (4 items)
This post has 3 Replies | 2 Followers

Posts 927
Tim Hensler | Forum Activity | Posted: Sun, Feb 21 2016 9:00 PM

After Logos crashes, and you restart the application, the layout name at the top of the window indicates the name of the layout you were using when it crashed (probably more accurately, last saved), but the layout is not the same and does not go with the layout name. I realize that Logos does not have time to save anything when it crashes, but before I realized this I saved the wrong layout to the selected layout name.

The layout name should reflect the layout that is being loaded, or there should not be a layout name associated with the layout loaded after a crash so that it does not overwrite the wrong layout when saved.

Posts 10850
Forum MVP
Jack Caviness | Forum Activity | Replied: Mon, Feb 22 2016 4:22 AM

Thanks for this bug report. I have noted this, but have not taken the time to create a bug report.

Tim Hensler:
the layout name at the top of the window indicates the name of the layout you were using when it crashed (probably more accurately, last saved), but the layout is not the same and does not go with the layout name.

Usually it seems to be a mixture of the last few layouts. IOW, a mess.

Tim Hensler:
there should not be a layout name associated with the layout loaded after a crash

This would be my recommendation, and it should be fairly painless to implement.

Posts 1471
Angela Murashov | Forum Activity | Replied: Tue, Feb 23 2016 10:51 AM

Tim Hensler:
The layout name should reflect the layout that is being loaded, or there should not be a layout name associated with the layout loaded after a crash so that it does not overwrite the wrong layout when saved.

Thanks for the report! I will create a case to get this fixed. 

Posts 10850
Forum MVP
Jack Caviness | Forum Activity | Replied: Tue, Feb 23 2016 4:04 PM

Angela Murashov:
Thanks for the report! I will create a case to get this fixed. 

Thank you, Angela. This has actually been a rather long-term bug, but it has become even more jumbled with 6.10. Leaving my update channel set to Beta, and trying to duplicate other user's crashes, gives me ample opportunity to see this bug in action Stick out tongue

Page 1 of 1 (4 items) | RSS