That code works very nice. I think for the future when we start to
implement a bunch of different transformations (like drilling on a
member to show children and such) that we need to do this with some
sort of listener interface instead of passing an instance of Dimension
Panel to the Report Panel. Obviously that will work (and does so
nicely now). But if we have other widgets that rely on actions in the
report pane then it would be nice to just register them as listeners
to the report pane and have messages sent when that pane changes.
As for your tasking you could try to implement the Report Panel
listeners for this item or you can continue to work on MDX->Query
model. Let me know what you'd prefer.
Bill