Sebastien Metrot :

I never had this problem. I googled a bit about this problem and it seems that people having this problem are using libraries compiled with older versions of visual studio (v6.x?) that uses the STL. I'm unsure how this can be fixed. They seem to say that pasting that in your own code fixes the problem:
_STD_BEGIN
       // report a length_error
       __declspec(dllexport) *void* __cdecl _Xlen()
       {_THROW(length_error, "string too long"); }
       // report an out_of_range error
       __declspec(dllexport) *void* __cdecl _Xran()
       {_THROW(out_of_range, "invalid string position"); }
       _STD_END

(check out http://groups.google.fr/group/microsoft.public.vc.stl/browse_thread/thread/c8ff6d50023fa1/7dc7801133c7e60c?q=void+__thiscall+std::_String_base::_Xran(void)const&rnum=5&hl=en#7dc7801133c7e60c)


This is really weird, because I'm either building nui/ngl+example
apps with platformSDK libs or .NET libs. When I use the latter there's
no problem with debug/release builds. I also tried to build nui/ngl
with .NET libs and examples with platformSDK libs - the same error
appears as if I'd used only platformSDK :-/ That would suggest, that
debug version of platformSDK libs (specificly libcmtd.lib) was built
with vc6. Crap! I think I'm using the newest platformSDK, but I'm not
sure. I'm going to download the latest version from msdn just to be
sure. If that won't help I'll try the code you've posted.

2. What should I do to avoid that font bug in vst-plugin that I
mentioned few days ago (when reopening editor, instead of normal fonts
some black rectangles appear)?


Ok, here is the init/uninint code we use in our own audio plugin framework:

Wow. Thanks for that! I'll try it later this day.

I'll have to adapt that code to the VSTPlugin example one of these days. It should be really easy, probably just some copy and paste in the right places...

Well, if I get it to work, I can merge those changes into example
vst-plugin :-)

Ok, I think the error should go away if you do this:
FEVWindow::FEVWindow(const nglContextInfo& rContextInfo,
   const nglWindowInfo& rInfo, const nglContext* pShared,
   const nglPath& rResPath) :
   nuiMainWindow(rContextInfo, rInfo, NULL, rResPath)
{    }

If it doesn't go away with that fix I'll need you to tell me where exactely the crash occurs (and may be part of the call stack).


Yeah. I did that in the first place. I actually looked at nuiTest
as a reference, but I get the same thing. Anyway, as soon as I'll get
debug going on, I'll post more informations.

Thanks in advance for any help, and once again sorry if I'm
being obtrusive.

Not at all! I hope you'll soon enjoy working on things more constructive than trying to find fixes for stupid bugs and compiler problems :).

Yeah. I hope so, and looking forward to it :-)
Once again thanks for your help & patience ;-)

cheers,
Bart
--
"When the only tool you know is a hammer,
every problem looks like a nail."


Reply via email to