Bug 162709 - provide configurable caret (text cursor) for all text-edit widgets
Summary: provide configurable caret (text cursor) for all text-edit widgets
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-27 17:23 UTC by Maciej Pilichowski
Modified: 2024-09-14 16:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2008-05-27 17:23:22 UTC
Version:            (using KDE 3.5.9)
Installed from:    SuSE RPMs

Currently there is only one cursor -- | (black).

It would be useful to be able to configure this (for both modes, insert and overwrite):
* shape: |, _, # (rectangle, filled)
* blinking/non-blinking
* color+transparency
* if blinking -- alternate color+transparency
* if blinking -- speed

Kdelibs: because it is important for every edit-box, memo, etc.
Comment 1 Matthew Woehlke 2008-05-27 18:00:54 UTC
By "cursor", I think you mean "caret"? The "caret" is the little indicator that shows where you are typing, which can also be called "cursor", except that "cursor" can also mean mouse cursor. Please clarify so I can make the bug description unambiguous :-).
Comment 2 Maciej Pilichowski 2008-05-27 18:41:20 UTC
Yes, caret, sorry for not using this term.
Comment 3 Matthew Woehlke 2008-05-27 20:30:24 UTC
No worries, it's a fairly obscure (and definitely technical ;-)) term.

I'll leave "text cursor" in the description as a reminder for people not familiar with the term and to help with bug searches.

Thanks for the clarification.
Comment 4 Christoph Cullmann 2024-09-14 16:17:51 UTC
Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have implemented this wish.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann