Bizarre blank spot noted

I am seeing what appears to be a fixed-in-location blank spot in outline mode,

Here, in a Dual Pane nav layout:

And here in a single-editor:

I also screen recorded a couple of movies that show it in two different projects, with each project in a different location on the screen (so, it’s not some kind of overlay artifact just at that location), but I don’t think I can upload .mov files. It is, however, fixed in location wherever it does appear.

Here are two frames from one of the movies, showing that this blank spot sits still when things are scrolled side-to-side:
Screen Shot 2018-09-29 at 20.52.08.png
Screen Shot 2018-09-29 at 20.52.28.png

That’s very strange! I’ve never seen anything like that and cannot reproduce it. My first thought was that maybe there is some background drawing to the keyword colour chips drawn outside of of where it should, but I’ve checked and there’s nothing like that going on. Can you find any steps that I can take to reproduce it in a blank project? And what OS are you on?

Thanks and all the best,

OS is Mojave 10.14 (18A391). I’ll see if I can isolate anything that seems to be reproducible—though, so far, it’s just something I’ve noticed in all the projects I’ve opened—although I can’t with any certainty say it wasn’t happening before on High Sierra. I don’t have a HS machine I can test on. I’ll give it a go later today and see if I can find a way to make it not appear.

Thanks. I’m on Mojave too and cannot reproduce it. Very strange!

No worries—and sorry it has taken so long to respond, life being what it is. I am not sure there’s a lot to really go on, and I haven’t found any reliable way to not reproduce it, so it could be a weird artifact of my setup.

Setup specific details:

  • MacBook Air (mid-2013, 13", 8 GB RAM, 256 GB SSD)
    [*]Connected to an external Samsung 40" 1080p TV via Thunderbolt->HDMI (… well, “technically” Mini DisplayPort, I suppose, though the Apple website does name it as a Thunderbolt port) which displays at 1920x1080 (default for display)
  • with built-in and external displays both separate displays (i.e., not mirrored), and the built-in at 1440x900 (also default for display)
  • macOS 10.14 (18A391)
  • Scrivener 3.0.3 (3032)

What i’ve noticed is that the “blank” spot isn’t actually blank, but rather very, very dim. I took a screen capture movie of only the outliner toolbar and a couple of lines worth of content, and when I look at it in full-screen I can see that the text and line are present, but almost invisible:

(hopefully this shows it, the “ds” of Keywords is present, just very light)

The effect extends down about one pixel, but otherwise does not affect the content area:

So, if I had to guess, it seems that it is connected to the drawing of the “header” row/toolbar of the outliner view, including any dropshadow that graphic element may possess. That could be an Apple thing, that could be a drawing-code-in-Scrivener thing, or it could be something with how the output through TB->HDMI interprets that particular piece of it.

The “spot” was still present—in the same location—when I moved the window from the large (TV) display to the built-in display. When I resized the window to fit, it disappeared, possibly because with the resize, that box was now off-screen. On the main display (the TV), I didn’t have the window sized to completely take over the screen (I use the Dock on the right, auto-hide/magnify, and have the Scrivener window full size top-bottom and all the way to the left side, but leave the entire right desktop column and half of the next-to-right column, so I can drag&drop from the desktop still, see image:

), so the box is outside the visible area of the three-panel Layout that I use when I move it to the smaller display and opt-click the zoom button. However, when I switch it to the Default Layout and switch to Outline mode, this box is in the same location, even on the smaller screen. So if it’s caused by being displayed on the larger display, it sticks afterward.

BUT, in the three-pane display that I use, if I resize the window (with option-click on the zoom button) on the smaller display, the box disappears, but only on the smaller display. Moving it to the larger display, the box reappears in the same spot it was in before. Also, if it is in single-pane Layout (like Default) on the smaller display, it shows the box there. It only disappears in the three-pane layout (Dual Navigation, for example) when the outliner is in the upper-right; switching to a single-pane view with outliner, the box reappears even on the smaller display.

When I say that the box “disappeared” when I resized the three-pane navigation Layout display on the smaller monitor, it disappeared completely—but only in that situation, and reappeared in the exact same place, on either display, if I switched to a single-pane Layout with the Editor in Outline view. Of course, on the main monitor, it was always visible.

I suspect that in the case where I had a three-pane navigation Layout with the outline in the upper-right, and then resized down to the smaller monitor, the box disappeared because it was redrawn—but the reappearing box is a bit mystifying. To me, if it was simply a redrawing problem, then resizing it so the box is off-camera should have reset it, and it would redraw normally from that point on, but that does not seem to be the case.

Hang on, I’m seeing it myself now, too! I think I didn’t see it before because I looked in my development version (the upcoming 3.1). I can see the issue in 3.0.3 (which was built on 10.13), but not in the upcoming 3.1 (which was built on 10.14). The only I can think of is that the corner view - the little arrow that lets you choose which columns should be visible - is triggering this, seeing that is the only thing this header bar has different from other headers in the app, and that it only occurs for apps built on 10.13 or below running on Mojave. The whole header bar is drawn differently for apps built on 10.14 (it’s grey rather than white), so presumably different drawing routines are being called in Apple’s code and there’s an oddity in the older one. So the good news is that this should be fixed in 3.1 just by virtue of 3.1 being built on Mojave.

That makes sense, and although it was just a very minor … heck I even hesitate to call it this … annoyance, I’m glad to hear that it’s probably just a tiny drawing artifact holdover and is fixed in the upcoming version :slight_smile:

Just to confirm, I am now running Scrivener 3.1.1 (9852) and this behavior is fixed. Thanks KB :smiley: