BatVink,
I really wish it were possible, but what are the chances of releases a major bugfix between now and the convention? I have discovered a major bug in DBPro that was around for ages now. I'm afraid to do my work around for it, because TGC could fix it and it'll render most of my plugins useless.
Take for example this function:
AUDIOEXPORT DWORD GetTagKey(DWORD index, DWORD keyidx)
{
SampleSource* source = OpenSampleSource(StreamInfo[index].file_name, FF_AUTODETECT);
return (DWORD)source->getTagKey(keyidx);
}code]
Its input is a simple 2 integers from DBPro. Now the major bug I've encountered for all my plugins was that DBPro screws up the stack pushes before it calls the plugin function by adding an extra push (I noticed this happens when you have a function that returns a string). The result is something that looks like this:
00360146 B8 00000000 MOV EAX,0
0036014B 50 PUSH EAX
0036014C B8 01000000 MOV EAX,1
00360151 50 PUSH EAX
00360152 A1 946E0F00 MOV EAX,DWORD PTR DS
F6E94]
00360157 50 PUSH EAX
00360158 BB 9010AB01 MOV EBX,eap155.?GetTagKey@@YAKKK@Z
0036015D FFD3 CALL EBX
The PUSH assembly instructions you see here are where DBPro pushes the input values onto the stack. The last PUSH instruction references a string value that was previously used, and isn't necessary and shouldn't be pushed at all!
So maybe I'll just do the work around and create my padded input variable.
[edit]
I used my dbpro bug work around, and have successfully displayed metatags. The updated plugin, and more updates soon. Stay tuned!
