Explaining my tab and cam issue from the previous post.
I’m actually about to wipe this computer and fall back to Ubuntu and a fresh install of everything. Debian refused to fix some video issues keeping me in 1024x768 and not allowing me to use my 2nd monitor. We’ll see if maybe this is just a resolution/driver/video issue.
@Carl_Fisher this is a fresh one, I cannot replicated exactly that but I’m having issues with the latest commit in Windows specially displaying the raster file
I’ll let you know if the behavior is any different once I switch the OS and put the latest build on there. If it does fix it, I have another old laptop I may put back to Debian and see if I can recreate it again. If it doesn’t fix it, I’ll post a follow up.
My issue has nothing to do with the latest commits. Went back a couple of days and same. Just updated chrome same. I was trying to replicate this issue by changing the resolution but stumbled into these other
oh good, I was going to ask about the browser. Mine was using firefox that came with the stock Debian install. I probably should have pulled Chrome to see if it was an issue there as well.
Solved my mystery (not usually use windows for LW) it was related to not having setup in this install the default raster ( Btw it’s something I asked for)
Quick follow up. I think this was a video driver issue. The new Ubuntu install has all good drivers and higher resolution and the issue is gone. I’ll drop back down later to a lower resolution and see if it comes back.
I fixed a couple of issues tonight (both of which I introduced… yikes!). If you haven’t set the default bitmap DPI yet and import a raster, I now default it to 25.4 DPI (which seemed to be the default for everything else in the codebase). I also reworked the problem that was causing rasters to snap back to the origin if you opened additional layers. I can’t say for sure if this was causing anything related to the issues you just saw. +Peter van der Walt originally told me that everything was only tested and supported on Chrome; I’ve fixed some Safari bugs in the code. You said this was Firefox on Debian?
@Carl_Fisher I just re-read your last comment. Let us know!