|
|
|
Darn... I went an duplicated this one elsewhere. Should have looked harder. Oops. Anyhoo...
I know this seems like such a small thing, but I relied on the escape key to control focus a great deal. It has become an ingrained habit that, after rattling off a chat message or IM, I could automatically hit escape and be free to jump or fly or whatever. It was an invaluable part of my building workflow in world as well. Clicking elsewhere in the window to achieve the same thing works, of course, but this just isn't as convenient. I could get used to an alternate keyboard method... is there one currently? Also broken on Windlight 1.19.0 (79185)
I'm also experiencing this problem.
Thanks for the bug reports and closing dupes! Importing for further investigation.
And... Not only does the ESC not unfocus from editing notecards, it is now failing to unfocus from editing scripts as well.
For some bizarre reason, hitting ESC causes the [View] pull down menu word to highlight briefly as well, regardless of the current focus. (I've been using nothing but WindLight for weeks but this and the online-friend-notifiation quick-freezes ( p.s.: While it does seem to unfocus from IM sessions okay, it does not unfocus from the contacts page. Turns out this is happening on other windows that allow you to type, not just chat, so I revised the title and description slightly. For example, it's keeping the focus inside the search, profiles, inventory... Whew!
Jopsy is right, because View -> Reset View is bound to ESC. The usual behaviour was always to lose focus of the current window first then, if pressed again, reset the view. This has always been good. Though not consistent on some windows. Inventory for example would lose focus AND reset view.
It is quite hindering and annoying since it's always been the way things work. I do hope this won't be the new behaviour, as many of us have got quite used to the old expected behaviour, obviously. I'd love to see the notecard window, and inventory window ESC functionality unified with everything else, if/when this gets fixed. But I understand that the two are probably quite unrelated requests. I hope this one at least is fixed in the next update! Fix for this coming soon (internal reference # is DEV-10046).
SO GLAD a fix is coming! I've heard about this from quite a few people, although many of them weren't able to really quantify what it was that was annoying them until I asked about the escape key and then they said "Oh yeah THAT's it..." It's such a relief to hear this will be fixed soon!
Woot! Unable to find any case in which ESC fails to properly return focus to navigation mode.
This is resolved for me in: Second Life 1.19.0 (80044) Feb 15 2008 16:46:46 (Second Life WindLight) This is appearing again in RC12 worse than ever ESC has no effect anywhere. I have relied on this a lot to take focus away from UI elements and restore control to the camera... it's so bad now, if I am sitting I cannot get my camera to return to default position. PLEASE FIX!!!
ESC key is working for me in RC12.
blah. the way this knowledge base is setup sucks. anyway heres my setup
windows vista, premium home edition. Version 6.0.6001 Service Pack 1 Build 6001 - Processor Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz, 2394 Mhz, 4 Core(s), 4 Logical Processor(s)- Installed Physical Memory (RAM) 4.00 GB - video Adapter Description ATI Radeon HD 3450 - Driver c:\windows\system32\drivers\atikmdag.sys (7.1.1.798, 4.39 MB (4,598,784 bytes), 12/18/2008 4:39 PM) after a couple days of being totally annoyed i thought well if the escape key works then stops working might have something to do with my video driver. I updated to the latest ati drivers and problem no more. The driver it had before was the factory installed dell ati drivers. Hope this can help someone in some way. regards |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Reopened
Normal
Pressing escape key when focused on local chat or other windows does not remove focus
I don't know how often I reported this bug to see it fixed and then return again 
How did this break?