Thank you for the post.
I am able to replicate with FileMaker Pro 13.0v5 (Advanced) with both Mac OS X and Windows clients. Additionally, I forwarded a report to Testing and Development for review.
Not really surprised to read this. Even without this issue, it's important to keep in mind that any update of a "live" database might catch one or more users "between stools". (And yes, I do these same updates to live systems all the time also.)
An entry in the Known Bugs List has been linked to this Issue Report. Any Comments/Questions/Suggested Corrections should be posted here or in a new thread. Please do not post such comments to the Known Bugs List thread.
Even though everybody knows that it is not recommended to do live updates, I have been doing minor adjustments live without issues for years and it is clearly allowed by FM Inc. In fact, it one of the many strengths of FileMaker, imo.
In this case I am using slide panels to automatically select the proper panel for a specific task upon layout entry and it is very confusing for users to be thrown out of their familiar interface without warning. For most users it is like hitting a wall. I would thus consider it a serious flaw.
Since no script triggers are firing when this occurs, it is impossible to handle it other than put up buttons everywhere to "reset" the layout. Seems very clumsy.
Thank you for the reply.
Testing and Development replied with the following feedback:
“Saving a layout hosted server side will force the layout on client side to reload. This action resets the slide control to show the default panel. This is the same behavior as with a tab control.”
The current behavior is a design limitation. If this behavior causes confusion for the end users, then the recommendation would be to duplicate the layout to make changes in lieu of developing on the layout while in production.