Users cannot run WaitZar and a non-Roman Windows keyboard layout at the same time

[GoogleCodeExporter]

See title.

This is probably because they both share the keyboard shortcut Ctrl+Shift.
Even if WaitZar is used exclusively, they might still have other layouts
for other languages.

A solution might include listing keyboard layouts:
http://msdn.microsoft.com/en-us/library/ms646297%28VS.85%29.aspx

...and then doing some math (e.g., "if the user hits Ctrl+Shift then switch
to the next keyboard. If at the end, switch to WaitZar. If at WaitZar,
switch to the first layout.").

However, we then need to handle issues regarding Hotkey registration. This
is probably easy, but it will require a lot of testing. Anyway, this is not
for release 1.7. I'd rather have multiple input methods within WaitZar
before I consider this bug, lest we end up with a temporary solution that
needs re-fixing later on.

Original issue reported on code.google.com by seth.h...@gmail.com on 24 Feb 2009 at 7:22

[GoogleCodeExporter]

It might be more than this: 
  If Zawgyi is activated via the menu, then its keys will re-map. I've already fixed this for LetterBasedLayouts.

This brings up an interesting question: if users are typing in a non-roman 
alphabet (like using Zawgyi) then maybe we SHOULD re-map for WaitZar and other 
Roman inputs. This is.... very confusing. For now, we'll keep it as it is.

Original comment by seth.h...@gmail.com on 22 Jun 2010 at 9:47

[GoogleCodeExporter]

I'm not sure if this bug should remain open, since WaitZar now allows typing in 
Zawgyi anyway. But I'll change the title to make it more accurate.

Original comment by seth.h...@gmail.com on 9 Jan 2011 at 1:33

• Changed title: Users cannot run WaitZar and a non-Roman Windows keyboard layout at the same time