SlickEdit Product Discussion > SlickEdit®

typed characters are appearing out of order

(1/4) > >>

Chris Nisbet:
I've started seeing a problem where characters I enter using the keyboard are getting entered out of order. I wouldn't swear to it, but I think it started happening after I upgraded to 27.0.2.0. What happens is that some characters show on the screen as expected, but then the screen will freeze for a short period of time and then the last few characters entered will turn up in the incorrect order.
e.g. this is the what turned up on the screen after entering the characters "turnkey".

turekny

The problem doesn't happen all the time - I can enter quite a few characters and not see the problem, but then I'll notice that some characters turn up in the incorrect order. For a while I thought it might be operator error, but it isn't. The out-of-order issue seems to coincide with this 'stickyness' I experience with the update of the edit buffer - the display will stop updating for a short time (< 1 second) and then the last few characters entered will/might show up in the incorrect order. If I type slowly, the problem doesn't occur, but what I will see is that even a single character will take some time to turn up in the buffer window.

In terms of buffers open, it doesn't seem to matter too much - I can reproduce the problem with just a single 500 line .c file open.


Anyway, I'm wondering if there are some settings I can adjust to reduce the likelihood of this happening? I'm guessing that maybe something like autocomplete or syntax highlighting might be involved somehow, but I don't know what the recommended/default settings might be.

Any assistance would be greatly appreciated.


Program Information:
SlickEdit Pro 2022 (v27.0.2.0 64-bit Qt4)

Serial number: VLX930448
Licensed number of users: Single user
License file: /home/chris/slickedit-pro2022/bin/slickedit.lic

Build Date: April 25, 2023   (State file: August 7, 2023)
Emulation: CUA

OS: Linux
OS Version: Ubuntu 23.04
Kernel Level: 6.2.0-33-generic
Build Version: #33-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 5 14:49:19 UTC 2023
Processor Architecture: x86_64

X Server Vendor: The X.Org Foundation
Window Manager: GNOME Shell
Display manager: /usr/sbin/gdm3

SlickEdit Pro 2022 (v27.0.2.0 64-bit Qt4)

Serial number: VLX930448
Licensed number of users: Single user
License file: /home/chris/slickedit-pro2022/bin/slickedit.lic

Build Date: April 25, 2023   (State file: August 7, 2023)
Emulation: CUA

OS: Linux
OS Version: Ubuntu 23.04
Kernel Level: 6.2.0-33-generic
Build Version: #33-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 5 14:49:19 UTC 2023
Processor Architecture: x86_64

X Server Vendor: The X.Org Foundation
Window Manager: GNOME Shell
Display manager: /usr/sbin/gdm3

Memory: 74% Load, 8502MB/11351MB Virtual
Shell Information: "/home/chris/slickedit-pro2022/bin/secsh" -i
Screen Size: 3840 x 2160

Project Type: Gnuc
Language: .c (C/C++)
Encoding: UTF-8, no signature

Installation Directory: /home/chris/slickedit-pro2022/
Configuration Directory: /home/chris/.slickedit/27.0.2/
Migrated from: /home/chris/.slickedit/26.0.3/
Spill File: /tmp/$slk.chris.1667411

Hotfixes:
/home/chris/.slickedit/27.0.2/hotfixes/hotfix_se2702_11_cumulative.zip Revision: 11   (currently loaded)
/home/chris/.slickedit/27.0.2/hotfixes/hotfix_se2702_5_cumulative.zip Revision: 5   (superseded)

Graeme:
You could try a key logger e.g. logkeys, just in case it's the O.S.

There's a little bit of information here on performance issues
https://community.slickedit.com/index.php/topic,19160.msg76331.html#msg76331

Chris Nisbet:
Thanks. I'll check out those SE options mentioned in that other thread.
SE is the only app affected, which makes me doubtful the the OS is the culprit. I'll investigate that as well though.

Chris Nisbet:
Hmm, logkeys does at least confirm for me that the keys are being entered in the order I think they are, suggesting that it's SE that's getting something wrong.

Graeme:
If it's not hard to repro, and it's associated with a screen freeze, you could try the slick C profiler and see what is happening when it freezes.

Navigation

[0] Message Index

[#] Next page