Content Pipeline platform dependent (texture resolution) import.

Hi,

I’m using the old approach to building content (Content builder project with references to MG content processors). I’ve implemented custom texture importer which looks for filenames with a @2x suffix (files with high resolution images) and if it finds it it replaces the original filename and feeds it to original texture importer. This way I can easily choose which resolution platform is being build. To make it a little bit more flexible I’d like to set the target resolution through some parameters (currently the @2x suffix has to be hard coded into the importer) but content importers don’t allow to expose parameters like content processors do. Is there any way to pass parameters to custom content importers besides reading a file?