Prev: discrete trasnfer function calculations discrepance
Next: Issue with Accessor methods
From: James Tursa on 21 Jun 2010 13:19
"Hu " <amber.du(a)gmail.com> wrote in message <hvnps8$r71$1(a)fred.mathworks.com>...
> Thank you again James,
> I tried the new header file, it still have the same problem. Is it because the function need return a value for ErrorFlag and I didn't define the variable in Matlab before I call the function?

How are you calling this from MATLAB? Maybe it's an error in the way you are calling it. Please provide an example. Also, you might try long instead of int. These are usually the same on a 32-bit system but maybe they are not on your system. e.g., you might try:

void PROCESSWEATHER(char *, long, char *, long, char *, long, char *, long, unsigned char *);

> Actually, there are three other functions in the DLL file.
> SetupPWInternalDataPath
> SetFixOutOfRangeData
> SetDefaultChgLimit
>
> The declaration of them are followed:
>
> VB declaration statement:
> Private Declare Sub SetupPWInternalDataPath Lib "EPlusWth" (ByVal strPath As
> String, ByVal InPathLen As Long)
>
> And a call from a VB program:
> Call SetupPWInternalDataPath(AppPath, Len(AppPath))
> --------------------------------------------------------------------------
> Likewise for Fortran 90/95:
> INTERFACE
> SUBROUTINE SetupPWInternalDataPath (Path)
> CHARACTER(len=*), INTENT(IN) :: Path ! Path where data files reside
> END SUBROUTINE
> END INTERFACE
>
> And then calling it from Fortran:
> Character(len=255) DataPath
> CALL SetupPWInternalDataPath(trim(DataPath))
> *************************************************
> VB Declaration statement:
> Private Declare Sub SetFixOutOfRangeData Lib "EPlusWth" (ByVal strValue As
> String, ByVal strValueLen As Long)
>
> And calling it from VB:
> Global FixOutOfRangeData As String
> FixOutOfRangeData = &#8220;Yes&#8221;
> Call SetFixOutOfRangeData(FixOutOfRangeData, Len(FixOutOfRangeData))
> ------------------------------------------------------------------------------------
> For Fortran 90/95:
> INTERFACE
> SUBROUTINE SetFixOutOfRangeData (YesNo)
> CHARACTER(len=*),INTENT(IN) :: YesNo ! &#8216;yes&#8217; to set fixing option;
> ! &#8216;no&#8217; to not
> END SUBROUTINE
> END INTERFACE
>
> And then calling it:
> CALL SetFixOutOfRangeData(&#8216;no&#8217;)
> *********************************************************
> VB Declaration Statement:
> Private Declare Sub SetDefaultChgLimit Lib "EPlusWth" (ByVal strValue As
> String, ByVal strValueLen As Long, ByVal strValue As String, ByVal
> strValueLen As Long)
>
> And a call from VB:
> Call SetDefaultChgLimit(TriggerLimit, Len(TriggerLimit),
> IgnoreCalcTrigger, Len(IgnoreCalcTrigger))
> *****************************************************
>
> The information in header file I used are:
> void SetupPWInternalDataPath (char *,int);
> void SetFixOutOfRangeData(char *,int);
> void SetDefaultChgLimit(char *,int,char *,int);
>
> Are they right?

Looks reasonable to me, although you may need to use all uppercase for your function names. You might also try long instead of int per my comment above. Quite frankly, however, I have no idea what passing a string ByVal could possibly mean in VB ... I can't imagine actually passing the string itself on the stack to the function as the usage seems to imply. This has me confused, and doesn't match what I think should be happening.

> Do I need call these functions firstly then call ProcessWeather?

I have no idea. You will have to consult the doc associated with the DLL to get this information.

James Tursa
First  |  Prev  | 
Pages: 1 2
Prev: discrete trasnfer function calculations discrepance
Next: Issue with Accessor methods