This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Preventing Kile changing cursor blink rate when compiling?

Tags: kile, cursor blink rate kile, cursor blink rate kile, cursor blink rate
(comma "," separated)
drmrd
Registered Member
Posts
2
Karma
0
I've been using Kile on Windows for quite awhile now (at least 2 years), and there's been a consistent, annoying, and fairly bizarre problem that I've encountered and can't figure out how to solve. The situation is as follows...

I hate blinking cursors with a passion (find them distracting), and accordingly keep my "Cursor Blink Rate" (let's call this CBR) setting in Vista/7 set to 0 (i.e., disabled). When I run "Quick Build" (defined as PDFLaTeX followed by ForwardPDF, the latter forwarding to Okular), the CBR setting in Windows is maxed out (making the cursor appear to be flickering rapidly) or reset to a rate slightly faster than Windows's default CBR. (To see what these look like, go to Control Panel > Keyboard in Vista (or just type "cursor blink rate" in the start menu in Windows 7) and change the CBR setting to the right most one or somewhere in the middle of the bar.) I find this really distracting, and wind up having to keep the Keyboard Properties window opened while typesetting documents (so basically at all times). This is made even more annoying since (due to the oh-so-sophisticated programming of the Keyboard Properties GUI) the setting change that occurs during compilation (or possibly previewing in Okular) isn't reflected in the Keyboard Properties screen (meaning to change the setting back to CBR=0, I have to change it to some other CBR, apply the change, then change it to CBR = 0, and once again apply changes); it's a bit of a pain to access the menu; and the only way I'm aware of (or remember) interacting with this setting in the menu is via mouse.

My questions are (1) Has anyone else had this problem? and (2) Any ideas on how to solve it?

Attempts at solving the problem thus far:
When working with Linux, I usually rely on http://www.jurta.org/en/prog/noblink for all my cursor-blink-disabling needs, but its information about KDE doesn't seem too relevant for KDE on Windows (since it appears Kile is using Windows's built-in cursor settings). I'd be very happy if I'm wrong here, however!

I've tried unsuccessfully to find a solution to this online, searching both MikTeX and KDE-related forums/newsgroups/bug reports. (IIRC, there is a related bug, which I can't seem to find at the moment, filed for Kile, but no one has responded to it.) I've also created a batch file that enables and then disables CBR at the registry level, but doing so doesn't seem to change the on-screen CBR. (I'm guessing explorer.exe or something related needs to be refreshed.)

In case it helps...
The bug affects every recent version of Kile/Okular on 32- and 64-bit Windows Vista/7 using MikTeX as a LaTeX backend. (I haven't checked if it persists when using another LaTeX distribution.) I'm guessing this is KDE on Windows specific, because it doesn't seem to occur in other LaTeX frontends. However, this could also be because the other frontends I've tried do not use Windows's default cursor settings.

Thanks in advance for any help you can provide!!
User avatar
SaroEngels
KDE Developer
Posts
49
Karma
0
OS
Could you make a bug report at bugs.kde.org about that? I can't try this out right away, but I would really like to look into that.


SaroEngels, proud to be a member of KDE forums since 2008-Oct.
drmrd
Registered Member
Posts
2
Karma
0
SaroEngels wrote:Could you make a bug report at bugs.kde.org about that? I can't try this out right away, but I would really like to look into that.


Done!

https://bugs.kde.org/show_bug.cgi?id=299079

Thanks for your reply/interest! :)


Bookmarks



Who is online

Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell