feedback master button states not being inherited by feedback layers

This is a long standing problem.  I posted about it earlier in this thread as have others.  I barely use any master slide  or feedback master functionality now, except for choosing a background colour on the 'blank' master slide. Occasionally I might place some triggers to manage variables  on there if I have a course wide counter or status indicator happening.

I also create original button graphics outside of SL in a graphics program, 1x .png for each state, then  import and assemble them in to button states inside SL. Doing this so  SL doesn't corrupt the design I'm looking for by replacing one of my states with one of its hard coded variants. (Although it still manages to occasionally delete the "visited" state and replace it with something unwanted of its own making.  Therefore I tend to not use the 'visited' state in any interactions....visited can also become problematic when attempting to use together with 'selected' - another story...)

I then copy/paste these custom buttons onto every screen that needs them so they can receive the right triggers...the problem you have so well described Dianne.

All of this, unfortunately, means we miss out on having a powerful and reliable master page based workflow.