tag:support.multimarkdown.com,2013-02-12:/discussions/problems-v4-ios/6-preview-font-size-too-smallMultiMarkdown Software, LLC: Discussion 2018-08-07T21:35:00Ztag:support.multimarkdown.com,2013-02-12:Comment/454030272018-06-25T17:18:46Z2018-06-25T17:18:47ZPreview font size too small<div><p>Lots of discussion on the other two, but this is the one that actually makes it unuseable as is.</p>
<p>Shrink the picture down to the size of an iPad screen — the Preview is almost unreadable.</p></div>Vincetag:support.multimarkdown.com,2013-02-12:Comment/454030272018-07-21T18:59:58Z2018-07-21T19:00:00ZPreview font size too small<div><p>Haven't heard from you on this, and haven't seen anything at all on any IOS issue since July 2nd.</p>
<p>Are you out there? Everything OK?</p></div>Vincetag:support.multimarkdown.com,2013-02-12:Comment/454030272018-08-03T15:41:37Z2018-08-03T15:41:38ZPreview font size too small<div><p>Another two weeks. I hope this is a REALLY long vacation and not something more serious.</p></div>Vincetag:support.multimarkdown.com,2013-02-12:Comment/454030272018-08-07T00:58:14Z2018-08-07T00:58:14ZPreview font size too small<div><p>Hmmm... For some reason your responses didn't come to my email.... Just saw this now.</p>
<p>I've been working on some core MMD work, in addition to being back in the hospital more than last year (academic years are Jul-Jul).</p>
<p>I'm not sure what the final approach with preview will be. There are two (three?) competing demands:</p>
<ol>
<li>
<p>Visibility -- easiest thing to do here is to use "actual" size of the view, which will lead to a taller, narrower preview in split view.</p>
</li>
<li>
<p>Accuracy -- the view you reference demonstrates a more "accurate" preview where the font is proportional the available space (just like an image shrinks when displayed in a smaller space)</p>
</li>
<li>
<p>Consistency -- Should the aspect ratio of the preview remain unchanged when the view is toggled from a split screen preview to a full screen preview? Or how about when the device is rotated? The approach currently used basically resizes the "paper" to fit the available space. This means that line breaks and the overall appearance of the preview are consistent no matter how the preview is resized. This is the usual approach of Safari (assuming that the page has not overridden that behavior.)</p>
</li>
</ol>
<p>Another option is to assume a fixed "resolution" and treat rotation/expanding the preview like adjusting the size of a window on a desktop computer (again, assuming that the web page does not override the behavior.) This would cause the text to remain the same size on screen, but the shape of the page and content would change every time the preview size was adjusted.</p>
<p>Each has its pros and cons, and I need to decide which is best (A user option may be needed, but I would really prefer a consistent approach.)</p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/454030272018-08-07T21:34:59Z2018-08-07T21:35:00ZPreview font size too small<div><p>I'll only say what I've already said — the current method leaves the app unusable. If I can't read the Preview, the preview doesn't do me any good.</p></div>Vince Rice