Author Topic: QueryInterface problem in visualization  (Read 112 times)


  • Posts: 2
QueryInterface problem in visualization
« on: 10 Mar '18 - 00:31 »
I'm writing my own visualization plugin and I'm having some trouble getting the QueryInterface to work. It's not very well documented but I've looked at some other plugins code and I think I'm using it correctly. I'm using mingw and have a feeling that there may be some difference in the way g++ and visual c++ implements virtual function tables. If that's the case, I guess that's the problem, and I wonder how I would work around this issue. If not, well what else am I missing?

Ian @ un4seen

  • Administrator
  • Posts: 20670
Re: QueryInterface problem in visualization
« Reply #1 on: 12 Mar '18 - 14:20 »
Please give a bit more info on the problem that you're having. I guess you are implementing a ReceiveQueryInterface function in your plugin, to receive an instance of the VisQueryInterface class? If so, is that getting called when your vis is activated? If so, are you having problems with the class's QueryInt/String functions, and if so, what parameters are you using in those calls? The strings currently supported by XMPlay are: currentsongfilename, currengsongdisplaystring, currentsongtitle, currentsongauthor.


  • Posts: 2
Re: QueryInterface problem in visualization
« Reply #2 on: 16 Mar '18 - 21:45 »
Oh, I see. I assumed all of the QueryInterface was supported and of course I only tried the unsupported strings. ^^
(which was really stupid since the one I actually needed was currentsongfilename)
Anyway, this turned out to be easier than I first thought. Thanks!

While I'm here I might as well ask if there is a way to use xmplays png loader (maybe there is a jpeg one as well?) in my visualization rather than bloating it by including my own one.