miketisdell Posted January 6, 2019 Share Posted January 6, 2019 I had the LXX-GNT chosen in the bottom window and then switched to the DSS-C; doing so switched the text but not the version name in bar. Link to comment Share on other sites More sharing options...
Matt Robertson Posted January 7, 2019 Share Posted January 7, 2019 Thanks Mike, I'll look into this. Incidentally, is the screenshot from a Chromebook? Link to comment Share on other sites More sharing options...
miketisdell Posted January 8, 2019 Author Share Posted January 8, 2019 Thanks Mike, I'll look into this. Incidentally, is the screenshot from a Chromebook? Yes this is a screen shot from a chrome book. 1 Link to comment Share on other sites More sharing options...
miketisdell Posted January 20, 2019 Author Share Posted January 20, 2019 Thanks Mike, I'll look into this. Incidentally, is the screenshot from a Chromebook? I have noticed that when the displayed version doesn't match the text in the window that the version indicated is almost always LXX-GNT even when that wasn't one of the most recently used versions. Link to comment Share on other sites More sharing options...
miketisdell Posted January 30, 2019 Author Share Posted January 30, 2019 I have noticed that when the displayed version doesn't match the text in the window that the version indicated is almost always LXX-GNT even when that wasn't one of the most recently used versions. Using accordance on a Samsung 7 edge phone, I had a similar issue. However I was in dual screen mode versions were HMT-W4/ESVi, I switched the bottom text to TARG-T and then switch accordance into the background and used a different app. When I switched back, the display still showed TARG-T but the text was back to ESVi Link to comment Share on other sites More sharing options...
miketisdell Posted January 31, 2019 Author Share Posted January 31, 2019 This is the first time I have seen this! The version names in BOTH windows are wrong!!!! Link to comment Share on other sites More sharing options...
Matt Robertson Posted January 31, 2019 Share Posted January 31, 2019 What led to this one? Was it also on returning to the app after closing it? Or during normal use? Link to comment Share on other sites More sharing options...
miketisdell Posted February 1, 2019 Author Share Posted February 1, 2019 What led to this one? Was it also on returning to the app after closing it? Or during normal use? These kinds of issues almost always happen when returning to the app after putting it in the background. I seldom close the app itself unless I am already having a problem. Link to comment Share on other sites More sharing options...
miketisdell Posted February 6, 2019 Author Share Posted February 6, 2019 What led to this one? Was it also on returning to the app after closing it? Or during normal use? Any updates? Link to comment Share on other sites More sharing options...
Matt Robertson Posted February 6, 2019 Share Posted February 6, 2019 Any updates? No updates unfortunately. I've not been able to reproduce the issue myself and have not had other reports of it. Without being able to reproduce it or seeing some sort of events log (which would be irrelevant for an issue like this) I don't really have any way to go about trying to find and fix the bug. Link to comment Share on other sites More sharing options...
miketisdell Posted February 6, 2019 Author Share Posted February 6, 2019 No updates unfortunately. I've not been able to reproduce the issue myself and have not had other reports of it. Without being able to reproduce it or seeing some sort of events log (which would be irrelevant for an issue like this) I don't really have any way to go about trying to find and fix the bug. Is there anything I can do to help you document this? Link to comment Share on other sites More sharing options...
Matt Robertson Posted February 6, 2019 Share Posted February 6, 2019 Is there anything I can do to help you document this? Not really, aside from what you've already done. Just to clarify, you said you have seen this happen on devices other than your Chromebook, correct? 1 Link to comment Share on other sites More sharing options...
miketisdell Posted February 6, 2019 Author Share Posted February 6, 2019 Not really, aside from what you've already done. Just to clarify, you said you have seen this happen on devices other than your Chromebook, correct? Yes, I have also seen it on my Samsung 7 edge, and my Samsung Tablet (Not using much any more because my Chromebook is my replacement) Link to comment Share on other sites More sharing options...
Matt Robertson Posted February 6, 2019 Share Posted February 6, 2019 Ok. I wouldn't expect that to cause this problem, but it would be quite a "coincidence" if one of the few Chromebooks running the app were the only device experiencing the bug. 1 Link to comment Share on other sites More sharing options...
.png.c3123c857d1029f98e39c9394adc358d.png)
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now