While the preview templates were designed to work well with the IE based HTML features, there were always some edge cases that didn't work in the past. Changes to make Improvements Easier Going forwardĪll of these 'internal' changes don't bring much in the way of new features (with the exception of the new Table Editor perhaps), but the switch to using the Chromium based controls for the editor, preview, table editor and various other dialogs bring many improvements.įor end users the immediate benefit is that the Preview is now using a modern browser as opposed to the old IE based browser.
All in all this process took up a couple of months between actual implementation and tracking down lots of small little behavior changes/bugs that had crept up as a result of the async changeover. This proved to be a much more involved process than the browser conversion as it ended up touching a huge swath of the codebase. That was a pretty major change as it is, but as part of that conversion it also required an intense refactoring to move the mostly sync application to mostly async. I've written quite a bit about the conversion from the Internet Explorer based WebBrowser views to the Chromium based Edge WebView2 control which touched a lot of the code base. Building out these changes actually took a lot of effort - a lot more than I expected. Most of these features are internal and they affect the underlying foundation that Markdown Monster sits on. If these don't sound very exciting from an end user perspective, you are right.
0 kommentar(er)
