[users] Re: New chirp-next build

It's on a second monitor that is not switched on or your OS has sent it to another machine?

We figured it out, but I think it was basically this. CHIRP attempts to restore the on-screen position of the window and the config had stored a location that was no longer on his screen (either due to a resolution size change or extra monitor or something). He nuked the config which brought it back into the default position. I've got a fix queued to maybe try to mitigate some instances of this (although it's a bit tricky to do universally).

--Dan