backspace is dead in Gtk2 version 1.208.5 about cudatext HOT 22 CLOSED

can do it later

from cudatext.

@veksha confirmed. I will report this issue to lazarus bugtracker. thanks.

from cudatext.

I cannot see the problem here.
no, Python is NOT the reason:

a) single-line inputs don't use Python
b) you can set wrong value of "pylib__linux" and it is not the fix

so some system setting is maybe the reason.
What OS / Desktop (on Unixes) and is it Gtk2 or Qt5?

from cudatext.

Debian, Xfce, GTK2.

199 worked well (and again works) and 208.5 doesn't... whether you can reproduce or not.

If I have a little more time I might try interim versions eg 204 etc and see when this first pops up. May take a while though and 199 was pretty stable so no need for me to rush this.

from cudatext.

Notebook with Xubuntu (Debian based) 22 / Xfce.
All works for me (1.202 and 1.209).
in theory it is possible that some OS setting (or app) blocks BkSp key in Cud.

from cudatext.

@veksha sorry, do you have time to install Lazarus 2.2.6
https://sourceforge.net/projects/lazarus/files/Lazarus%20Linux%20amd64%20DEB/
? if you compile Cud with it, we will ask topic-starter to test the binary.

from cudatext.

cudatext.tar.gz

from cudatext.

@tmsg-gh This binary from veksha's post cannot be run on my older Ubuntu 20 (GLIBC version error), can you run it?

from cudatext.

I can run the above binary but alas the backspace key remains dead.

in theory it is possible that some OS setting (or app) blocks BkSp key in Cud.

While that's clearly true, let me re-iterate that every other program I use on that machine (including your own 199 version) has no problems whatsoever with the backspace key.

from cudatext.

I found this text:
https://forums.codeblocks.org/index.php?topic=20834.0

I run here:

apt list |grep ibus-gtk

and got

ibus-gtk3/focal-updates,now 1.5.22-2ubuntu2.1 amd64 [installed,automatic]
ibus-gtk3/focal-updates 1.5.22-2ubuntu2.1 i386
ibus-gtk/focal-updates,now 1.5.22-2ubuntu2.1 amd64 [installed,automatic]
ibus-gtk/focal-updates 1.5.22-2ubuntu2.1 i386

from cudatext.

I am not sure what to make of that. The post you're linking to deals with Jessie (a really ancient version of Debian) and a toolkit called wxGTK.

At any rate, the packages referred to in that post don't exist for my Debian install (bookworm).

I'll stick with what works and will occasionally check newer versions as to whether they support backspace.

AFAIC you can close this issue as you can't repro the problem.

from cudatext.

I mean that my OS has this

ibus-gtk/focal-updates,now 1.5.22-2ubuntu2.1 amd64 [installed,automatic]

and your OS don't have it. so let's try to install ibus-gtk on your OS?

from cudatext.

Again, AFAIC you can close this issue as you can't repro the problem.

from cudatext.

I've again looked into the matter of the dead backspace key, mostly because I found it strange that 208.5 would not work and the previously OK 199 would also stop working after 208.5 has been run once. Here is a sequence as to what I've observed.

1. Starting point is a working 199 installation, ie backspace works.
2. Install 208.5 over 199 and start Cudatext --> backspace is now dead.
3. Copy back the 199 executable only (I tried this as a fast first test) --> backspace is still dead.
4. Restore the full 199 install --> backspace works again.
5. I've tracked the problem to keys.json. After deleting keys.json, no backspace problem with 208.5.
6. However, keys.json (the file) is unchanged after 208.5 has been run once but something else must have changed as the 199 binary doesn't work after 208.5 has been started once.
7. I've manually cleaned up my keys.json and now both 199 and 208.5 work. However I don't know which of my changes did that.
8. A copy of the problematic original keys.json is included. You might be able to repro this strange bug with that and 208.5.

keys.json

from cudatext.

the bad part of key.json:

{
  "152" : {
    "name" : "delete char left (backspace)",
    "s1" : [
      "BkSp"
    ],
    "s2" : [
    ]
  }
}

Cud don't understand string 'BkSp', it understands only 'Backspace' string.
So you can change 'BkSp' to 'Backspace' is backspace works again.
but better delete this part at all.

how did you write 'BkSp' there?

from cudatext.

how did you write 'BkSp' there? - you are OK, it is lazarus issue.
lazarus has 2 functions to convert hotkey to string.

• ShortcutToText --- giving 'BkSp' result for 8
• ShortcutToTextRaw -- giving 'Backspace' result!!! what???

I will study this. at some point Cud changed the used API function so your config - broke the work, sorry.

the remedy - just delete that part from config keys.json.

from cudatext.

Also some key names are different between gtk and qt versions of Cud.

from cudatext.

@veksha What is the list of different keys?

from cudatext.

As you realised I didn't write anything into keys.json, I always use F1/F9 for that, so any invalid string is Cudatext's doing.

lazarus has 2 functions to convert hotkey to string.
Also some key names are different between gtk and qt versions of Cud.

Sounds like a recipe for more disasters. More consistency would help?

from cudatext.

Also some key names are different between gtk and qt versions of Cud.

@veksha means (I guess) then top menu shows different hotkeys in Gtk2/Qt5 versions. don't worry, this display in menu does not affect any configs, it is separate code (one in gtk2, one in qt5, one in windows). it is not reason for a bug.

BTW, the same issue (as 'BkSp' vs 'Backspace') is here for 'PgDown' vs 'PgDn'. i will fix it too. next update of Cud.

from cudatext.

@veksha means (I guess) then top menu shows different hotkeys in Gtk2/Qt5 versions

no. i mean:

if you assign ` key (near 1 key) - Qt5 Cud will show Num0 for it.
- key (near 0 key) - Qt5 Cud shows NumMinus
shift+= keys - Qt5 Cud shows Shift+NumPlus (without shift it shows =)

Gtk2 version will show correctly: `, - and Shift+=

from cudatext.

About original issue ('BkSp' vs 'Backspace'). sorry but it won't be changed in lazarus. so the issue will be not fixed. we still have bug if Cud uses old configs with 'BkSp' and 'PgDn' strings. sorry.

the remedy here - is to delete config (keys.json) parts about 'BkSp' and "PgDn".

from cudatext.