01-09-2017, 10:04 AM
Dominic,
I'm really struggling to figure out why the application is behaving that way on your machine. I just tested everything you described on my PC, and it worked fine. I'm going to test again on my Surface Pro 4 with a release build, but I'm willing to bet it will work fine there too (otherwise I would have seen these issues earlier). One thing that will probably help me is if I can get a copy of either your settings files or a library backup so I can test with the same library as you.
Even if I did find a way to reproduce this issue and pushed out an update, Microsoft won't approve the update that quickly. It usually takes them at least one day to approve an update. I'm sorry I wasn't able to get this addressed for you in time, but it's difficult to fix a problem I can't reproduce.
Thanks,
Mike
I'm really struggling to figure out why the application is behaving that way on your machine. I just tested everything you described on my PC, and it worked fine. I'm going to test again on my Surface Pro 4 with a release build, but I'm willing to bet it will work fine there too (otherwise I would have seen these issues earlier). One thing that will probably help me is if I can get a copy of either your settings files or a library backup so I can test with the same library as you.
Even if I did find a way to reproduce this issue and pushed out an update, Microsoft won't approve the update that quickly. It usually takes them at least one day to approve an update. I'm sorry I wasn't able to get this addressed for you in time, but it's difficult to fix a problem I can't reproduce.
Thanks,
Mike