Make the help keyboard more functional

[GoogleCodeExporter]

#WZ 1.7~ reported by dr. Carbon
how about pop-up menu with Hide option if user right click on the keyboard?

This is a good point. He also recommends tracking the mouse and allowing
the user to type with the mouse, since it is (after all) a virtual keyboard.

I will add a config option to disable the help keyboard, but let's add some
run-time support for this too.

Will wait for the 1.7 release.

Original issue reported on code.google.com by seth.h...@gmail.com on 27 Mar 2009 at 7:58

• Blocking: #89

[GoogleCodeExporter]

I'm going to start testing to see how easy/difficult it is to track the mouse 
position and respond to events. 

Original comment by seth.h...@gmail.com on 18 Aug 2010 at 7:05

• Changed state: InProgress

[GoogleCodeExporter]

From the SVN:
Highlighting works on both windows with one major problem:
  1) If you minimize and then maximize, the window won't update. In other words, keys will remain highlighted, etc.

Also check:
  2) Make sure we're actually ignoring MemoryWindow region updates when the window is minimized. I don't think we explicitly check this like we do for the help window.

Once these two are fixed, I'll mark this bug as fixed.

Also:
  After closing this, I'll split the "highlight keys" bug into its own issue, since it involves a bit more than just registering a ton of key events. (For example, we need some kind of nice, efficient region detection algorithm).

Original comment by seth.h...@gmail.com on 20 Aug 2010 at 8:34

Attachments:

• minimize_wz.png

[GoogleCodeExporter]

Fixed. 

There's a minor issue with, e.g., dragging the memory window on top of the help 
window and then expecting highlights to work, but it'll only really become 
obvious when we start playing with virtual key highlights, so I don't want to 
address it until then.

Original comment by seth.h...@gmail.com on 20 Aug 2010 at 9:37

• Changed state: Fixed