I share your priorities, believe me. Here's the actual case that motivated my post: I was looking at a rather large class written by another developer. I felt it would be helpful to refactor it because it contained some 40 or so methods. I wanted to bring a summary of the class to a code review to make my point. As a matter of fact, I did use PrintScreen, but even then there were more methods than could fit on the screen at once!
"Leif Jantzen" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > [EMAIL PROTECTED] (Kenji Andrew Matsuoka) wrote in > <afvcbp$nes$[EMAIL PROTECTED]>: > > > >I love the structure pane. It's a great way to get a quick glimpse of a > >Java class. It would be even nicer if I could save/copy/print this view > >of the class! > > > >Kenji Matsuoka > > > -10 > > Use PrintScreen or somesuch. I'd prefer the folks at IntelliJ to focus on > tasks that make coding simpler and faster. > > -lj _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
