Bug 7033

KeyDownevent (DataWindows) documentation about return value is WRONG 12 October, 2021

mike S
29 July, 2021
Product: PowerBuilder Category: Documentation
Version: 2019 R3 Build: 2703
Classification: Sybase (legacy) bug Publishing: Public
Priority: P4
Status: Scheduling Reason:
Mark Lee @Appeon 12 October, 2021
#4
Hi Mike,

Thank you for reporting this issue! We will correct the documentation.

Regards,
Mark Lee
mike S 30 July, 2021
#3
no follow up required
Mark Lee @Appeon 29 July, 2021
#2
Hi Mike,

Thanks for report the problem. 
We are working on it and we will get back to you after analyzing it.
We'll keep you posted here!

Regards,
Mark Lee
Hi Mike,

Thanks for reporting this documentation issue.
I'll transfer it to the respective team for their review and feedback.

Regards,
Francisco
mike S 29 July, 2021
*Phenomenon:
Current documentation states:

Return Values
There are no special outcomes for this event. The only code is:
0 -- Continue processing

This is wrong and has been wrong at least as long as setactioncode has been obsolete (20 years?!)

There is a return value of 1 as well:
1 = reject (ignore) the keystroke

I assume that return value of 1 is the only special processing, but that is only a guess.

*Reproduce Steps:


Remarks:
There are a few topics on keydown and they are NOT linked to each other in help.
1) KeyDownevent (DataWindows)
2) KeyDownPowerScript function
3) Examples of user event scripts    Examples of user event scripts 

Also, #3 - shows the use of return value 1, but the example is extremely out of date.  

Your documentation people should search on obsolete terms in the help (such as setactioncode) and fix them in help.  The way it is written now, you are encouraging people to use setactioncode!
OS:
All
Platform:
Database Type:
Database Version: