Expected behaviour

Editing text on the real document view, not on the code view.

Actual behaviour

You have to edit text in the code view, and then look to the final view. I can't see a reason for this although I know it's very normal among MD editors with few exceptions.
I have to use the entire screen just for Qownnotes, because it needs two views for writing only one file. If QN is not maximized, the lines arent rendered correctly, like they are really lookind in the real document. This would not be a real problem if not because I usually am taking text from sources like webpages, OCRed books, and other documents like OTF and PDF files, so I have half screen for those documents and the other one for the text editor, side by side so I can instantaneously jump from one the other. But since QN forces me to have its window splitted in two, each QN's view, code and real, are 1/4 of my screen's width, whic is too narrow to see the complete page.
So, at the end, I have to maximize QN and Alt+Tab constantly to swap between QN's windows and the document I'm using at each occasion.

Steps to reproduce

1. Write something
2. Try to edit over the formatted view.

Output from the debug section in the settings dialog

Sorry, I have no idea what you are talking about. I'm just an average user that has opened this Github account because someone told me that GH isn't only for developers but also for users who want to collaborate with suggestions and bug reports.

Relevant log output in the Log panel

Excuse me if you plans for your app are to keep it "geeky". If so, surely youll want to forget this post. But if you want a broader public, please consider adding a WYSIWYG option like Uncolored, or at least "quasi" WYSIWYG like Abricotine.

Markdown is ideal for elaborated notes, drafts and brief documents that don't need as many features as ODT documents, like lot of pages and references, footnotes, comments, wrapping texts, font families, etc. Besides you can edit them with any thing thats able to write text. It's great. But being forced to type code, even if easy, doesnt help to popularize MD. Editors should be as easy to use that common users, accustomed to work in a totally visual way in text processors, mail composers, etc, could use them without the need to "study" before. Think if your aunt would feel comfortable taking notes of her vacations having to remember "**", "#", "__", " ", "()[]" etc... I think most users prefer an user friendly interface.
All this, in case you are interested in making GW for as many people as possible. Obvously, the program is yours and you are entitled to want a more techy public, of course.

But if you are open to consider my point of view, please take a look to telegra.ph, the online publishing tool by Telegram, or to Uncolored, mentioned before. They cant be easier: no code views, no "occult" stuff behind weird symbols. Just type, select text, and a floating menu appears to provide the tools you need to format your text or insert media files; and in every moment you see what you are doing without the need of two panels that clutter your desktop and confuses you (when I say "you" am obvously referring to the "average Joe").
BTW, those floating menues is something you could implemente even if don't want to add the WYSIWYG option. Having the pertinent tools at your "cursortip" instead having to "travel" to the fixed menu bar open a pop up menu and then click on whatever option, is a nice improvement for efficience: saves time and avoids distractions.

Im proposing all this WYSIWYG thing as an option, not as a substitution, of course. The code view is useful too and once you are familiar with the syntax it's some times faster if you have very clear what parts of the text you want to format, like in the case of headers, for example; and you know exactly "what's happening" in the "guts" of your text. But in general, using the mouse to select text, click a button, and there you have your format or your link inserted is faster.

I'm not very experienced in Github's "etiquette", but please take this as constructive criticism. I'm using your software since some days ago, and I'm liking it (I'm reasonably fluent with Markdown, even if code editing is always slow), but it would be also nice to "liberate" relatives and friends from proprietary software like MS One Note and the MS ecosystem in general; for their own sake but also to be coherent with that usual complaint in the Linux world: With 2 - 3% of the market share we'll never have good device support, no good job opportunities for Linux experts beside the servers and investigation fields, and never ever Autocad/Photoshop/whatever for Linux.
All that is true, but how to liberate or beloved ones and also increasing the number of Linux/BSD/whatever if they find things on FLOSS more complex than necesary? It's understandable that they end turning back to One Note, G. Keep, etc; not because they think those are better, but give them less headaches.

BTW, I see you accept donations. Do you also accept "bounties"? You know, some users want a feature, they talk ans agree to put some money together for the developer if these adds such feature. I think is a better way to suppoert development than just donating withiut conditions. It levels the balance a bit by giving some little portion of power to the users.

Cheers. and forgive the lenght of this post. But I think it's better to write a long and explaining post than a brief one, and then other 2 to explain what wasn't well explained in the first. 😬

Appendix:
Excuse a last suggestion: Look this from Typora's site, it's a very nice feature that avoids, fos example that annoying thing that we all who spend many hours a week typing documents: to loose track of the position where we are writing. Dimming everything but the lines where we are is a very neat idea. :)