Scrollbar not working
I'm not sure how I got into this state, but I've been loading style files. When I try to grab the scrollbar, I end up selecting text as if the scrollbar is not actually there. See video.
- Scrolling_Bug_-_Wi-Fi.m4v 1.43 MB
Comments are currently closed for this discussion. You can start a new one.
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 30 Apr, 2013 01:19 PM
Not sure what to tell you. I've never had any trouble with the scrollbars.
You seem to be having a lot of unusual problems in a very short period of time that have not been reported by anyone else. Several options seem possible:
1) There is a known memory leak that is being repaired. If you leave the app open for extended periods of time, it could use up more memory and slow down. It shouldn't cause what you are seeing, but I suppose it's theoretically possible. Fix: quit and relaunch app.
http://support.multimarkdown.com/kb/troubleshooting/why-does-composer-use-so-much-memory-after-its-been-open-for-a-while
2) I suppose you could cause some strangeness with an improper style sheet, but again, shouldn't do anything like what you're showing.
3) The most obvious common denominator is your machine. Virus? Corrupted system file? (I've seen some really strange stuff in the past when I had a hard drive error that affected a few system files. Things that would have been impossible to track down, but I ran a hard drive check and discovered problems.) Broken 3rd party extension? I would try creating a new user account on your machine and running Composer there to see how it works. Delete preferences files. Run Disk Utility. Check Console app for any clues. Something seems odd here, and while it's certainly possible that Composer is "at fault", it seems unusual that you are the only person reporting these sorts of problems and no one else is experiencing them. I've been using the app (during development and after) for around a year, and have never seen the things you're describing.
4) You typed some sort of magic incantation into your document, and you're seeing the beginnings of the world about to end. My money's on this one. ;)
Let me know if the suggestions under #3 help at all.
FTP
--
Fletcher T. Penney
Manager, Founder
MultiMarkdown Software, LLC
[email blocked]
2 Posted by hchapman-mmdcom... on 01 May, 2013 08:16 AM
As to the amount of problems, I've just been using the program non-stop for a few days. I decided to report the problems I found in case no one else had reported them.
It turns out that this is easy to reproduce. See video.
Support Staff 3 Posted by Fletcher on 01 May, 2013 02:17 PM
Hmmm…. this works fine for me, but it may be related to an accessibility issue. Try toggling "Enable access for assistive devices" and see if it changes behavior.
In any case, I have changed some of the code related to accessibility that should help with this as a side effect.
F-
--
Fletcher T. Penney
Manager, Founder
MultiMarkdown Software, LLC
[email blocked]
Support Staff 4 Posted by Fletcher on 02 May, 2013 01:50 PM
This should be improved in 2.2b.
Fletcher closed this discussion on 02 May, 2013 01:50 PM.