Eh? The same way you’d set a breakpoint or search in any other source files (?)[/quote]
I set a break point by expanding groups in the project file containing the JUCE sources, locating the desired file, double clicking to open it, placing the cursor on the line of interest and then choosing the Set Breakpoint option. Of course, this requires that the JUCE sources are actually in a project in the current solution (Visual Studio).
With the modules, you don’t add all the JUCE sources. You add something like juce_gui_basics.cpp instead. But what if I want to set a breakpoint in juce_Component.cpp? The only thing I can figure is that I have to have an explorer window up somewhere, switch to it, and use it to open the file. Which truly sucks. Or maybe I’m missing something? Please, if you know a better way, I would love to hear it.
Now when I do a Find in Files I usually choose “Current Project” or “Entire Solution”. This instructs the IDE to look in all files that are known in the current project, or all projects in the solution. Again, we have the same problem. If I’m looking for all calls in the JUCE source code to setVisible, and I only have the module .cpp files (juce_core.cpp, juce_audio_basics.cpp, etc…) then Find in Files wil not locate it.
Besides breakpoints, there is also the problem of browsing the JUCE sources in general. It is very often the case that I want to see which classes are available, open up a header file corresponding to a class, and just browse the interface. How do you do that with just the library code files (juce_core.cpp, etc…) ?
I brought these issues up a while back, and your consensus was that the static library project had to stay. Now you’re suggesting, to take it away? How will these issues get resolved?