When I open Markdown Monster I get the splash screen, then a black box with no UI. It appears to be partly functional though as if I click in the right place I can close the app, or get a menu to appear. See below (interestingly the screenshot shows it as a white box):
However, if I then move it onto another screen (the laptop itself), it's fine. And then if I move it back onto a monitor, it's fine.
My display settings - all screens are scaled to 100%.
Thanks for posting this detail.
We had a previous issue on that, but unfortunately no resolution as it appears to be a WPF rendering bug that occurs very rarely (I think) and presumably only on certain monitors/video card combos. So far I've heard of 2 people running into this - so it happens, but rarely.
I've tried to dupe with a variety of monitors and TVs (thought it might be low-res displays especially susceptible), but haven't had any way to duplicate. We've also tried to different ways to force the window to refresh itself (and do a raw render). One thing MM does is render off screen then flic in because of the Web browser controls. But even without that in the previous case the rendering didn't work.
Can you try:
MM should remember the screen location. Is the behavior the same on all monitors?
Shutting down and restarting MM on different screens:
Interestingly I get a similar issue with Google Chrome - on the external monitors F11 for full screen causes a black screen, whereas on the laptop screen it works fine.
I suspect this may be graphics card driver related.
Leave it with me - I'll see if I can get full-screen working properly in Chrome and then retry MM if I do.
Updating the graphics drivers to the latest (from Lenovo at least) didn't help but following these steps did, for Chrome: http://superuser.com/questions/1098204/chrome-html5-videos-in-fullscreen-are-black-when-intel-graphics-are-enabled-or-h
Thanks for checking into this and checking back here.
Cross referencing a couple of other issues that have reported similar issues here so maybe we can find common ground:
Certainly looks like this is a hardware/gpu rendering issue to WPF.
This post has a few suggestions:
I wonder if you could try the Registry hack temporarily to see if that gets rid of the issue.
If so I can probably try setting the rendermode flag in code as an option if things fail. This is seriously troublesome, given that random hardware can cause things to behave. Especially since you setup sounds like pretty standard, commonly used fare. Sigh.
Another thing to try is: See if you can force your MM to run on the Intel Video card. The nVidia driver options should have an app that let you specify whether you want accellerate specific apps. WPF apps automatically end up getting pushed onto the nvidia card most likely. Maybe running on the intel driver will produce better results.
The registry hack works.
The system was configured to run everything using Integrated Graphics by default. I tried switching the configuration for MM between the two options but it made no difference, still black (with the registry hack reverted temporarily).
If something could be put in code that would be useful, though it sounds like it's not affecting many.
Ok - I added:
RenderOptions.ProcessRenderMode = System.Windows.Interop.RenderMode.SoftwareOnly;
in 1.1.28 (just updated - I didn't rev the version number).
Undo the registry hack, then start MM and edit the configuration and set that key in the configuration file to true:
which should do it for just Markdown Monster. You might have to start, stop then restart to see the key show up in the configuration file (as it gets written when MM exists).
Thanks Rick, that works perfectly. I'm happy to consider this issue closed as it doesn't seem to be an MM issue and your workaround seems like the only solution for now.
Thanks for helping track this down Tom. While it sucks this happens at all, at least this workaround hack provides a solution I can point people at. I don't see any significant performance difference in MM operation due to this even though there are some animations due to our usage of MahApps.
I have this issue, I did change the value in the config file to disable hardware acceleration and that did not fix the issue. That being said, if I open it, drag it to my laptop screen and then back to my main external monitor (sometimes 2 or 3 times) it seems to work fine. I am new to using this editor, but if it works well this bug is not really a big issue for me.
Hmmm... that should definitely work. Did you double check to make sure the key was set when you started up? It sure sounds like exactly the same issue described here.