Random visual glitches around the menu area v1.1 (Win 7)

[wfdctrl]

Since I upgraded to the new version(1.1), I have been noticing that the menu area is flashing at random times. I also get a similar glitch when I minimize the window.

[redmunds]

@wfdctrl You'll need to provide more info. A screen shot and set of steps to reproduce each problem would be very helpful.

[wfdctrl]

As I said the flashing seems to happen at random, so it is not directly triggered by any of my actions. It always happens when I am typing, so I never got a good look at it. It kind of looks like the glitch when you minimize the window. I'll try to take a video...

In the mean time I downgraded, because it was a bit distracting and I haven't had any problems since...

[wfdctrl]

I reinstalled the new version and it doesn't recur when I pay attention to the upper corner of the screen. It could be possible that my peripheral vision is playing tricks on me.

On an unrelated note, the text started to turn green when I tried to reproduce the glitch. Should I open a new issue?

[redmunds]

@wfdctrl

the flashing seems to happen at random

Yes, everything seems random until you figure out what's happening :)

[wfdctrl]

The glitch is also triggered when the window loses focus, however I can no longer reproduce it just by typing. I finally have the screen-cap:

[nethip]

@wfdctrl Do you have any programs installed on your system to customize windows themes? Possibly related #8890.

[wfdctrl]

No, I use the default theme, always have. Anyways my computer is a little sluggish today, therefore the window switching works slower than usual. Now I can see what’s actually going on. The default windows border and title bar peek through for a brief moment and the white lines I have been noticing are their edges. The flashing also happens when I press ctrl-s and that is how it was triggered while typing. 😄

[peterflynn]

Btw, about "the text started to turn green": that's the normal, correct syntax highlighting. When you type a number in a JavaScript file, it will be color-coded green.

[peterflynn]

Hmm, I can actually repro this today when switching windows too.

[nethip]

@wfdctrl This can be reproe'd on Brackets 1.0 as well. It might not be that evident in 1.0, but you could still see the white line just in the project tree. This might have gotten worse in 1.1 as there is now a little more room between the menu bar and the editor. (see #10081).

[wfdctrl]

@nethip yes, you’re probably right, when I first installed 1.1 version, there was constant flashing while I was typing (I compulsively press ctrl-s after every input). After I downgraded it was no longer triggered by saving, so it was as good as fixed for me. Then after I upgraded again I couldn't replicate that behavior, hence the confusion in my earlier comments...

@peterflynn about the green text: am not the sharpest tool in the shed at 3 in the morning 😅

[fxb]

I think this could be caused by ScheduleMenuRedraw and MenuRedrawTimerHandler. Maybe try to not only call DrawMenuBar, but instead do whole DoPaintNonClientArea? Legacy windows code probably draws this white line, which needs to be drawn over again.

[fxb]

I also noticed this happening after a WM_NCACTIVATE / WM_ACTIVATE. Changing the following in cef_dark_aero_window.cpp seems to get rid of that, since the default WndProc doesn't get to draw weird stuff after our call to UpdateNonClientArea.

case WM_NCACTIVATE:
case WM_ACTIVATE:
    if (mReady) {
        UpdateNonClientArea();
    }
    break;

Changed to:

case WM_NCACTIVATE:
case WM_ACTIVATE:
    if (mReady) {
        UpdateNonClientArea();
    }
    return 0L;

[nethip]

@fxb 👏 This indeed fixed this! Good job! Could you put up a PR for this.

[frenic]

Still having this issue in v1.3. Sometimes it looks randomly sticks like this until I move my cursor. In this case I expanded a directory. Would be nice close this with v1.4?

[nethip]

@faddee The PR adobe/brackets-shell#507 is not yet merged with the master as we ran into couple of issues while unit testing.

[frenic]

@nethip Argh! Ok, thanks for the info and good work though! :-)