Actions
Forum Thread Details
  • Replies 6 replies
  • Subscribers 179 subscribers
  • Views 1022 views
  • Users 0 members are here
Related

Eagle 7.3 Text edit insertion point visibility bug screen cap video

gwideman

This post follows up on previous post Eagle 7.3 schematic: cursor missing in text boxes?, with some actual screen cap evidence :-)

 

Description:

 

Throughout Eagle 7.3, upon initially clicking into a text edit box, the insertion point cursor is invisible until I start typing, or use the arrow keys to move the insertion point. Often that's very annoying because you get no feedback as to whether you've positioned the insertion point at the correct position in the existing text. At the very least, you can't tell that the text edit box has focus.

 

System: Windows 7-64, up-to-date.

 

Problem did not occur in 6.5.

 

Attached screen cap video shows 6.5 and 7.3, running side-by-side demonstrating the problem only in 7.3..

 

It's speculation for sure, but it's as though 7.3 (or at least 7.x) uses a more recent version of QT which has somehow changed the initial visibility of the insertion point and requires a slightly different calling procedure.

 

-- Graham

Attachments:

  • Hi Graham,

     

    I hope you're doing well. I came to check out the video, it's odd but I can't reproduce what you're seeing. Both 7.3.0 and 7.3.2 work as expected. Do you have any other machines you could test this on to see if perhaps it's an isolated incident?

     

    Thanks for the video, I wish all bug reports came with a video.

     

    Best Regards,

    Jorge Garcia

  • in reply to Jorge_Garcia

    Hi Jorge thanks for replying.

     

    I'm curious whether you are trying it on Windows 7-64, or some other OS or version?

     

    I can try it on another Win7-64 machine and see what that reveals -- might take a couple of days though.

     

    Am I right that Eagle uses QT? And if so, I would like to know what QT version was used in Eagle 6.5 and 7.3, as that might lead google to some related comments.

     

    Thanks!

  • in reply to Jorge_Garcia

    I'm pleased to announce -- diagnosis NAILED!

     

    It is indeed a bug in Eagle 7.3, albeit possibly passing on a bug in Qt 5.something.

     

    The bug is not in 6.5, nor in 7.2 (which I subsequently tested).   Examining Eagle's dialogs with Ranorex Spy, I confirmed that from 7.2 to 7.3, Eagle did change the version of Qt employed.

     

    The heart of the problem is this: upon initially focusing the (I assume) QLineEdit control, Qt sets the flashing cursor to its "flash-off" phase, relying on the subsequent flash-on... flash-off action to make the cursor visible. But, thwarting this expectation, in Windows, the text cursor flash rate is set at the system level, and can be set to "None", which is what I had.

     

    Consequently, the cursor never proceeds from its flash-off state to its flash-on state, hence it remains invisible. Apparently, if you then make a move with the arrow keys, or type in some text, there's code which forces the cursor to flash-on state (presumably so that while you're moving the cursor it's continuously visible).

     

    To work around the problem, Windows > Control Panel > Keyboard > Speed > Cursor blink rate ... and set it to some value other than None.

     

    Obviously to repro the problem, visit the same setting, and set it to None.

     

    I have repro'd this on another Win7-64 machine with Eagle 7.3. Initially the symptom was not present, but setting Cursor blink rate to None did precipitate the problem.

     

    I hope that helps devs pin-point the problem in the code, and/or file a bug report with Qt.

     

    -- Graham

  • in reply to gwideman

    Hi Graham,

     

    I did try it in Windows 7-64 bit

  • in reply to gwideman

    Hi Graham,

     

    I applaud you for your investigative skills. That explains why I couldn't reproduce it, the blink rate isn't set to None by default so I have the default blink rate and thus don't see the effect your describing.

     

    EAGLE does use Qt and we switched versions between 7.2.0 and 7.3.0. I'll submit the issue to the Devs and see if anything will be done. Few users change the blink rate on their machines so I'm not surprised that this didn't pop up before.

     

    Best Regards,

    Jorge Garcia

  • in reply to Jorge_Garcia

    Hi Jorge and the I'm sure hordes of other interested onlookers,

     

    I since verified that this is a problem with other Qt apps (including Qt Creator itself), and even made a quick Qt app to verify that it is with the Qt QLineEdit component.

     

    I have filed a bug report: https://bugreports.qt.io/browse/QTBUG-47867

     

    -- Graham