Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 19 08:09
    conradakunga opened #870
  • Oct 15 09:49
    SMTStuck commented #864
  • Oct 15 09:45
    SMTStuck closed #868
  • Oct 15 09:45
    SMTStuck commented #868
  • Oct 15 09:44
    SMTStuck commented #869
  • Oct 15 09:44
    SMTStuck commented #869
  • Oct 14 23:04
    RickStrahl commented #864
  • Oct 14 23:03
    RickStrahl commented #864
  • Oct 14 23:01
    RickStrahl commented #864
  • Oct 14 22:27
    RickStrahl labeled #869
  • Oct 14 22:27
    RickStrahl assigned #869
  • Oct 14 22:27
    RickStrahl commented #854
  • Oct 14 21:41
    RickStrahl commented #854
  • Oct 14 21:41
    RickStrahl commented #854
  • Oct 14 21:18
    RickStrahl commented #869
  • Oct 14 21:16
    RickStrahl commented #869
  • Oct 14 21:01
    RickStrahl commented #868
  • Oct 14 19:47
    RickStrahl commented #867
  • Oct 14 19:40
    martink777 commented #867
  • Oct 14 18:49
    RickStrahl commented #868
Mehul Harry
@mehulharry_twitter
unfortunately no.
Rick Strahl
@RickStrahl
Hmmmm....
Mehul Harry
@mehulharry_twitter
"WebBrowserPreviewExecutable": "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe",
Rick Strahl
@RickStrahl
And that's valid?
Mehul Harry
@mehulharry_twitter
checking
yes
how can I launch it in Edge instead?
I was thinking that changing that setting, it might re-enable that menu option?
Rick Strahl
@RickStrahl
Leaving it blank uses a different path, but I don't think that's the actual problem - the problem is the menu binding is not refreshing as it should. Normally, opening a window EXPLICITLY forces the binding to be refreshed (due to this funky behavior which I notice on my end is work).
You can try leaving the executable blank.
Mehul Harry
@mehulharry_twitter
it's blank now but still disabled
Rick Strahl
@RickStrahl
You do have to restart for that to have an effect.
Hang on I'm going to check the conditions there with the refresh.
Mehul Harry
@mehulharry_twitter
k
Rick Strahl
@RickStrahl
Ouh...
I think I see the problem :-)
You have your preview browser not visible?
If not make that visible and the activate another window and back.
Mehul Harry
@mehulharry_twitter
Chrome? it's open, visible, and active
Or the built in one inside MM?
Rick Strahl
@RickStrahl
No - the preview in MM.
Mehul Harry
@mehulharry_twitter
even with that enabled, which it is now, it's still disabled menu option
Rick Strahl
@RickStrahl
Can you restart with it on?
There's definitely a bug there, you may be seeing something slightly different than what I see here.
Rick Strahl
@RickStrahl
So the bug is that it didn't work with the Preview off because it's looking to just display the last rendered HTML output file. I fixed that so that the file always gets re-rendered.
Thanks for pointing me into that direction.
But... that still doesn't explain why you're options are disabled.
Mehul Harry
@mehulharry_twitter
I'm using the portable version
Rick Strahl
@RickStrahl
Enabled status is controlled by thisIsEnabled="{Binding IsEditorActive}" and so somehow I suspect that flag is not set properly, but I'm not sure how.
I don't think that should make a difference.
Rick Strahl
@RickStrahl
I'm looking at this and I don't see how this could not be working unfortunately. There's some 'magic' around this because the bindings have to be explicitly refreshed, but I tried with a bunch of different scenarios here and it doesn't fail with disabled menu options for me.
I did add a fix for the execution bit so it now will work when the preview is not active. Doesn't address the disabled state however.
I guess for the moment all I can say is wait for the next update and see if that's any better. Sorry.
You can try the full version instead of the portable one (which now runs non-admin installs anyway so there's really no great reason to run the portable install)
But I don't think that that is actually the problem.
Mehul Harry
@mehulharry_twitter
Ok, I'll test the next update. thanks for looking into it
hmm, I downladed the regular install but it still brings up my version that I run from dropbox
nm, it's running from appdata and still loading docs like the portable version. Either way, good news, it's enabled that option now.
Mehul Harry
@mehulharry_twitter
Thanks again!
Rick Strahl
@RickStrahl
If you use the manual install you'll need to run markdownmonster -uninstall to remove the registry bindings to .md files, paths etc. The uninstaller normally handles this.
You should be able to run that (against the portable version) and when you restart MM it'll rewrite these settings with the new executable location. If you switch back same routine :-)
Not sure why there's a difference between portable and full version. That doesn't make any sense to me.
FWIW, you can run your installer on the full version and change the install folder to your dropbox location which should in effect give you a 'portable' install. Haven't tried this but I think that should work for updates etc. One more thing to look at :-)
Anyway - thanks for taking the time to look at this. I found and fixed at least one unrelated issue...
Mehul Harry
@mehulharry_twitter
Thanks and keep up the good work!
Alex Wiese
@alexwiese
hey @RickStrahl just noticed .NET 4.8 will add the ability to host UWP controls within WPF. Maybe you could look at replacing the IE-based WebBrowser control with the Edge-based UWP one?
Rick Strahl
@RickStrahl
Yeah I saw that. Depending on what that looks like though I'm more inclined to go with Chrome rather than shimming UWP + Edge. I have an addin that allows using Chrome for output rendering here: here. It's a proof of concept and it only does the preview which is simpler than than editor as the preview only has a few small interop entry points, while the editor has a ton.
Another point to all this is I did set up a proof of concept for Chrome (using CefSharp) for the editor without hooking up all the interop, but just running the core editor which can run without any of the interop conditionally. What I found was that the editor was considerably slower than IE - so much so that there was stuttering and a few other issues at which point I pretty much walked away from it. Say what you will about IE, the perf it gives when embedded is quite good. OTOH, I think CefSharp had a number of big performance improvements in the works which might change that in the future.
We'll see how this plays out. If the UWP control is truly full featured with easy access to the DOM then that might be an option. Not holding my breath though because the UWP control has almost no way for easy access to the DOM which rules out the JS interop.