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

Tim Hensler
Tim Hensler Member Posts: 1,547 ✭✭✭

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.

Comments

  • Jack Caviness
    Jack Caviness MVP Posts: 13,625

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

    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.

    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.

  • Angela Murashov
    Angela Murashov Member Posts: 1,532 ✭✭✭

    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. 

  • Jack Caviness
    Jack Caviness MVP Posts: 13,625

    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 [:P]