Thanks for your suggestion. I tested the suggested solution but unfortunately it doesn't work. (Right alt + Z) AltGr-Z is not called at all in pbm_renkey in TichTextEdit.

I also had problems with Richtext edit checking on keys.

This works, (make sure you don't have any menu in which you have a shortcut for ALT+Z):

if keydown(keyalt!) and keydown(keyz!) then
	post messagebox('debug', "cancelled")
	return 1
end if
return 0

This also works:

if keyflags = 4 and key = Keyz! then
	post messagebox('debug1', "cancelled")
	return 1
end if

return 0

This does NOT work:

// keyflags ...
// 1 = SHIFT
// 2 = CTRL
// 2 = AltGR (like ctrl!!)
// 3 = should be SHIFT+CTRL but does not work !!
// 4 = ALT (undocumented in PB help)

// nevertheless, this should work, but it doesn't:
if keyflags = 4 then
	if key = Keyz! then
		post messagebox('debug', "cancelled")
		return 1
	end if
end if
return 0

Hope it works, this is using the v15 version of the TX text control in PB 2019 R3

regards.

Nothing happens with Alt+Z on mine, but with AltGr ...

If I use the v15.0 version and I type "abcde" and then do AltGr+z,the whole text disappears (English windows and settings).

If I use the v28.0 version, same thing happens. AltGr+z seems to clear the whole contents. (Not too worried about that a user would do that though).

One workaround may be to capture the keystroke ALT-Z and replace it with a command that works in the RTE object ~OR~ simply do nothing. It's better than the UNDO.

Olan

A similar problem exists in the PowerBuilder IDE in all versions. When typing the Polish letter "ż" (Alt-z), the previously entered character is deleted. Years later, Polish programmers learned to handle the problem by typing a space before putting "ż" (Alt-z).

I hope that this bug will be fixed relatively quickly, especially in the RTE editor. I will open the support ticket with this bug.

Regards

I am using Built-in TX Text Control. 

Alt-z problem occurs on all windows 10 and windows 7 computers.

Which RichText option are you using?

can you reproduce same problem on a Windows 10 machine?