Bug: Picking up a non-local Layout as Active

My Laptop (Stable) opened Logos to a Desktop layout as below: (jpg as gif does not work)

Both systems startup to a Local layout.

The absence of a local App Closed layout for Laptop is somewhat bizarre. [but note the one dated Sat 9:18pm. EDIT: it is local to Laptop Beta)]

The last action I had performed was Update to current snapshot against Laptop 5.A, so it seems reasonable that the Laptop 5.A layout should have been opened in these circumstances.

Here's the Desktop Layouts:

And here's the Laptop (Beta) - opened after saving Laptop 5.A layout at 0807 on Laptop (Stable)

Why is App Closed @ 0739 Sunday local to Laptop (Beta) and Desktop?

Why is Laptop 5.A @ 0802 Yesterday missing from Laptop (Beta)?

Find more posts tagged with

Comments

Dave Hooton

This isn't going away, folks.

My Laptop (Stable) just picked up a layout Laptop Beta from my beta installation in similar circumstances i.e. a non-local layout.

JT (alabama24)

https://community.logos.com/discussion/comment/489873#Comment_489873

This isn't going away, folks.

I have had similar problems in the past (during this beta cycle), where my iMac or MacBook would pick up the other one's layout… I ended up deleting all of my layouts and starting over with computer centric names (was not a big deal for me), and have not experienced this recently since. If it happens again, I'll will let you know.

JT (alabama24)

https://community.logos.com/discussion/comment/489874#Comment_489874

If it happens again, I'll will let you know.

Well, it did today! In the screen shot, notice that the layout is titled "iMac Basic"... the problem is that my layout from my MacBook opened instead. Also notice the warning in the screen shot. This was a personal book that I was creating on my laptop! It has never been opened on my desktop.

Here is what my preference is set to:

I'm in a huge hurry... Hopefully the logs are right:

2845.LogosLogs.20130517-150400.zip

kelly.flones

There is an active case for this issue, I have added a link to this thread.

JT (alabama24)

https://community.logos.com/discussion/comment/490819#Comment_490819

Here are some more logs Kelly:

7127.LogosLogs.20130612-081222.zip

The first screen shot is what loaded. The second screen shot is the layout it should have loaded.

Angela Murashov

Why is App Closed @ 0739 Sunday local to Laptop (Beta) and Desktop?

Why is Laptop 5.A @ 0802 Yesterday missing from Laptop (Beta)?

This will be fixed in 5.1a Beta 1.

Dave Hooton

https://community.logos.com/discussion/comment/489873#Comment_489873

This isn't going away, folks.

My Laptop (Stable) just picked up a layout Laptop Beta from my beta installation in similar circumstances i.e. a non-local layout.

This situation repeated as Beta 2 picked up a recent Stable (non-local) layout and name because, presumably there was no local App Closed layout for the Beta. But there was an older (local) Beta Layout from July 12!

Seth Copeland

https://community.logos.com/discussion/comment/509558#Comment_509558

This situation repeated as Beta 2 picked up a recent Stable (non-local) layout and name because, presumably there was no local App Closed layout for the Beta. But there was an older (local) Beta Layout from July 12!

I'm not exactly sure what the problem still is. But maybe if I give some details as to what happened to cause the earlier issues, and how we've fixed them it would help.

We only ever show 10 application closed layouts. When a new one is created, we would overwrite the data for the oldest one on your machine. The problem with this was what if you didn't have time to sync up that change, and on your other machine, when it shut down it also overwrote the same last one. This caused a conflict on the server, and it would simply pick the latest date of the layout. So your last local app closed layout, for the machine who shutdown earlier was lost.

So to make sure that didn't happen again, each local machine will have 10 application closed layouts, but only the newest 10 from all the layouts from all synced machines will every be available in the layouts menu.

The image not being displayed, or displayed wrongly, has to do with the fact we simply don't sync the image, so during conflicts, and other things, we may not have deleted the stale image, or deleted a stale image but the conflict didn't provide the right image.

Does that answer any questions?

Regards,

Seth

Dave Hooton

https://community.logos.com/discussion/comment/509743#Comment_509743

I'm not exactly sure what the problem still is. But maybe if I give some details as to what happened to cause the earlier issues, and how we've fixed them it would help.

The issue I'm reporting is the one illustrated in my first post, which was ignored as a bug. There is no local App Closed to use so a non-local one is used instead, giving me an inappropriate layout. A named local layout is available (from July 12) but why wasn't it used as per my Setting?

Seth Copeland

https://community.logos.com/discussion/comment/509747#Comment_509747

The issue I'm reporting is the one illustrated in my first post, which was ignored as a bug. There is no local App Closed to use so a non-local one is used instead, giving me an inappropriate layout. A named local layout is available (from July 12) but why wasn't it used as per my Setting?

That is a good point and does seem like a bug. I'm guessing the assumption was "last local", mean last local application closed layout, which can be nothing if it has been deleted via sync on a different client. I'll have to investigate more to find out what the right solution is.