Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ Widgets - General questions or Mixed problems » AK example and/or key_source bug? (The key tables or hash or something isn't working right for key '1')
AK example and/or key_source bug? [message #44054] Fri, 19 December 2014 15:04 Go to previous message
rainbowsally is currently offline  rainbowsally
Messages: 29
Registered: December 2014
Promising Member
Using Linux.

In the AK demo/example where we input new key bindings for the menu selections, when I enter Ctrl-1 for the key to trigger the first menu item using the top row keys on my keyboard the code isn't right. When I use the '1' on the keypad it is.

The demo works, but the encoding doesn't.

Number '2' encodes and decodes correctly in the top row keys. I could'nt see where the problem was coming from -- just guessing it's a key table.

Sorry if this has been addressed already. There's a LOT of material here.

Smile

Also, when I change the language to Czech, only the second menu item changes.

[Edited...]

I see now that this is (apparently?) intentional.

KEY(FN1, "First function", K_CTRL_M)

KEY(FN2, t_("Second function"), K_CTRL_W)

KEY(EXIT, t_("Exit"), K_CTRL_Q)


FN1 doesn't get translated.

Good hacking exercise. Smile But the key encoding.. that's a bit advanced.

[Updated on: Fri, 19 December 2014 15:10]

Report message to a moderator

 
Read Message
Read Message
Read Message
Previous Topic: Drop list is not shown
Next Topic: Using a Button to load a window/form using Run. THISBACK syntax
Goto Forum:
  


Current Time: Sun Jul 21 19:32:53 CEST 2024

Total time taken to generate the page: 0.02367 seconds