JOSM shortcuts lose focus

[steve@…]

One or more of the tool panels on the right makes ctrl-up, ctrl-down... ctrl-, etc lose focus. If I just load in a GPX then its ok but then I enabled some tool panels and downloaded data and I can't move around anymore.

If I could ctrl-drag or something to move (on a macintosh) that would be really really helpful :-)

This is using latest subversion.

[imi]

All of them works for me.

Can you please describe the exact steps until Ctrl-cursor keys don't work anymore?

As for the Ctrl-movement: I will probably make the "move screen" configurable once shortkeys are configurable.

[Michael]

I have this problem too using JOSM on Linux in wmii (​http://www.suckless.org). It is very annoying: If I stay in one mode (adding new ways), switching to selection mode by pressing 's' works. However, as soon as I start adding tags (by using alt+A or by clicking on Add), the shortcuts such as 'a' or 's' do not work anymore. Also, alt+a doesn't work from then on.

I have (probably) the same problem using the surveyor plugin: If I switch active window using Mod+J/Mod+K in wmii from surveyor to JOSM and back, surveyor does _not_ have focus. It just gets focus as soon as I click on a button. Shortcuts don't works.

Just to be sure: I think the problem is not wmii as JOSM is the only application I've ever seen with this focus problems. All other programs such as Firefox, Opera, urxvt, GIMP, inkscape work without any problems.

If this is a duplicate please point a link to the original ticket. This is a serious issue for usability in my opinion.

[Michael]

Just want to add that this also happens on my workstation using enlightenment (e17).

[anonymous]

Another easy reproducable case:
CTRL+A is select all. As soon as you select an error in validator dialog it CTRL+A will select all in this dialog and no longer in the map, even if you go back into the map and click there.

[Michael]

Why did you change priority and component? Are you sure about gui vs. JOSM core?

And for the priority, I clearly want it to be major. This is a huge impact in working with JOSM which should be fixed ASAP.

To be a bit more productive: Which Java-Version do you recommend to use JOSM with?

[stoecker]

A major issue is something which makes working hard or impossible. This bug is neither of these two that's why minor. An yes it's "JOSM core".

[Michael]

OK, so then it's JOSM core.

This bug definitely makes working hard to impossible (on the long term). Please provide at least some information on how to debug/workaround this. It's really a K.O. argument for JOSM on linux. Given that I won't use anything but linux, it's quite a K.O. argument for JOSM itself.

[Henry Loenwind]

while testing the new keyboard handling code I found that it is operation system dependent which keys will be sent to the global shortcut handler, which ones will never be seen by it and which ones bypass it completely and are dispatched to some individual component.

This is not a bug in JOSM. It may be a bug in the Java Runtime Environment or even in the operating system.

I'd advise you to reconfigure the shortcuts to use keys that are handed to the shortcut handler on your platform.

PS: If you want to blame JOSM, you'd better compare it with other Java programs, not with native applications.