Keyboard location problem

When I need to type and the keyboard appears, it now shows up in the middle of the screen instead of at the bottom. Makes it next to impossible to see what yo're typing. How to I change setting to put it back at the bottom?

When the keyboard is visible tap and hold on the keyboard key at the lower right of the keyboard. A menu will appear with a choice to dock the keyboard.
You can turn off the ability to undock and split the keyboard in Settings.

Similar Messages

A possible solution for "foreight language keyboard shortcut" problem...

Hi(Bonjour)!
Everyone know the problem of losy keyboard layout when Final Cut is used with foreight language keyboard. We loose the COMMAND-Q shorcut.
As PieroF suggested in many posts in final cut express forum, there is a workaround:
"+I just installed Leopard and I ran into this keyboard shortcut problem.+
+I can confirm that:+
+a. the problem exists also with the Italian keyboard (in addition to other languages, as pointed by other posters)+
+b. the workaround I described in my previous answer works fine :+
+- close FCE (if open)+
+- open System Preferences/International/Language+
+- drag English to the first place on top of the other languages+
+- drag your own language (Italian in my case) again on top of English (at the end the window will show the same original settings, but something happened in the heart of Leopard...)+
+- close System Preferences+
+- open FCE: now all shortcuts work as expected, and are correctly listed with their corresponding menu commands+
+It's a workaround, it's not convenient (I'd better have this bug fixed), but apparently you have to apply it only once for each system startup.+
Piero "
As stated by Piero, you have to follow this procedure after each computer startup.
I found a way to restore the COMMAND-Q shortcut with the keyboard and mouse system pref panel.
Simply add Final Cut application and add a +custom shotcut+. Be careful to type exactly the "Quit Final Cut Express" menu.
This solution allows to restart the computer.
It's work with Final Cut Express and Final Cut Pro under Leopard 10.5.4.
Michel Boissonneault

Hi Michel,
I like your suggestion because the keyboard shortcuts defined in the system preferences do not require redefinition at each startup. So in theory we could define all missing/wrong shortcuts this way, and not only the cmd-Q as you suggested. Boring, but we could do it once for all.
The only problem is that I don't know how to define shortcuts for submenus, for example "Render Selection/Both": it seems system preferences allows only to define shortcuts for the menu ("Render Selection" - in this case absolutely useless) but not for the submenu.
Do you know a way ? (I looked in the help, which didn't... help).
Piero

Weird dreamweaver keyboard mapping problem

weird dreamweaver keyboard mapping problem:
Hope this solution helps someone out. If you have q's, ask
and I will try to help.
I was having a weird problem in dreamweaver... Whenever I was
in code view and typed "shift+i" to make a capital "I", instead it
would paste from the clipboard.
I finally figured out what was happening. I compared the
menu.xml in my app support folder in the user library to the
original menu.xml file that was in the application folder. I went
through until I came across the diff:
menu.xml in my library/app support folder:

<shortcut key="Cmd+Ins" name="Copy2" platform=""
command="if (dw.canClipCopy()) { dw.clipCopy() }"
domRequired="FALSE" id="DWShortcuts_HTMLSource_Copy2" />
<shortcut key="Shift+Ins" name="Paste2" platform=""
command="if (dw.canClipPaste()) { dw.clipPaste() }"
domRequired="FALSE" id="DWShortcuts_HTMLSource_Paste2" />
<shortcut key="Shift+Del" name="Cut2" platform=""
command="if (dw.canClipCut()) { dw.clipCut() }" domRequired="FALSE"
id="DWShortcuts_HTMLSource_Cut2" />
orig menu.xml file:

<shortcut key="Cmd+Ins" name="Copy2" platform=""
command="if (dw.canClipCopy()) { dw.clipCopy() }"
domRequired="FALSE" id="DWShortcuts_HTMLSource_Copy2" />
<shortcut key="Shift+Ins" name="Paste2" platform=""
command="if (dw.canClipPaste()) { dw.clipPaste() }"
domRequired="FALSE" id="DWShortcuts_HTMLSource_Paste2" />
<shortcut key="Shift+Del" name="Cut2" platform=""
command="if (dw.canClipCut()) { dw.clipCut() }" domRequired="FALSE"
id="DWShortcuts_HTMLSource_Cut2" />
There was a diff in the "platform=" tags. The orig stated
[platform="win"], my config stated [platform=""] (nothing in
between the ""'s). So, I reset the platform tag to be
[platform="win"] in my settings and then relaunched dreamweaver. It
fixed the problem.
Not sure how this occurred, but it works now.

Calling1.4.1 signed applet from Javascript causes keyboard/focus problems

Pretty sure there's a JRE bug here, but I'm posting to forums before I open one in case I'm missing something obvious :-)
This issue may be specific to IE, I haven't tested elsewhere yet. Our web application is centered around a signed applet that is initialized with XML data via Javascript. We first noticed the problem when our users started upgrading from the 1.3.x plug-in to the 1.4.x plug-in. The major symptom was that shortcut keys stopped working. I debugged the problem off and on for about a month before I boiled it down to a very simple program that demonstrates the issue (included below). Basically, the program has a function that adds a JButton to a JPanel and registers a keyboard listener (using the new DefaultKeyboardFocusManager class) that prints a message to the console. This function is called by the applet's init() method, as well as by a public method that can be called from Javascript (called callMeFromJavascript()). I also included a very simple HTML file that provides a button that calls the callMeFromJavascript() method. You can test this out yourself: To recreate, compile the class below, JAR it up, sign the JAR, and put in the same dir with the HTML file. Load the HTML file in IE 5.0 or greater, and bring the console up in a window right next to it. Now click the button that says init--you should see the small box appear inside the button that indicates it has the focus. Now press some keys on your keyboard. You should see "KEY PRESSED!!!" appearing in the console. This is proper behavior. Now click the Init Applet from Javascript button. It has removed the button called init, and added one called "javascript". Press this button. Notice there is no focus occurring. Now press your keyboard. No keyboard events are registered.
Where is gets interesting is that if you go back and make this an unsigned applet, and try it again, everything works fine. This bug only occurs if the applet is signed.
Furthermore, if you try it in 1.3, signed or unsigned, it also works. So this is almost certainly a 1.4 bug.
Anyone disagree? Better yet, anyone have a workaround? I've tried everything I could think of, including launching a thread from the init() method that sets up the components, and then just waits for the data to be set by Javascript. But it seems that ANY communication between the method called by Javascript and the code originating in init() corrupts something and we don't get keyboard events. This bug is killing my users who are very reliant on their shortcut keys for productivity, and we have a somewhat unique user interface that relies on Javascript for initialization. Any help or suggestions are appreciated.
================================================================
Java Applet (Put it in a signed JAR called mainapplet.jar)
================================================================
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
public class MainApplet extends JApplet implements KeyEventDispatcher
    JPanel test;
    public void init()
        System.out.println("init called");
        setUp("init");
    public void callMeFromJavascript()
        System.out.println("callMeFromJavascript called");
        setUp("javascript");
    private void setUp(String label)
        getContentPane().removeAll();
        test = new JPanel();
        getContentPane().add( test );
        JButton button = new JButton(label);
        test.add( button );
        test.updateUI();
        DefaultKeyboardFocusManager.getCurrentKeyboardFocusManager().addKeyEventDispatcher(this);
    public boolean dispatchKeyEvent(KeyEvent e)
        System.out.println("== KEY PRESSED!!! ==");
        return false;
}================================================================
HTML
================================================================
<form>
<APPLET code="MainApplet" archive="mainapplet.jar" align="baseline" id="blah"
     width="200" height="400">
     No Java 2 SDK, Standard Edition v 1.4.1 support for APPLET!!
</APPLET>
<p>
<input type="button" onClick="document.blah.callMeFromJavascript();" value="Init Applet via Javascript">
</form>

I tried adding the requestFocus() line you suggested... Same behavior.
A good thought, but as I mention in my description, the applet has no trouble gaining the focus initially (when init() is called). From what I have seen, it is only when the call stack has been touched by Javascript that I see problems. This is strange though: Your post gave me the idea of popping the whole panel into a JFrame... I tried it, and the keyboard/focus problem went away! It seems to happen only when the component hierarchy is descended from the JApplet's content pane. So that adds yet another variable: JRE 1.4 + Signed + Javascript + components descended from JApplet content pane.
And yes, signed or unsigned DOES seem to make a difference. Don't ask me to explain why, but I have run this little applet through quite a few single variable tests (change one variable and see what happens). The same JAR that can't receive keyboard events when signed, works just fine unsigned. Trust me, I'm just as baffled as you are.

Which part of the machine is related to the keyboard flex problem ?

Mine is T420s
And I got a keyboard flex problem.
Actually which part is related to this problem ?
Isn't it inclusive to fix this problem in the warranty ?
thx

Mine doesn't exhibit any keyboard flex and I don't think it's a common issue with T420s; anyway:
http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T420s-Keyboard-Flex/td-p/454851/highlight/t...
http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/t420s-keyboard-flex/m-p/755255/highlight/tr...
T420s i5-2520M HD3000 480GB Crucial M500 SSD 8GB RAM Ericsson F5521gw
T430 i5-3210M HD4000/NVIDIA 5400M 512GB Crucial MX100 SSD 12GB RAM Ericsson H5321gw

(foreign) keyboard mapping problems

Many people, myself included, have voiced problems with keyboard mappings since updating to Leopard. It appears to particularly afflict people with non-US keyboards, but I may be wrong.
Does anybody out there have a generic fix? Manually modifying the keyboard map as the Latvians did seems to address (some of) the symptoms, not the underlying problem. Accordingly, it doesn't appear to be a general fix, as reported here:
http://m10lmac.blogspot.com/2007/10/fixing-leopards-latvian-keyboard.html
Here are some of the other posts I saw/wrote that make me think this is a SIGNIFICANT PROBLEM IN LEOPARD:
http://discussions.apple.com/thread.jspa?messageID=5794935&#5794935
http://discussions.apple.com/thread.jspa?messageID=5644709&#5644709
http://discussions.apple.com/message.jspa?messageID=5688731#5688731
http://discussions.apple.com/thread.jspa?messageID=5854794
http://discussions.apple.com/thread.jspa?messageID=5788789

Does anybody out there have a generic fix?
There is no generic fix because the problems are unrelated, except to the extent they represent goofs in creating certain files and failure to find these before release.
The Latvian keyboard issue is caused by errors in a particular .keylayout file. I don't know of any other similar layout with the same problem (In Tiger it was Macedonian and Romanian which had such errors). The Hanin Chinese IM problem is caused by errors in a couple of files particular to it -- all the other Chinese input systems have correct mappings. The X11 keyboard mapping problem concerns a different part of OS X than the others. The issues of QWERTY/AZERTY/QWERTZ in Chinese input were present in a different fashion in Tiger and earlier and many people have switched to a different IM called QIM to solve it. Having a dead Apple key is not related to ordinary character mapping issues.
Your own issue with ViaVoice is not totally clear to me, will try to respond in that thread.

XSD Location Problem.

Hi Gurus,
After starting the node in a cluster environemnt, often receiving "Unable to load Translation schemas from for http://xmlns.oracle.com/BRM/schemas/BusinessOpcodes due to: XSD Location problem.
XSD Loading problem."
This is mainly observed in BRM schemas, has anyone exprienced this? what shall be the workaround/solution other than restarting the container/application?
We are using SOA 10.1.3.4 MLR 8 and Oracle AIA 2.4.
Please help.

The BRM schemas are present in the AIA Components which will be referred by the load balancer url in a clustered environment. However, if in any of the nodes, the url for AIA Components has the local node url instead of load balancer url, this issue occurs.
Identify the node which is giving the issue (shutting down one node at a time and retrying the operation which gives the error). In the node which has the issue, try doing a search on AIA components to find out if there is any reference using local node url instead of load balancer.
If you find any, replace with the load balancer url. I had faced a similar issue and I was able to resolve it as I have mentioned above.
Cheers,
- AR

Storm9530 Location problem??

Hi, i live in Canada and recently purchased a used and unlocked BB Storm 9530 off the internet from texas USA. I am using the phone Pre-paid for the time being and for some reason my calls I make are costing me a fortune. I live in a border-town with a US town right on the american side but since the phone is pre-paid it cant roam. Ive talked to my cell phone company about this and they said for some reason the phones is calling internationally and its not the service itself. The phone is manually selected for my home network and i just cant figure it out. is it because the phone is an american phone? is there any way of checking more into this because i cant even use my phone to call because $5.00 for a 15 second call is rediculous. please help!

sherrdrew wrote:
Does anyone know if Apple is ever going to fix the location problem. I live in IL and my Ipad thinks I'm in NC. I'm lucky though, searching the problem on the net I found most people who live in the US are having Ipad that think they live in Europe and Germany. At least mine is on the same side of the world.
What a totally ridiculous claim. Most iPad owners have no problems at all in this area. The fact that you are is invidual to you and your case and, absent any useful information at all in your two posts aside from "Hey, it ain't working ...", I guess we could guess that your problems are due to the fact that
a. You don't have a 3G model, and therefore you don't have GPS, or ..
b. You do, but it isn't working right, or ..
c. You do, and it's working right, but PEBKAM, or ..
d. You don't have a 3G model, and your iPad is unable to resolve the local WIFI data to generate a rough location, or ...
e. Same as d. above, but the local wifi datafields are simply incomplete or incorrect, or ...
f. Yadda yadda yadda ......

Potential keyboard hardware problem T410

Dear all,
since yesterday I have been experiencing a problem with my T410, which is potentially due to
a hardware issue with the keyboard.
A few specific keys are not working anymore. These seem to be the Power On key, the Fn key,
the Alt Gr key, and the ThinkVantage key.
I am assuming it is a keyboard hardware problem, since I cannot use the Power On button to
start the laptop. Fortunately, this is possible using the fingerprint reader start-up.
When the laptop is running (using Windows 7) everything is working fine, except the mentioned
buttons. I cannot access any Fn button functions (e.g. the reading lamp) or Alt Gr symbols (e.g.
the @ symbol which is on my keyboard on the 2 button) or power down with the Power button.
I tried various easy fixes:
* Making sure all drivers are up to date
* Remove and reattach the keyboard
* Static discharge procedure (unplug all power, 10 presses and 30 sec holding of power button)
* Checking Bios settings
* Replace battery
Unfortunately, these did not change the situation.
I am wondering if the simultaneous malfunctioning of these specific buttons points to a certain
hardware problem. I hope a replacement of the keyboard might solve this, but it could be an
issue with the motherboard.
Any hints would be welcome.
Thank you,
MH
Solved!
Go to Solution.

Dear all,
thank you for your suggestions. Unfortunately, it was not the keyboard. It appears to
be a more serious problem. In fact, since yesterday the laptop does not boot correctly
anymore. The boot process is started, but I only end up with a black screen, and some
randomly colored first few lines at the top of the display.
It all points to a major malfunction. Unfortunately, the warranty expired 3 months ago...
Regards,
mh

Autocomplete text popup location problem

Hi,
I encounter a autocomplete text popup location problem
whereas the popup location is always located few cm below the textBox itself.
Any idea how to solve this?
Is there any property i need to set in order to prevent this?
I am using BluePrints Ajax Component by the way.
Thanks

yea.
i think that is the problem.
i have a autocomplete textfield under groupPanel and this groupPanel is located under gridPanel
and the resultiing popup list is located outside the panel itself.
Thanks.
Can u refer me to the bug URL?
is there any workaround for this?
Thanks

Keyboard layout problem at the login screen

Hi there!
I'm having a huge problem at the login screen just after installing OS X Lion 10.7. It seems like the keyboard layout has changed, and I need to enter some numbers in my password. I can't find the digit 9, and I really don't know if the other numbers are in the right place either. Maybe it's changed to a us layout.. What to do?

stoneheart,
the numbers are in the same position on a US English keyboard as they are on a Norwegian keyboard.
If you select the Users & Groups pane of System Preferences, and select its Login Options, do you have the “Show Input menu in login window” checkbox checked? (That’s where the checkbox’s location is in Mavericks; I don’t have Lion, so I don’t know if it’s in the same location there.)

More Keyboard Viewer problems ...

Hi - I'm trying to see the Keyboard Viewer. According to help,
1) Choose Apple > System Preferences and click International.
2) Click Input Menu, then select the checkbox next to Keyboard Viewer.
3) Choose Show Keyboard Viewer from the Input menu on the right side of the menu bar (the one that looks like a flag or alphabetical symbol).
#3 is where I'm having problems. I click the checkbox next to Keyboard viewer but am unable to find the 'Show Keyboard Viewer' command. I am assuming something will pop up when I do this? (Or perhaps I've already done it and nothing happens. If this is the case - then what? How do I see the selected keyboard layout?)
I'm assuming this is the way I'll be writing french words (with accents) into my document?
Julie

HI JCanlis,
Ok.. number 3. When you click the "flag" and see the check mark, just below that the pop up menu doesn't say: Show Character Palette and Show Keyboard Viewer? Make sure when you click on the flag to allow the pop up menu to appear and scroll down to Show Keyboard Viewer.
If you still can't prompt the Keyboard Viewer try this. Locate this file:
com.apple.HIToolbox.plist It's here: MacinoshHD/Library/Preferences.
Open the Preferences folder, locate that file and drag it to the Trash. Reboot. It's ok to Trash a preference file, your Mac will create a new one for you.
Post back if you still need help...
Carolyn

Which heading for posting apple keyboard hardware problems?

I'll apologize in advance, but I'm having a little difficulty locating a forum heading for posting about problems involving the Apple aluminum keyboard hardware. Specifically, I've been getting little electrical shocks once in a while from the keyboard. If someone would kindly directly me to the proper forum heading, I'll post about my problem over there.
Thanks!

Hi nconrads!
Maybe posting in the Using Your Mac Pro Forum, would produce some additional, helpful suggestions.
Others with the same hardware, may be experiencing the same issue.
ali b

Keyboard Backlighting Problem

Hello,
Recently, if i use the f5 or f6 keys to raise or lower the level of illumination on my laptops keyboard, the semi-transparent window comes up with the horizontal bar and the blocks to indicate brightness level, but has a O with a slash through it underneath the row of blocks, and neither keys have any effect.
I went to system preferences, enabled "illuminate keyboard in low light conditions" and it lit right up. I then tried to use the keys once it was already lit in this manner, and they functioned RIGHT until I uncovered the iSight camera (I covered it to cut off all light).
Any help?
Thanks in advance, and Happy Holidays!

Just to add to eww's observations, it seems to me that the location of the sensor in the upper bezel next to the iSight camera adds to the problems quite a bit. I find myself that the light falling on this point can be quite different from that falling on the keyboard itself. Simply changing the angle of the screen, or altering ones sitting position can produce substantial variations in the behaviour of the backlight. We have high "clerestory" windows in our house for example, and if I sit with my back to them the light hitting the light sensor can be far greater than the light falling on the keyboard itself.
I can see pluses in the location , too, especially on a small keyboard like the 13" one where ones hands would be likely to interefere with illumination levels, but by and large I think the location on the early MBPs under the speaker grids on either side of the keyboard was superior.
Maybe rather than using "blackout" tape, some sort of semi transparent filter material over the sensor would be an option?
Cheers
Rod

Keyboard/trackpad problems - are Macbook top cases too fragile?

I'm starting to wonder if the top case with keyboard/trackpad is the Achilles heel of the black and white Macbooks 2007-08. I'm having problems with 3 different Macbooks.
On one, a 2.1Ghz from 2008, no internal keyboard/trackpad is recognized by the Macbook. Its original kb/tp just stopped working one day. I removed the top case and checked the connections, as well as any dust or bent pins in the socket on the logic board, but all seemed ok. Reassembled, but kb/tp still not working. I then replaced the top case with another one that I knew was working, but still no go.
Any ideas? The MB boots fine (even with the original top case installed) and works great with external kb/mouse.
On a second, a 2.16Ghz from 2007, the kb/tp suddenly stopped working one day. I'd opened the MB a couple of times just before, but I'm pretty careful and don't think I broke the cable or anything else. All the pins and the cable seem fine, as does the socket on the logic board. Here too, an external mouse/kb work perfectly.
I tried another working top case and this time it seemed to work okay. But after a day or two, it stopped working too. I then reassembled it, thinking there might be something pushing up on the keyboard, or maybe some screws loose. And once again it seemed to work.
I also noticed something odd: a couple of times at first, when I'd just reassembled the top case, the kb/tp weren't recognized. But then when the MB woke from Sleep, I heard the hard drive and DVD spin up, and suddenly the kb/tp were working again.
Anyway, after a couple of days the kb/tp stopped working again.
Question: how can the kb/tp work for a couple days, then suddenly stop working? If it were broken, wouldn't it always not work?
The 3rd Macbook is a 2.0Ghz Core 2 Duo from early 2007. Its kb/tp stopped working too (unrecognized by system, etc.). I swapped the kb/tp from the 2008 2.1Ghz onto it and this seems to have fixed the problem. It's been a few weeks now and I haven't had any trouble with it.
Question: would swapping in the top cases from different models create any problems? I see that they sometimes aren't perfect fits in terms of looks, but the screws are in the same place and everything installs pretty solidly. IIRC you have to be careful re. mixing top cases with an orange trackpad cable and a silver one, but in my case all of them had silver cables.
This is really getting to be a problem. I've got the 2 fast well-upgraded Core 2 Duo Macbooks sitting here, working perfectly apart from the kb/tp.
Any ideas greatly appreciated.

Sorry, just wanted to add in concluding that there seem to be 2 different problems.
1) with the 2.1Ghz from 2008, no working top case seems to work, so it doesn't seem to be a top case problem, but rather a problem with the connection to the logic board or somewhere else.
2) with the 2.16 from 2007, here it does seem to be a problem with the top case.
Unfortunately I don't have what I know to be a good, working top case to try on the 2.16. I think with all the assembling/disassembling, the semi-decent kb/tp I had may now have problems too.

Keyboard location problem

Similar Messages

Maybe you are looking for