Text is jumping when I finished typing a word
Dear Multimarkdowners,
I use Multimarkdown Composer since a few months now and I really like it. It is the best MM tool I know—and I know a lot.
But one thing drives me crazy: When I type and finish a word, all the text moves a pixel or two to the top. This happens after *every* word I type. In typewriter view and in standard view. I type quite fast, so this is really annoying. The text is always jumping up and down.
I use quite a large view (the default is *way* too small in any preset), so the movements are really big. They are visible in the text pane as well as in the preview pane.
There is a workaround, however: When you have another character below the text you are actually typing (just empty paragraphs are not enough).
Do you think there is a way to fix it? This would be great!!!
Keep up the great work,
Jens
PS: One more suggestion: What about using the standard keyboard shortcut for Zoom Editor in, which is cmd +? Thanks for considering this!
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Fletcher on 10 Oct, 2014 12:05 PM
Can you send a video of what you're seeing? There is a bug in Apple's
Webkit code on OS X that causes it to scroll when a space is typed, but
that doesn't affect the editor, and I don't refresh the preview when a
space character is typed. I haven't seen the behavior you're describing
in the editor pane.
Cmd + does zoom the editor in.
Thanks!
Fletcher
2 Posted by recherche on 10 Oct, 2014 12:32 PM
Fletcher,
Wow, you are quick!!
Thanks for your reply. I’ll upload the video soon, when I have a minute.
To the question of zooming:
> Cmd + does zoom the editor in.
I use a German keyboard, there nothing happens when I hit cmd +.
Thanks & greetings
Jens
Support Staff 3 Posted by Fletcher on 10 Oct, 2014 01:00 PM
There's your problem. You need a US keyboard. ;)
If you use the non-sandboxed build, you should be able to override the keyboard commands. For some reason, I don't think apple lets you override keyboard shortcuts for App Store apps.
F
Sent from my iPhone
4 Posted by recherche on 10 Oct, 2014 01:09 PM
Ah, great tip!
I did not think about this option, but I tried system settings/keyboard/shortcuts, and in fact I was able to change the setting! And this although I do have the AppStore version of MMC!
Great, first issue/suggestion solved!
5 Posted by recherche on 16 Oct, 2014 04:02 PM
Fletcher,
It took a while, but here is the video I promised.
Cheers,
Jens
Support Staff 6 Posted by Fletcher on 20 Oct, 2014 11:05 PM
Thanks for the video!
There's something up with your font or your system, or an unusual character embedded somewhere.
Composer doesn't adjust line heights on a per-line basis. It only happens when you type a space. There's something going on that changes the height of the line that you are editing. I'm not sure why it doesn't happen in the middle.
The only time I've seen something like this is the way Apple handles certain Asian character sets in "mid-combination" -- it adds an underscore underneath, which changes the line height.
Try different fonts and different themes. I don't think it's something I can fix, but if you can narrow it down I can dig deeper.
Fletcher
7 Posted by Ryan on 22 Jan, 2015 05:02 PM
I just bought MultiMarkDown Composer on the App Store and replaced it with the non-sandboxed build 2.8 (58). I have the same problem, whenever I type a space, I mean every time, on a line with an empty line directly below but with text further down the document, the line heights of those lines from the one I am editing to the bottom of the document jump. It is very irritating. If there is no text below the line I am editing, the jumping does not occur. What can I do? I really like MMD Composer, it is just about to replace Byword as my text editor of choice because it's incredible, but I cannot abide this jumping. Help if you can!
Support Staff 8 Posted by Fletcher on 22 Jan, 2015 06:49 PM
Ryan,
I'm sorry this is happening. I've heard of one other user having
similar trouble, but I've never been able to replicate it and other
users do not report it.
Two options:
1) You can send me a screencast of what's happening, the file that it
is happening with, and a copy of your preferences so I can try and
replicate. You can also try creating a new user account to turn off all
other third party apps/extensions and see if it still happens. You can
check the Console application to see if any relevant error messages are
popping up. If I can find a way to replicate it, I should be able to fix it.
2) As announced on the App Store and on the web site, I'm working on
MultiMarkdown Composer 3. If you own v2, you will get free access to
version 3.0, and there will be a discount sale at some point if you want
to upgrade to gain access to future updates (meaning that the total
price will remain the same if you just bought at the $5 US price and buy
v3 at a discount later). If you want to start using the version 3 beta
now instead of waiting (it will probably go to public beta within the
next week), I can add you to the list and send you a link. My guess is
that the problem will not exist for you on the new version (the code is
almost completely rewritten). The beta uses the same license as the
non-sandboxed build.
Whichever option you choose works for me.
Fletcher
9 Posted by Ryan Smith on 22 Jan, 2015 08:22 PM
Dear Fletcher:
Thank you for you superhuman response time. I think I would rather use the beta than have to troubleshoot soon to be outdated software (saves us both time). I will gladly install the new beta, thanks. Will I have to reinstall the App Store version to use the beta?
Yours,
Ryan
Support Staff 10 Posted by Fletcher on 22 Jan, 2015 08:36 PM
I've sent you an email. You don't need to reinstall, unless you deleted all other copies and cleaned out your library.
Fletcher
Support Staff 11 Posted by Fletcher on 06 Feb, 2015 07:32 PM
Parser is now fixed to handle the case you sent in.
Thanks!!
Fletcher
--
Fletcher T. Penney
Manager, Founder
MultiMarkdown Software, LLC
[email blocked]
12 Posted by recherche on 10 Feb, 2015 10:07 AM
Fletcher,
Thanks a ton. Works fine for me, and I love working with v3.
One feature request: it is not possible to add a margin-bottom to each paragraph or to the headings, is it? At least I was not able to achieve this and could not find any old styles which did this.
But it would be great, because now I add double returns after each paragraph, which is not very elegant…
Thanks for considering this.
Regards,
Jens
Support Staff 13 Posted by Fletcher on 10 Feb, 2015 06:11 PM
Any line with a "newline" at the end is considered a paragraph according
to OS X. Markdown/MultiMarkdown require a blank line to indicate a
paragraph. So this would likely yield inconsistent results.
I actually think the double newlines is the best approach -- it's clear,
and it yields the same effect regardless of which text editor one uses.
F-