Delay when typing in main window


I just downloaded Scrivener 0.0.29 on Arch Linux. Everything seems to be working great, except for a very noticeable delay of half a second or so between pressing a key and the character showing up on the main window (not sure what’s the right name for this - I mean the area where you actually edit a document). This delay also happens in full-screen mode, but nowhere else (typing in the synopsis cards, renaming documents in the binder, etc, all happen instantly). I’ve tried disabling everything in the Auto-Corrections tab in the options, but it makes no difference.

This doesn’t make the program unusable, but it’s quite disruptive. I searched the forums but couldn’t find anything similar except for this thread, which is quite old and about the OSX version. Any clues?

Thank you very much.

Are you using a compositing window manager (e.g. something like Compiz, or GNOME/KDE with ‘Desktop Effects’ enabled)?

If so, try disabling compositing and see if that helps. I’ve had the same thing happen with isolated applications (e.g. rxvt-unicode but not konsole) when the Composite module was loaded in the E17 window manager.

Nope, I’m only using Awesome WM.

I’m noticing a bit on my netbook after upgrading to 0.3.5. there was a change where some optimizations were removed for this one, which might cause my problem. And I have Pandora going.

I just accidentally found out that this problem is related to the window size. The smaller the window, the smaller the delay. My desktop resolution is 1920x1080; using it maximized is terribly annoying, but if I make the window half that size the problem becomes almost unnoticeable.

I’m having the same issue on the Windows version. I thought it was possibly my netbook not having a very good processor, but I’m now experiencing the same problem on my notebook as of the latest release. I can’t write this way at all, it’s too distracting, so this is going to be a dealbreaker for me if it can’t be resolved.

The problem is greatly reduced in 1.0.1, but it’s still there. Any chance we could get an update from the developer?