Tim Monko

I think that this issue could be closed, especially after our recent remapping of colormap cycle, changes to sample data, and all the things that @psobolewskiPhD mentioned. The only thing...

I just had this bug happen today. I had the napari viewer open in a position outside either of my monitors, so it could not be moved. The only fix...

This bug still popped for me after a close on a fresh new env / napari install last night. This time, I did not need `napari --reset` to place it...

Sounds good to me, I added some labels to help us track.

@Modjular that's definitely a good starting place! Peter's comment provides some good insight. Thinking about implementation more, I would move it to a CanvasOverlay, which will also tile nicely once...

> * Is there a napari UML diagram anywhere I could reference? I'm having a lot of trouble figuring out if I'm looking at model or viewer or controller code....

@Modjular this is so awesome to see working! Would be amazing if you made a PR to our repo, seeing the code (especially in this quite working state!) will help...

Definitely looks fixed to me :) Branch: Default top_right:  Size 30:  Main: Default top_right:  Size 30: 

Part of this is fixed, in that `scale_bar.length` exists. The method is also now `viewer.export_figure()`, however, if `scale_factor` arg is large, then the problem still occurs. This does make sense...

I was checking out the new [napari-vector-graphics](https://github.com/JoOkuma/napari-vector-graphics) yesterday -- and while it still needs polished up, it may be a route to success. I.e. have everything look nice and pretty...