调用VC++生成的.DLL文件 ug调用后提示“缺少需要的库内存功能ufusr”

dingweigang · 发表于 2013-11-28 17:27

刚刚进行vc++与ug nx 7.0二次开发在编对话框访问时生成dll 但是使用nx open后调用dll 然后出现“缺少需要的库内存功能ufusr”
亟待解决啊
附代码：
/* These include files are needed for the following template code.          */
#include <stdio.h>
#include <uf.h>
#include <uf_defs.h>
#include <uf_exit.h>
#include <uf_ui.h>
#include <uf_styler.h>
#include <uf_mb.h>
#include "access_dialog.h"

/* The following definition defines the number of callback entries */
/* in the callback structure:                                     */
/* UF_STYLER_callback_info_t DIALOG_ACCESS_cbs */
#define DIALOG_ACCESS_CB_COUNT ( 2 + 1 ) /* Add 1 for the terminator */

/*--------------------------------------------------------------------------
The following structure defines the callback entries used by the
styler file.  This structure MUST be passed into the user function,
UF_STYLER_create_dialog along with DIALOG_ACCESS_CB_COUNT.
--------------------------------------------------------------------------*/
static UF_STYLER_callback_info_t DIALOG_ACCESS_cbs[DIALOG_ACCESS_CB_COUNT] =
{
{UF_STYLER_DIALOG_INDEX, UF_STYLER_BACK_CB       , 0, DIALOG_ACCESS_back_cb},
{DIALOG_ACCESS_BUTTON  , UF_STYLER_ACTIVATE_CB    , 0, DIALOG_ACCESS_button_cb},
{UF_STYLER_NULL_OBJECT, UF_STYLER_NO_CB, 0, 0 }
};

/*--------------------------------------------------------------------------
UF_MB_styler_actions_t contains 4 fields.  These are defined as follows:

Field 1 : the name of your dialog that you wish to display.
Field 2 : any client data you wish to pass to your callbacks.
Field 3 : your callback structure.
Field 4 : flag to inform menubar of your dialog location.  This flag MUST
      match the resource set in your dialog!  Do NOT ASSUME that changing
      this field will update the location of your dialog.  Please use the
      UIStyler to indicate the position of your dialog.
--------------------------------------------------------------------------*/
static UF_MB_styler_actions_t actions[] = {
{ "access_dialog.dlg",  NULL, DIALOG_ACCESS_cbs,  UF_MB_STYLER_IS_NOT_TOP },
{ NULL,  NULL,  NULL,  0 } /* This is a NULL terminated list */
};

/*---------------- MENUBAR HOOKUP HELP Example -------------------
To launch this dialog from a Unigraphics menubar, you must follow
the steps below.
1)  Add the following lines to your MenuScript file in order to
associate a menu bar button with your dialog.  In this
example, a cascade menu will be created and will be
located just before the Help button on the main menubar.
The button, ACCESS_DIALOG_BTN is set up to launch your dialog and
will be positioned as the first button on your pulldown menu.
If you wish to add the button to an existing cascade, simply
add the 3 lines between MENU LAUNCH_CASCADE and END_OF_MENU
to your menuscript file.

The MenuScript file requires an extension of ".men".
Make sure that you add the extension to the file and place
the file in your startup directory:
   $UGII_USER_DIR/startup or
   $UGII_SITE_DIR/startup or
   $UGII_VENDOR_DIR/startup directory

Move the contents between the dashed lines to your Menuscript file.
! ----------------------------------------------------------------
VERSION NX7

EDIT UG_GATEWAY_MAIN_MENUBAR

BEFORE UG_HELP
   CASCADE_BUTTON UISTYLER_DLG_CASCADE_BTN
   LABEL Dialog Launcher
END_OF_BEFORE

MENU UISTYLER_DLG_CASCADE_BTN
   BUTTON ACCESS_DIALOG_BTN
   LABEL Display access_dialog dialog
   ACTIONS access_dialog.dlg
END_OF_MENU
! ---------------------------------------------------------------

2) Issue a call to the function, UF_MB_add_styler_actions from the ufsta
user exit as shown below.  To use this call, remove the conditional
definitions:  #ifdef MENUBAR_COMMENTED_OUT
               #endif MENUBAR_COMMENTED_OUT

The static structure, actions, will allow you to associate ALL of your
dialogs and callback functions to the  menubar at once.  For example, if you
wish to have 10 dialogs associated to 10 different buttons on the menubar,
you may enter each dialog and callback list into the actions structure. Make
sure that you have created a corresponding button in your MenuScript file.

You may also have separate shared libraries, each with a ufsta user exit
for each individual dialog.

3) Place your compiled and linked ufsta user function in
$UGII_USER_DIR/startup or
$UGII_SITE_DIR/startup or
$UGII_VENDOR_DIR/startup directory.

NOTE:  The user function must contain the proper extension .so, .sl or .dll
to make ensure that it is recognized by the MenuScript.  If it does not
have the proper extension, it will NOT be recognized by MenuScript.

The action name you have provided in your MenuScript must correspond to
to the dialog name provided in the action structure.  This MUST match inorder
to bind your dlg file to your MenuScript button.

4) Copy your UIStyler dialog file to the proper directory.
All dialog files (.dlg) must be located in
   $UGII_USER_DIR/application or
   $UGII_SITE_DIR/application or
   $UGII_VENDOR_DIR/application directory

------------------------------------------------------------*/
#ifdef MENUBAR_COMMENTED_OUT
extern void ufsta (char *param, int *retcode, int rlen)
{
int  error_code;

if ( (UF_initialize()) != 0)
      return;

if ( (error_code = UF_MB_add_styler_actions ( actions ) ) != 0 )
{
      char fail_message[133];

      UF_get_fail_message(error_code, fail_message);
      printf ( "%s\n", fail_message );
}

UF_terminate();
return;
}
#endif/*MENUBAR_COMMENTED_OUT*/

/*-------DIALOG CREATION FROM A CALLBACK HELP Example ----------
If you wish to have this dialog displayed from the callback of
another UIStyler dialog, you should:

1) Make sure that the callback of your UIStyler dialog is
designated as a dialog building callback.
2) Remove the conditional definitions:
#ifdef DISPLAY_FROM_CALLBACK
#endif DISPLAY_FROM_CALLBACK
3) Your callback should issue a call to this function.
4) You should also add the funcitonal prototype to your header file
(access_dialog.h) and ensure that the file is properly included.

All dialog files must be located in
   $UGII_USER_DIR/application or
   $UGII_SITE_DIR/application or
   $UGII_VENDOR_DIR/application directory
--------------------------------------------------------------*/

#ifdef DISPLAY_FROM_CALLBACK
extern int <enter the name of your function> ( int *response )
{
int  error_code = 0;

if ( ( error_code = UF_initialize() ) != 0 )
         return (0) ;

if ( ( error_code = UF_STYLER_create_dialog ( "access_dialog.dlg",
         DIALOG_ACCESS_cbs,    /* Callbacks from dialog */
         DIALOG_ACCESS_CB_COUNT, /* number of callbacks*/
         NULL,       /* This is your client data */
         response ) ) != 0 )
{
      char fail_message[133];

      /* Get the user function fail message based on the fail code.*/
      UF_get_fail_message(error_code, fail_message);
      UF_UI_set_status (fail_message);
      printf ( "%s\n", fail_message );
}

UF_terminate();
return (error_code);
}
#endif /* DISPLAY_FROM_CALLBACK */

/*-------DIALOG CREATION FROM A USER EXIT HELP Example --------
To create this dialog from a user exit, you must invoke a
call to the NX Open API, UF_STYLER_create_dialog.  An example
is shown below.

All dialog files must be located in
   $UGII_USER_DIR/application or
   $UGII_SITE_DIR/application or
   $UGII_VENDOR_DIR/application directory

1) Remove the conditional definitions:
#ifdef DISPLAY_FROM_USER_EXIT
#endif DISPLAY_FROM_USER_EXIT
2) Add a user exit to the function name below, for example, ufusr.
3) Consider how your shared library will be unloaded.  Take a look
at the generated function ufusr_ask_unload.
--------------------------------------------------------------*/

#ifdef DISPLAY_FROM_USER_EXIT
extern void ufusr (char *param, int *retcode, int rlen)
{
int  response = 0;
int  error_code = 0;

if ( ( UF_initialize() ) != 0 )
         return;

if ( ( error_code = UF_STYLER_create_dialog ( "access_dialog.dlg",
         DIALOG_ACCESS_cbs,    /* Callbacks from dialog */
         DIALOG_ACCESS_CB_COUNT, /* number of callbacks*/
         NULL,       /* This is your client data */
         &response ) ) != 0 )
{
      char fail_message[133];

      /* Get the user function fail message based on the fail code.*/
      UF_get_fail_message(error_code, fail_message);
      UF_UI_set_status (fail_message);
      printf ( "%s\n", fail_message );
}

UF_terminate();
return;
}

/*--------------------------------------------------------------------------
This function specifies how a shared image is unloaded from memory
within Unigraphics. This function gives you the capability to unload an
internal NX Open application or user  exit from Unigraphics.  You can
specify any one of the three constants as a return value to determine
the type of unload to perform:  immediately after user function
execution, via an unload selection dialog, or when Unigraphics terminates
terminates.  If you choose UF_UNLOAD_SEL_DIALOG, then you have the
option to unload your image by selecting  File->Utilities->Unload Shared
Image.

NOTE:  A program which associates NX Open applications with the menubar
MUST NOT use this option since it will UNLOAD your NX Open application image
--------
from the menubar.
--------------------------------------------------------------------------*/

extern int ufusr_ask_unload (void)
{
   /* unload immediately after application exits*/
   return ( UF_UNLOAD_IMMEDIATELY );

   /*via the unload selection dialog... */
   /*return ( UF_UNLOAD_SEL_DIALOG ); */
   /*when UG terminates...             */
   /*return ( UF_UNLOAD_UG_TERMINATE ); */
}

/*--------------------------------------------------------------------------
You have the option of coding the cleanup routine to perform any housekeeping
chores that may need to be performed.  If you code the cleanup routine, it is
automatically called by Unigraphics.
--------------------------------------------------------------------------*/
extern void ufusr_cleanup (void)
{
return;
}
//#endif /* DISPLAY_FROM_USER_EXIT */

/*-------------------------------------------------------------------------*/
/*---------------------- UIStyler Callback Functions ----------------------*/
/*-------------------------------------------------------------------------*/

/* -------------------------------------------------------------------------
* Callback Name: DIALOG_ACCESS_back_cb
* This is a callback function associated with an action taken from a
* UIStyler object.
*
* Input: dialog_id - The dialog id indicate which dialog this callback
*                      is associated with.  The dialog id is a dynamic,
*                      unique id and should not be stored.  It is
*                      strictly for the use in the NX Open API:
*                            UF_STYLER_ask_value(s)
*                            UF_STYLER_set_value
*       client_data - Client data is user defined data associated
*                      with your dialog.  Client data may be bound
*                      to your dialog with UF_MB_add_styler_actions
*                      or UF_STYLER_create_dialog.
*       callback_data - This structure pointer contains information
*                      specific to the UIStyler Object type that
*                      invoked this callback and the callback type.
* -----------------------------------------------------------------------*/
int DIALOG_ACCESS_back_cb ( int dialog_id,
         void * client_data,
         UF_STYLER_item_value_type_p_t callback_data)
{
   /* Make sure User Function is available. */
   if ( UF_initialize() != 0)
      return ( UF_UI_CB_CONTINUE_DIALOG );

   /* ---- Enter your callback code here ----- */
   uc1601("您将退出对话框!",1);
   UF_terminate ();

/* Callback acknowledged, terminate dialog.          */
/* It is STRONGLY recommended that you exit your    */
/* callback with UF_UI_CB_EXIT_DIALOG in a back call */
/* back rather than UF_UI_CB_CONTINUE_DIALOG.       */
return (UF_UI_CB_EXIT_DIALOG);

}

/* -------------------------------------------------------------------------
* Callback Name: DIALOG_ACCESS_button_cb
* This is a callback function associated with an action taken from a
* UIStyler object.
*
* Input: dialog_id - The dialog id indicate which dialog this callback
*                      is associated with.  The dialog id is a dynamic,
*                      unique id and should not be stored.  It is
*                      strictly for the use in the NX Open API:
*                            UF_STYLER_ask_value(s)
*                            UF_STYLER_set_value
*       client_data - Client data is user defined data associated
*                      with your dialog.  Client data may be bound
*                      to your dialog with UF_MB_add_styler_actions
*                      or UF_STYLER_create_dialog.
*       callback_data - This structure pointer contains information
*                      specific to the UIStyler Object type that
*                      invoked this callback and the callback type.
* -----------------------------------------------------------------------*/
int DIALOG_ACCESS_button_cb ( int dialog_id,
         void * client_data,
         UF_STYLER_item_value_type_p_t callback_data)
{
   /* Make sure User Function is available. */
   if ( UF_initialize() != 0)
      return ( UF_UI_CB_CONTINUE_DIALOG );

   /* ---- Enter your callback code here ----- */
   UF_STYLER_item_value_type_t data[3];
   char info[100];

   data[0].item_attr=UF_STYLER_VALUE;
   data[0].item_id=DIALOG_ACCESS_INTEGER;
   UF_STYLER_ask_value(dialog_id,&data[0]);

   data[1].item_attr=UF_STYLER_VALUE;
   data[1].item_id=DIALOG_ACCESS_REAL;
   UF_STYLER_ask_value(dialog_id,&data[1]);

   data[2].item_attr=UF_STYLER_VALUE;
   data[2].item_id=DIALOG_ACCESS_STRING;
   UF_STYLER_ask_value(dialog_id,&data[2]);

   sprintf(info,"整数为:%d\n实数为:%f\n字符串为:%s\n",data[0].value.integer,data[1].value.real,data[2].value.string);

   uc1601(info,1);

   UF_terminate ();

/* Callback acknowledged, do not terminate dialog */
return (UF_UI_CB_CONTINUE_DIALOG);

/* or Callback acknowledged, terminate dialog. */
/* return ( UF_UI_CB_EXIT_DIALOG );             */
}

dingweigang · 发表于 2013-11-30 13:45

木有人啊。。。求指导啊

shaoye12312 · 发表于 2013-12-5 14:38

我觉得楼主狠牛B 我一个看不懂啊！

dingweigang · 发表于 2013-12-5 16:10

#ifdef MENUBAR_COMMENTED_OUT
#endif/*MENUBAR_COMMENTED_OUT*/

找到原因了没屏蔽这两句呵呵我也是新手。

		自动登录	找回密码
密码			注册

[疑难] 调用VC++生成的.DLL文件 ug调用后提示“缺少需要的库内存功能ufusr”

浏览过的版块

[疑难] 调用VC++生成的.DLL文件 ug调用后提示“缺少需要的库内存 功能ufusr”

浏览过的版块

[疑难] 调用VC++生成的.DLL文件 ug调用后提示“缺少需要的库内存功能ufusr”