Issue 27141 - Alt plus W failing to register
Summary: Alt plus W failing to register
Status: CONFIRMED
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1.1
Hardware: All Windows XP
: P4 Trivial (vote)
Target Milestone: AOO PleaseHelp
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2004-03-30 13:01 UTC by shmuelh
Modified: 2013-07-30 02:18 UTC (History)
4 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description shmuelh 2004-03-30 13:01:53 UTC
I'm not sure if this is an OO problem.

Because of the fact that OO does not allow one to record a macro which starts 
in another document and concludes in another, I was forced to use an outside 
utility, Macro Express, to record a macro. The macro starts with a Selected 
passage in Document 1, copies it (using Control C) then uses ALT W to go to 
the "Window" setting. It then has the Down Arrow go down until it finds the 
second document. It then uses <enter> to go into the second document. It then 
copies the phrase in (Ctrl V).

I find that sometimes this doesn't work, and that the phrase is copied into the 
first document.

Now my problem: I checked what the cause is, and it is that ALT W (or ALT 
anything) has stopped working, so obviously there is no switch from one 
document to the other. Nothing I do gets OO to recognize the ALT key 
combination.

I've tried to leave OO and reenter, but that made no difference - the ALT 
combinations didn't register. Only after I restarted the computer did I get the 
Alt to respond again.

I realize now that I might not have needed to restart if I went into the 
Windows Task Manager and closed OO in it. I'll try that next time.
Comment 1 shmuelh 2004-03-30 14:13:07 UTC
This just occurred again. I went to Windows Task Manager and closed the OO open 
file (54 Meg!). When I reopened Oo, the problem had been solved.
Comment 2 michael.ruess 2004-03-31 09:04:56 UTC
MRU->ES: pls have a look. Looks like, that under certain circumstances the Menu
shortcuts (Alt-anything) do not work anymore.
Comment 3 shmuelh 2004-03-31 13:07:32 UTC
I think I solved it. I am using XP Hebrew-enabled. In this mode, you can rotate 
between English and Hebrew by pressing Left Shift - Alt. Sometimes, I find that 
my English suddenly switches to Hebrew. Why? Probably some Microsoft quirk. I 
think that the problem occurs when I am in Hebrew keyboard mode. In that 
situation, while I'm pressing ALT-W, in reality the program sees this as ALT 
plus the Hebrew <single quote> mark. If I recycle to the English mode, ALT-W 
works again.

This in essence means that all ALT + letter combinations (File, Window, Help, 
etc.) will not work when the Hebrew keyboard is active.

My suggestion is that somehow the program should be able to recognize ALT + the 
<single quote> mark as the equivalent of ALT - W, and so on for all the Alt 
combinations.

Incidentally, I just checked MS Word with Hebrew installed. Alt-W works whether 
you are in the English or Hebrew keyboard.

I'd appreciate if you'd let me know if my analysis holds up and whether this 
can be remedied.

 
Comment 4 utomo99 2004-05-18 04:36:04 UTC
Utomo > shmuelh:
1.0.3 is too old, please also try newer version. 
regarding windows behaviour you must contact microsoft for that :(

add sforbes, hebrew QA member.
Comment 5 sforbes 2004-05-18 05:08:28 UTC
1) OOo 1.0 has no Hebrew support. Are you sure that is the version that you are
using? (Hebrew support was added with 1.1)

2) On my Linux, the kayboard shortcuts still work when I am in Hebrew (alt O for
example for the Open Dialog). 

I don't have Windows here at the moment. Can someone with Windows please text
this and verify the bug?
Comment 6 shmuelh 2004-05-18 05:57:00 UTC
I've tested it on 1.1.1 and on the beta 680 (build 40), and it still has the
same problem when you have the keyboard set to Hebrew. (I have XP.)

I believe this problem is probably surmountable, because when I used to use MS
Word I found that the Alt+letter combinations worked even when the Hebrew
keyboard was active. 
Comment 7 eric.savary 2004-10-23 22:55:47 UTC
ES->cp: Please have a look
Comment 8 sforbes 2004-10-23 23:15:38 UTC
"I've tested it on 1.1.1 and on the beta 680 (build 40), and it still has the
same problem when you have the keyboard set to Hebrew. (I have XP.)"

Sounds like a dup of issue #31653 (althugh for me on Linux, it did work in 1.1.x)
Comment 9 christof.pintaske 2004-10-25 17:23:41 UTC
cp->ssa: do you have an immediate fix for this ? if there is no instantious
solution we will have to retarget it to later. 
Comment 10 stephan_schaefer 2004-10-27 16:17:07 UTC
There is no easy fix available and in fact all Windows applications suffer from
it, even MS Office to a certain degree.
First, no standard Windows application except MS Office is capable of dealing
with menu shortcuts (Alt+letter) when in Hebrew input mode (tested with Notepad,
Explorer, WordPad, Mozilla suite)
Second, even MS Office cannot deal with it in dialogs - the mnemonics just don't
work. 

The problem is what keyboard mapping should I choose when the keyboard just
reports hebrew letters ? MS Office seems to fall back to english, which becomes
obvious when I try to select the menu entry "Zoom" with a german keyboard where
y and z are exchanged when compared to an english keyboard. I actually have to
type 'y' to select Zoom...
We could at least try to have it working that way, although this is no perfect
solution.

To solve the problem within your macro, just use F10 and the cursor keys to
navigate through the menu.
Comment 11 shmuelh 2005-05-24 13:31:51 UTC
I'm using 1.1.4, and it's the same problem - ALT+Letter not responding when the
keyboard is set for Hebrew. But I just got a solution! (Thanks to my friend
Perry Zamek - give credit where it's due!). Instead of ALT+Letter, use
ALT+Shift+Letter. It works like a charm whether in the English or Hebrew
keyboard! I modified my macro (in Macro Express)accordingly, and the problem is
solved!

Maybe this fact should go into a FAQ file somewhere to prevent others from
having the same problem?
Comment 12 stephan_schaefer 2006-11-30 11:23:24 UTC
reassigned
Comment 13 Rob Weir 2013-07-30 02:18:28 UTC
Reset assignee on issues not touched by assignee in more than 2000 days.