Expose filter and deviceManager in StandaloneFilterwindow?


#1

Hi Jules,

in the StandaloneFilterWindow class, would it be acceptable to you to expose the filter and devicemanager members to derived classes?
This is useful when I need to access the filter/devicemanager from custom menu handlers in my own standalone window.

concretely, adding something like this would be fine:

[code]protected:

AudioProcessor* getFilter()
{
if (filter)
{
return filter.get();
}
else
{
return 0;
}
}

AudioDeviceManager* getDeviceManager()
{
if (deviceManager)
{
return deviceManager.get();
}
else
{
return 0;
}
}
[/code]

it’s a fix I can easily add myself of course, but it would be handy to have it permanently in the official juce tree


#2

…or even:

AudioProcessor* getAudioProcessor() const noexcept { return filter; } AudioDeviceManager* getDeviceManager() const noexcept { return deviceManager; }

:wink:

No problem, I’ll add that.


#3

excellent! Thanx