Module Settings window pops up when I click on a Project/<module>... WHY?

Am I the only one who's annoyed by this new "feature"? Every time I right- or left-click on a module in the Project pane, the Settings window pops up for this module, and, sure as hell, I don't care to see it. What was wrong with the good old context menu in response to a right-click? I often use the "Compile" option from that menu to compile all Java classes in the module. Now, I need to expand the tree and separately compile the sources, and then the test classes.

Actually, at first I thought that my modules got messed up when I upgraded to the latest EAP version and, perhaps, the IDEA was trying to tell me something by redirecting me to the setup window. IMHO, this is not an improvement.

Also, who decided to replace the tabs in the settings window with the tree view? How is this better? Is there a new manager in the User Experience group at JetBrains? Bring the old guy back! :)

8 comments

I should point out that I am working with a multi-module project. To play a devil's advocate, I will be willing to assume that the new behavior may be less intrusive if the project contains only a single module. Perhaps, the JetBrains' UI designers have reasoned that the user will rarely click on the module's root node, unless they need to modify the module's settings. Well, this "feature" really gets in a way and drives me nuts. Even if some users like it, shouldn't there be a way to disable it?

Also, I am also not convinced that the new way of setting up libraries (the Classpath tab) is +clearer + then the old Libraries tab. I agree that it makes sense to refer to "classpath" in the tab that configures the libs, and this tab seems to fuse the old Libraries and Dependencies together. However the new tab's functionality seems to be unfinished. For example, if I select an existing module name in the classpath list (a module that the given module depends on), the Edit button is enabled, but when I click on it, nothing happens. It seems I can only edit the actual "libraries", i.e. the lists of jars/classes.

0

Maybe you're the only one has these experience. IDEA works fine for me in the "old" way. ;)

0

Hello no_reply@jetbrains.com,

Are you on OS X (or probably Linux). If so please note popup menus appear
at mouse pressed, not mouse release (that's how it works for Windows). That
way if you press and release mouse quickly first menu item may fire unexpectedly.

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

No, I am on Windows XP, actually. This behavior is very consistent. The Setting windows opens on a single click - always. That's very strange. I've seen situatiuons before, when, for example, you download a plug-in that conflicts with an existing short cut, and the shortcut gets disabled. But this is clearly a different story here. I haven't copied any of my old plugins into the new installation folder yet. Yesterday, I saw something even more strange (I can't recreate it today though.) The Settings window would pop up by itself as soon as I closed it.

0

Maxim,
Also, I have noticed that when I right-click on the module name, for a split of a second there, I see a grey rectangle where the context menue should appear. But then it disappears immediately, and the Settings window pops up. You may be right suggesting that something instantly triggers the first item on the menu. Could it be that IDEA misinterprets the mouse event somehow? I am using a regular PS/2 compatible mouse attached to a laptop. IDEA 5.1 works just fine, and I have never seen any faulty behavior in any other apps.

0

OK, here's the sequence:

1. Click on a module name in the Projects pane (single click, right or left.) The Settings window opens immediately.

2. Uncheck the entries in the classpath window.

3. Click OK to close the window. The window closes and opens up immediately - by itself. This keeps happening each time OK is pressed.

4. Re-store the checks for the dependency entries in the classpath. Click OK. The window closes and opens again by itself. After repeating this procedure a couple of times - without modifying the class path - finally, the window closes and does not re-open... unless you click on the module name.

Definitely, looks like a bug. A subtle one - since, apparently, it doesn't happen to everyone.

Thanks,
C

0

Have you any actions mapped to the mouse left button click ?
Could you please send me your keymap configs (IDEACONFIG/keymaps/*.xml) ?
--
regards,
--
Alexey Kudravtsev
Software Developer
JetBrains, Inc, http://www.jetbrains.com
"Develop with pleasure!"

"Const@ntine" <no_reply@jetbrains.com> wrote in message
news:7897803.1143822109153.JavaMail.itn@is.intellij.net...

OK, here's the sequence:

>

1. Click on a module name in the Projects pane (single click, right or
left.) The Settings window opens immediately.

>

2. Uncheck the entries in the classpath window.

>

3. Click OK to close the window. The window closes and opens up
immediately - by itself. This keeps happening each time OK is pressed.

>

4. Re-store the checks for the dependency entries in the classpath. Click
OK. The window closes and opens again by itself. After repeating
this procedure a couple of times - without modifying the class path -
finally, the window closes and does not re-open... unless you click on the
module name.

>

Definitely, looks like a bug. A subtle one - since, apparently, it doesn't
happen to everyone.

>

Thanks,
C



0

Alexey,

I don't have any specific key mappings. In fact my ".IntelliJIdea60\config\keymaps" folder is empty.

A couple of additional details:

1. The settings window opens always with the focus in the Classpath tab.
2. After a change is made in the classpath tab (entries checked or unchecked) and OK is clicked, the Settings window opens on its own exactly 2 more times. (OK, reopens, OK, reopens, OK, stays closed until you click on the module name again.)

Please note that it doesn't matter which mouse button I click - right or left. As I have mentioned, the right click does seem to trigger the context menu that closes before it is painted, and then the Settings window appears.

Thanks,
Constantine

0

Please sign in to leave a comment.