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.
I think it would be better to have the filters in Profiling Results' views case insensitive.
I am sorry... the Java language is case-sensitive, so I don't think our filters should introduce inconsistency and confusion by being case-insensitive.
I'd disagree with Misha here. Whatever is the case sensitivity in Java language spec has lower impact on what is going to be useful. An example I'd use here is IntelliJ's "Open Class" dialog, which is class insensitive by default, even accepting "Camel words" (i.e. "TAR" would match to "TargetAppRunner" for instance). Jirka and I have been thinking about whether to make the String comparison case sensitive or insensitive, and have leaned towards case sensitivity, but we are not completely sure about that, so this type of feedback is quite useful.
Well, opening a file and dealing with Java program identifiers are somewhat different issues. Consider a case when you have both package foo.bar and class foo.Bar. If you want to just load Bar.java, you can always point the tool at the right file, if not by typing its name then by clicking on it. But a user who just wants to filter out just methods of class foo.Bar (and maybe foo.Bar1,.. etc.) will be confused and dissatisfied if they receive the whole foo.bar package in addition to that. For this reason, I think we need to have case- sensitivity as at least an option (and probably a default one).
Thanks for your opinion Misha. We'll play with the two options, possibly asking users at the usability study, and based on that will decide which is the better way to do this.
I vote for having this at least as an option. I find it quite useful in OptimizeIt.
Assigning to Jirka to resolve
I agree that for instrumentation filters case sensitivity should follow Java language approach. On the other side, I think that usage of results filters is slightly different and case insensitivity could simplify using it. I've changed results filters to be case insensitive from now and I'm closing this issue for now. We can reopen it if there will be any problems with this approach.
Verification of old issues.
Closing old issues.