This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
On OSX most apps (Finder, iCal, Preview) show some information about the selected file/document with command + I. It's quite non-intuitive that NetBeans shows files in various windows (Projects, Files) but you cannot use Command + I to open the properties window, you usually have to open that popup and scroll all the way down. Not a bug perse but it kinda breaks the flow when working with OSX as you are reminded again this is not a native app.
there's ctrl+shift+7 shortcut which opens the global properties window, there's no need for popup menu cc'ing our hie experts anyway
Ctrl+I is taken by IDE quicksearch, which seems to be rather frequently used. Yes, NB is not a native app. We do our best for it to appear so, but in some aspects (shortcuts is one of them), the possibilities are limited. On one side, there's apple and other shortcut guidelines. On the other side there are limited resources for creating and maintaining multiple shortcut profiles, plus steep learning curve for people who switch the OSes, yet stay with NetBeans. Suggesting wontfix, i'm sorry.
Well, this brings up another shortcut that's non-standard. On Safari, google search (which would be the equivalent of quicksearch) works via Command + Option/Alt + F. This also seems to work in Firefox on OSX although Firefox also has Command + K for this. So, on OSX if we link QuickSearch to Command + Option + F, we have Command + I available for the properties window. I assume the logic of having a single keymap for NetBeans depends if we assume people generally "learn NetBeans" compared to "learn the OS". I would say that unless normal developers switch machines and operating systems a lot, they need to use other tools on the given OS such as email client, web browser, some file navigator, etc. What I have found is that you learn these OS shortcuts in time as a natural thing through plain repetition. And at this point, NetBeans becomes non-standard since you notice that the shortcut doesn't do what it was supposed to do. It feels like using a broken mouse. You click -- and nothing happens. Then you click again. Only to realize the application doesn't allow clicks in that region. I see it as a big "flow"-destroyer and against the "don't make me think" mantra applications should apply. I understand the lack of resources though and no application is perfect but sometimes these little things matter.
i'd say that 'quick search' would be used more frequently than opening properties window (which stays opened afterwards) but i'll leave it up to the HIE team to decide
Emi, agree with almost everything you wrote, including the little things which matter, breaking the flow and OS vs app priority. I'd like to have 3 totally native shortcut profiles (win, OS X, KDE) .. but currently, there's no way. We try in cases of frequently used actions such as build, etc.. but we just don't have capacity for all. Sorry.