Uploaded image for project: 'Core ReactOS'
  1. Core ReactOS
  2. CORE-17929

Cursor/Caret blinking rate never is never reaching None

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 0.4.15
    • RosDlls, Win32SS
    • None

    Description

      ReactOS version: 0.4.15-dev-3507-g00ffe2d

      Bug: Cursor/Caret blinking rate "Never" get the caret static (always shown). None position is not doing its job, as Windows ("None") does.

      Videos attached:
      ReactOS Blinking caret - Never not working.webm
      XP XP - Blinking caret Never OK.webm
      Also, it's spamming this in the log:

      (/win32ss/gdi/gdi32/objects/gdiobj.c:326) Trying to delete system object 0x00900030

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. CORE-11950 The position of the caret is shifted by 2 pixels to the left

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. CORE-9141 Abiword 2.6.8 Can't type or edit text properly, because the cursor is not visible initially

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. CORE-13984 LibreOffice Writer shows no blinking caret

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. CORE-14359 [WIN32SS] Apache Open Office 4.1.2 SWriter - no blinking Caret

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              zecarlos1957 zecarlos1957
              julenuri julenuri
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: