Welcome![Sign In][Sign Up]
Location:
Search - POP H

Search list

[OpenGL programview3ds

Description: 源码3d格式转化软件view3ds下载 1,用VIEW3DS打开*.3ds文件; 2,左键点击打开的VIEW3DS显示区上任意一点将会弹出选择菜单; 3,按下E键选择:Export OpenGL C Code,将会自动生成两个文件*.h和   *.gl; 4,将两个文件拷到你的工程(为OpenGL环境)目录下; 5,在你的工程中加入#include\"*.h\"; 6,给*.h文件中生成的显示列表赋id,Model = GL3DS_initialize_--()   "--"代表3ds文件的名称; 7,调用显示列表:glCallList(Model) 。   ok!-source 3d format conversion software download a view3ds with VIEW3DS open *. 3ds documents; 2, Click on the button to open the display area VIEW3DS arbitrary point on the menu will pop up; 3, press the button to select E : Export OpenGL C Code will automatically generate two documents *. H *. Gl; 4, the two documents will peruse your project (for OpenGL Environment) directory; 5. your works include # include "*. h"; 6 to *. H documents generated by the display lists given id, Model = GL3DS_initialize_ -- () "--" document on behalf of 3ds the name; 7, calling the display lists : glCallList (Model). Ok!
Platform: | Size: 45463 | Author: 沈淳 | Hits:

[Windows Developccombobox

Description: 自动完成的复合框的实现在AutoCompleteCombo.cpp和AutoCompleteCombo.h两个文件中,用户可以把这两个文件引入自己的工程中,删除\"工程名.clw\"文件后退出,再次进入工程系统会提示找不到\"工程名.clw\"文件,选择\"“是(Yes)\"重新创建一个,接下来在弹出的对话框里选择\"Add all\"就可以在新工程中使用CAutoCompleteCombo这个类了(注意引入头文件),我在示例对话框中创建了一个CAutoCompleteCombo类型的变量\"m_combo\",在对话框的\"nInitDialog()\"函数中添加了以下语句: // TODO: Add extra initialization here m_combo.AddString(\"America\") m_combo.AddString(\"British\") m_combo.AddString(\"China\") m_combo.AddString(\"Dalian\") m_combo.AddString(\"England\") m_combo.AddString(\"France\") 这样,用户在输入这些字符的头几个字符(不区分大小写)就可以看到自动完成的效果了.-automatic composite frame to complete the realization of the AutoCompleteCombo.cpp and AutoCompleteCombo.h two documents, the user can introduce these two documents of the project, delete the "project name. Clw documents "to withdraw, once again entered the system is not able to find" who works. Clw "document choose "" (Yes), "a re-creation of, the next in the pop-up dialog box you select" Add all "on the new projects CAutoCompleteCombo use of this category (Note the introduction of the first paper), in the example I created a dialog CAutoCompleteCombo type of a variable" m _combo "in the box" nInitDialog () "function to add the following phrase : / / TODO : Add extra initialization here m_combo.AddString (" America &quo
Platform: | Size: 28030 | Author: wang | Hits:

[GUI Developbrew window manager

Description:

 

Objective
This topic describes how to create a windowed application that will share the display with other applications.
Brew® MP windowed applications need to be written differently than traditional Brew MP applications. Traditional Brew MP applications, when running in the foreground, occupy full screen space and can modify the display at any time. In the windowing framework, multiple applications share the display at the same time and are not allowed to modify the display arbitrarily. A windowed application also needs to create one or more widgets to be used to create the windows.
A windowed application needs to:
·                  Create and initialize one or more widgets to be passed to IWindowMgr_CreateWindow().
The application can implement its own IWidget, or it can make use of an existing IWidget.
·                  Handle the EVT_APP_START_WINDOW event (and create a window).
·                  Implement handlers for visibility changes, focus changes, and extent changes. The implementation of these handlers is dependent on the details of the application.
·                  Draw in two stages:
·                                  Tell the container that drawing is necessary (ICONTAINER_Invalidate()).
·                                  Draw only when told to draw by the container (IWIDGET_Draw()).
Note: A windowed application should not call any functions that modify IDisplay directly. This includes explicit IDisplay function calls or implicit updates, such as calls to IIMAGE_Draw() or ICONTROL_Redraw(). Drawing should happen only on demand, for example, when IWIDGET_Draw() is called for the widget used to create the window. Existing Widget based applications follow these guidelines and, with minor modifications, can be ported to the windowing framework.
Event handling
A windowed application must respond to these events:
EVT_APP_START_WINDOW and EVT_APP_START
A window-based application receives EVT_APP_START_WINDOW first. If the application returns TRUE for this event, the application does not receive EVT_APP_START. If an application needs to support both the environments (window based and non-window based), it should handle both events.
When the application receives EVT_APP_START_WINDOW, it should create one or more windows.
If creation of IWindowMgr0 fails while handling EVT_APP_START_WINDOW, the application should assume that the platform does not support window-based applications. In this case, the application should return FALSE and continue the application logic in the code for EVT_APP_START.
EVT_APP_SUSPEND and EVT_APP_RESUME
After an application returns TRUE for EVT_APP_START_WINDOW, it will not receive EVT_APP_SUSPEND and EVT_APP_RESUME as non-windowed Brew MP applications do. Instead, the application must check for window status events that are sent to the widget through EVT_WDG_SETPROPERTY events. For EVT_WDG_SETPROPERTY events, wParam indicates which property was set, and dwParam specifies the value of the property. When the AEEWindowMgrExt_PROPEX_STATE property has a value of AEEWindowMgrExt_STATE_VISIBLE, the window is visible.
EVT_WDG_WINDOWSTATUS
The EVT_WDG_WINDOWSTATUS event is sent to a widget to notify it about various window related status messages. AEEWindowStatus.h contains information on the meaning of various status messages.
Sample code location

ZIP filename
Location
Run app
hellowindowapp
Brew MP Library
·                       Download and extract the ZIP file.
·                       Compile the app.
·                       Run it on the Brew MP Simulator.

Example of a windowed application
In the hellowindowapp sample, HelloWindowApp_HandleEvent handles the EVT_APP_START_WINDOW event and creates soft key and pop-up windows:
   case EVT_APP_START_WINDOW:   
      DBGPRINTF("EVT_APP_START_WINDOW");
 
      // Create the softkey and popup windows
      HelloWindowApp_CreateSoftkey(pMe);
      HelloWindowApp_CreateOrActivatePopup(pMe);
 
      // Handling this event tells Brew that we are a windowing
      // application.
      return TRUE;  
HelloWindowApp_CreateSoftkey() creates the soft key widget, sets the color text of the widget, then calls HelloWindowApp_CreateWindow() to create the window.
   WidgetWindow *pWindow = &pMe->softkeyWindow;
  
   if (pWindow->piWindowWidget != NULL) return;
   pWindow->pszDbgName = "Softkey";
   pWindow->pMe = pMe;
  
   (void) ISHELL_CreateInstance(pMe->applet.m_pIShell, AEECLSID_SoftkeyWidget,
            (void **) &pWindow->piWindowWidget);
   if (pWindow->piWindowWidget == NULL) return;
 
   {
      WidgetExtent extent = {0, HWA_SOFTKEY_HEIGHT};
      IWidget_SetExtent(pWindow->piWindowWidget, &extent);
   }
  
   (void) IWidget_SetBGColor(pWindow->piWindowWidget, MAKE_RGBA(200,200,200,255));
  
   // Now set the softkeys text
   {
      IWidget *piTextWidget = NULL;
      (void) IWidget_GetSoftkey(pWindow->piWindowWidget, PROP_SOFTKEY1, &piTextWidget);
     
      if (piTextWidget != NULL) {
         (void) IWidget_SetText(piTextWidget, L"Hover", TRUE);
      }
      RELEASEIF(piTextWidget);
 
      (void) IWidget_GetSoftkey(pWindow->piWindowWidget, PROP_SOFTKEY2, &piTextWidget);
      if (piTextWidget != NULL) {
         (void) IWidget_SetText(piTextWidget, L"Close", TRUE);
      }
      RELEASEIF(piTextWidget);
   }
 
   HelloWindowApp_CreateWindow(pMe, pWindow, AEEWindowMgrExt_CLASS_Softkey);  
HelloWindowApp_CreateWindow() creates the soft key window, as follows:
   int result;
   uint32 winId;
   AEEWindowProp propList[1];
  
   // Set custom window handler
   HANDLERDESC_Init(&pWindow->hdHandler, HelloWindowApp_WindowHandler, pWindow, NULL);
   IWIDGET_SetHandler(pWindow->piWindowWidget, &pWindow->hdHandler);
        
   propList[0].id = AEEWindowMgrExtProp_CLASS;
   propList[0].pbyLen = sizeof(winClass);
   propList[0].pby = (void *) &winClass;
     
   result = IWindowMgr_CreateWindow(pMe->piWindowMgr, (IQI*) (void *) pWindow->piWindowWidget,
      propList, ARR_SIZE(propList), &winId);
 
   if (result != SUCCESS) {
      DBGPRINTF("Window creation failed for %s: %d", pWindow->pszDbgName, result);
      HelloWindowApp_DestroyWindow(pWindow);
   } else {
      DBGPRINTF("Window %s created: id=%d", pWindow->pszDbgName, winId);
   }
HelloWindowApp_CreateOrActivatePopup() creates the widget for the pop-up window, then calls HelloWindowApp_CreateWindow() to create the pop-up window.
   pWindow->piWindowWidget = HelloWindowApp_CreateAndInitImageWidget(
                                pMe,
                                "popups.main" // Image as defined in appinfo.ini
                             );
 
   if (pWindow->piWindowWidget == NULL) return;
 
   {
      WExtent extent = {HWA_POPUP_WIDTH, HWA_POPUP_HEIGHT};
      IWIDGET_SetExtent(pWindow->piWindowWidget, &extent);
   }
 
   HelloWindowApp_CreateWindow(pMe, pWindow, AEEWindowMgrExt_CLASS_Popup);
Related information
·                  See Brew MP Widgets Technology Guide: Creating a Widgets application
·                  See Brew MP API Reference

Base version:
Brew MP 1.0
Tested version:
Brew MP 1.0
Phone tested:
No

 

Platform: | Size: 439828 | Author: bluecrest | Hits:

[Algorithmhyplas

Description: ************************************************************************ * * * * * THIS IS THE H Y P L A S 2.0 README FILE * * ----------------- * * * * HYPLAS is a finite element program for implicit small and large * * strain analisys of hyperelastic and elasto-plastic two-dimensional * * and axisymmetric solids * * * * HYPLAS v2.0 is the companion software to the textbook: * * EA de Souza Neto, D Peric & DRJ Owen. Computational Methods for * * Plasticity: Theory and Applications. Wiley, Chichester, 2008. * * (www.wiley.com/go/desouzaneto) * * * * Copyright (c) 1998-2008 EA de Souza Neto, D Peric, D.R.J. Owen * *----------------------------------------------------------------------* * File last updated: 18 October 2008 * * * * This file belongs in the directory ../HYPLAS_v2.0 * ************************************************************************ * * * I M P O R T A N T * * * * READ SECTIONS 0 TO 3 OF THIS FILE CAREFULLY BEFORE ATTEMPTING * * TO COMPILE AND RUN THE PROGRAM HYPLAS ON YOUR COMPUTER !! * * * * THE AUTHORS DO NOT GUARANTEE THAT ANY SUGGESTIONS/INSTRUCTIONS * * GIVEN IN THIS README FILE WILL WORK ON ANY PARTICULAR OPERATING * * SYSTEM. IF YOU DECIDE TO FOLLOW ANY SUGGESTIONS/INSTRUCTIONS * * GIVEN HERE YOU MUST DO SO AT YOUR OWN RISK. * * * * * * BUG REPORTS: Please send bug reports to * * * * hyplas_v2.0@live.co.uk * * * * Messages sent to the authors' personal email addresses * * will NOT be answered. * ************************************************************************ This file contains the following sections: 0. Copyright statement and disclaimer 0.(a) Copyright statement 0.(b) Disclaimer 0.(c) Conditions of use 1. Introduction 1.(a) Note on portability 2. Compiling and running HYPLAS 2.(a) Memory requirements 2.(b) Testing a newly compiled executable 3. The HYPLAS directory tree 4. Cross-referencing between the source code and the textbook 5. HYPLAS error messaging 6. Further remarks on HYPLAS ************************************************************************ 0. COPYRIGHT STATEMENT AND DISCLAIMER ================================== 0.(a) Copyright statement ------------------- You may only use this program for your own private purposes. You are not allowed, in any circumstances, to distribute this program (including its source code, executable and any other files related to it, either in their original version or any modifications introduced by you, the authors or any other party) in whole or in part, either freely or otherwise, in any medium, without the prior written consent of the copyright holders. 0.(b) Disclaimer ---------- This program (including its source code, executable and any other files related to it) is provided "as is" without warranty of any kind, either expressed or implied, including, but not limited to, any implied warranties of fitness for purpose. In particular, THIS PROGRAM IS BY NO MEANS GUARANTEED TO BE FREE FROM ERRORS. This program (or any modification incorporated to it by you, the authors or any other party) will run entirely at your risk. The results produced by this program are in no way guaranteed to be fit for any purpose. Under no circumstances will the authors/copyright holders be liable to anyone for damages, including any general, special, incidental or consequential damages arising from the use or inability to use the program (including, but not limited to, loss or corruption of data, failure of the program to operate in any particular way as well as damages arising from the use of any results produced by the program for any purpose). 0.(c) Conditions of use ----------------- You may only use this program if you fully understand and agree with the terms of the above disclaimer. You must not use this program if you do not agree with or do not understand (fully or in part) these conditions of use. 1. INTRODUCTION ============ HYPLAS is a finite element code for small and large strain analysis of hyperelastic and elasto-plastic solids. Most procedures implemented in HYPLAS are described in detail in its companion textbook: EA de Souza Neto, D Peric & DRJ Owen. Computational Methods for Plasticity: Theory and Applications. Wiley, Chichester, 2008 (www.wiley.com/go/desouzaneto). 1.(a) Note on Portability ------------------- HYPLAS has been written in standard ANSI FORTRAN 77. Currently, the only known (and deliberate) exceptions to the FORTRAN 77 ANSI standard are the instructions: INCLUDE '' used in many routines to include the HYPLAS database files (common blocks and global variables), and; CALL GETENV('HYPLASHOME',HYPLASHOME) used in subroutine "ERRPRT" (file ../HYPLAS_v2.0/src/GENERAL/errprt.f). This instruction inquires the name of the system environment variable HYPLASHOME and writes it on the character string HYPLASHOME. This instruction is NOT part of the ANSI FORTRAN 77 standard, but seems to work in most currently available FORTRAN 77 compilers. 2. COMPILING AND RUNNING H Y P L A S ================================== The HYPLAS source code is stored in directory ../HYPLAS_v2.0/src/ (../HYPLAS_v2.0/ being the current directory) and all its subdirectories. To generate an executable file, you just need to compile the FORTRAN source files: ../HYPLAS_v2.0/src/hyplas.f and ../HYPLAS_v2.0/src/*/*.f together. We recommend that the executable HYPLAS be stored in the directory ../HYPLAS_v2.0/bin to which the environment variable HYPLASHOME should be set (see below how to set a system environmental variable). WINDOWS (R) systems ------------------- On Microsoft Windows(R) systems, HYPLAS has been successfully compiled using Intel Visual Fortran Compiler(R) integrated with Microsoft Visual Studio(R). Here you only need to create a project that contains all Fortran source files mentioned above as well as the include files ..\HYPLAS_v2.0\src\*.INC On a Windows XP system, the system environment variable HYPLASHOME can be set as follows: 1. Open a File Manager 2. Right-click on the "My Computer" icon 3. Select "Properties" on the drop-down menu 4. A new window named "System Properties" will pop-up. Here select the "Advanced" tab. 5. On the "Advanced" tab, click the "Environment Variables" button. 6. A new window titled "Environment Variables" will pop-up. Here click the button "New" in the "System Variables" section of the window. 7. A new window will pop-up titled "New System Variable". Here you should fill the fields "Variable name" and "Variable Value", respectively, with HYPLASHOME and the path name (in full) of the directory ..\HYPLAS_v2.0\bin. 8. Press "OK" on the relevant pop-up windows. 9. The next time the computer is REBOOTED, this variable will be set to the correct path and HYPLAS should be able to find the error messages file ERROR.RUN if required. UNIX/LINUX systems ------------------ In a UNIX/LINUX operating system using a C-shell, for instance, the HYPLASHOME environment variable should be set with the command: setenv HYPLASHOME where here denotes the full path to the directory ../HYPLAS_v2.0/bin. To compile HYPLAS (from directory ../HYPLAS_v2.0/src) with a FORTRAN 77 compiler such as g77, you can use the command: g77 -o ../bin/hyplas hyplas.f */*.f Note that the executable file "hyplas" will be stored in the directory ../HYPLAS_2.0/bin (i.e. the directory set in the HYPLASHOME environment variable). Alternatively, you may use the Makefile provided (with suitable modifications, if needed) to create the HYPLAS executable. IMPORTANT: Before generating a HYPLAS executable, read Sections 2.(a) and 2.(b) below. 2.(a) Memory Requirements ------------------- HYPLAS memory requirements depend on the array dimensioning parameters set in files: ../HYPLAS_v2.0/src/ ELEMENTS.INC GLBDBASE.INC MATERIAL.INC MAXDIM.INC Files ELEMENTS.INC, GLBDBASE.INC and MATERIAL.INC contain parameters which are associated with the currently implemented finite elements and materials. DO NOT MODIFY THEM ! unless you are absolutely sure of what you are doing (only developers coding new elements or new material models/analysis types may need to modify them by changing the existing dimensioning parameters and/or including new parameters). The ONLY dimensioning file that can be safely modified by the average user is the file MAXDIM.INC This file contains the array dimensioning parameters related to the maximum permissible dimension of problems to be analysed by HYPLAS. These parameters include the maximum number of nodes, elements, element groups, etc. If necessary, CHANGE THESE PARAMETERS TO SUIT YOUR PROBLEM SIZE/MEMORY REQUIREMENTS before compiling HYPLAS. 2.(b) Testing a newly compiled executable ----------------------------------- After you have successfully compiled the HYPLAS source code and created an executable file, the next step is to run some tests to verify that HYPLAS is working well. To do this, proceed as follows: The directory ../HYPLAS_v2.0/book_examples/data_files contains a series of data files named .dat of benchmarked examples described in the companion textbook. The corresponding (benchmarked) result files are in the directory ../HYPLAS_v2.0/book_examples/result_files This directory contains a series of result files named .res generated with the current version of HYPLAS on a tested platform. All these files have been named such that their names start with the textbook section number where the corresponding example is described. For instance, files 14_9_2_tresca.dat and 14_9_2_tresca.res refer to a problem described in section 14.9.2 of the textbook, and so on. To check that HYPLAS is working well on your platform, after compiling HYPLAS, run the program HYPLAS for the examples of files .dat and compare the newly generated results .res with their benchmarked counterparts (of the same filename) in the result_files directory. To run an example, execute HYPLAS and use the keyboard to enter the name of the corresponding data file in full (including the extension .dat). To compare the benchmarked .res files against their newly generated you may proceed as follows: 1. On MICROSOFT WINDOWS systems - Here we have successfully used the software "ExamDiff" (the task was made particularly easy by selecting "View" and then the "Show Differences Only" option - this refers to version 1.8 of this software). 2. On UNIX/LINUX systems - Here we use the "diff" command from a shell window (and set the option to ignore blank spaces). A shell script may be used to perform this task automatically (including running HYPLAS and checking for result file differences) for all benchmarked examples provided. IMPORTANT: THE ONLY ACCEPTABLE DIFFERENCES BETWEEN A THE NEWLY GENERATED RESULT FILES AND THEIR BENCHMARKED COUNTERPARTS ARE THE DIMENSIONING PARAMETERS (FROM FILE MAXDIM.INC) USED TO COMPILE THE NEW EXECUTABLE (THESE PARAMETERS ARE PRINTED RIGHT AT THE BEGINNING OF THE RESULT FILES) AND NUMERICAL DIFFERENCES IN RESULTS DUE TO NUMERICAL "ROUNDING-OFF" (THESE ARE VERY SMALL DIFFERENCES THAT DEPEND ON THE PRECISION OF ARITHMETIC OPERATIONS IN THE PLATFORM USED). ALSO NOTE THAT THE EXAMPLES OF THE COMPANION TEXTBOOK DO NOT COVER ALL FEATURES OF HYPLAS. HENCE THIS TEST DOES NOT GUARANTEE THAT EVERYTHING IS WORKING PROPERLY. 3. THE H Y P L A S DIRECTORY TREE ================================ 3.(a) Summary ------- ../ HYPLAS_v2.0/ bin/ book_examples/ data_files/ result_files/ man/ html/ src/ CRYSTAL/ DAMAGE/ DAMAGED_ELASTIC/ DRUCKER_PRAGER/ ELASTIC/ ELEMENTS/ GENERAL/ MATERIALS/ MATHS/ MOHR_COULOMB/ OGDEN/ TRESCA/ VON_MISES/ VON_MISES_MIXED/ 3.(b) Description ----------- The HYPLAS program directory tree is organised as follows: ../HYPLAS_v2.0/ (this directory) This is the HYPLAS root directory, where the HYPLAS directory tree starts. ../HYPLAS_v2.0/bin/ This directory contains the file ERROR.RUN where most HYPLAS error/warning messages are. IMPORTANT: the environment variable HYPLASHOME should be set to this directory. Otherwise, HYPLAS will not find its error/warning messages when required. We also recommend that the EXECUTABLE of HYPLAS be stored in this directory. ../HYPLAS_v2.0/book_examples/ This directory has the following subdirectories: ../HYPLAS_v2.0/book_examples/data_files ../HYPLAS_v2.0/book_examples/result_files Refer to Section 2.(b) above for further details. ../HYPLAS_v2.0/man/ This is the HYPLAS documentation/manuals directory. It contains the following files: input_man.txt - A concise input data manual for HYPLAS in ASCII format; hyplas_calltree.txt - Contains a flowgraph (shows the call tree) of HYPLAS in ASCII-format. Note: calls to function subprograms are not included in this flowgraph; and the subdirectory: ../HYPLAS_v2.0/man/html This directory contains the hypertext (HTML) format Fortran source code and of manual pages of the entire HYPLAS program. Manual pages with descriptions of each function/subprogram including their argument list are linked to their corresponding HTML-format source code. This allows the user the navigate through the HYPLAS source code using a web browser. To start at the main program, use your web browser to open the file hyplas.html. This facility should be helpful to those trying to understand the flow of program HYPLAS. ../HYPLAS_v2.0/src/ This directory (and its subdirectories) contains the Fortran source code of HYPLAS. The files containing the sources are named following the standard practice: .f where is the name of the FORTRAN procedure (subroutine, function subprogram, etc.) whose source code is in file .f. The source code of the HYPLAS main program is in file hyplas.f and the HYPLAS database (COMMON blocks, array dimensioning parameters and other global parameters) is coded in the "include files" ELEMENTS.INC GLDBASE.INC MATERIAL.INC MAXDIM.INC in this directory. In addition, this directory contains a file named "Makefile" (UNIX-LINUX Release only) which may be used for compiling and linking HYPLAS in UNIX/LINUX systems. The subdirectories of ../HYPLAS_v2.0/src are as follows: ../HYPLAS_v2.0/src/CRYSTAL Contains the source code of all procedures related to the finite strain single crystal plasticity model implemented in HYPLAS. ../HYPLAS_v2.0/src/DAMAGE Source files of the procedures related to the Lemaitre ductile damage model implementation. ../HYPLAS_v2.0/src/DAMAGED_ELASTIC Source files of the procedures related to the damaged elasticity model with crack closure effect. ../HYPLAS_v2.0/src/DRUCKER_PRAGER Source files of the procedures related to the implemented Drucker-Prager plasticity model. ../HYPLAS_v2.0/src/ELASTIC Source files of the procedures related to the linear elasticity model (Hencky model under large strains) implemented. ../HYPLAS_v2.0/src/ELEMENTS Source files of the element interfaces and element-related procedures. ../HYPLAS_v2.0/src/GENERAL Source files of general procedures. ../HYPLAS_v2.0/src/MATERIALS Source files of the material interfaces. ../HYPLAS_v2.0/src/MATHS Source files of the mathematical procedures. ../HYPLAS_v2.0/src/MOHR_COULOMB Source files of the procedures related to the implemented Mohr-Coulomb plasticity model. ../HYPLAS_v2.0/src/OGDEN Source files of the procedures related to the implemented Ogden hyperelasticity model. ../HYPLAS_v2.0/src/TRESCA Source files of the procedures related to the implemented Tresca plasticity model. ../HYPLAS_v2.0/src/VON_MISES Source files of the procedures related to the implemented von Mises plasticity model with isotropic hardening. ../HYPLAS_v2.0/src/VON_MISES_MIXED Source files of the procedures related to the implemented von Mises plasticity model with mixed isotropic/kinematic hardening. 4. CROSS-REFERENCING BETWEEN THE SOURCE CODE AND THE TEXTBOOK ========================================================== Many references are made in the textbook to various subprograms of HYPLAS. These are usually made when a particular procedure described in the text is implemented in the program. The reader should refer to the textbook index. Also, a substantial number of comment lines have been added to the source code of HYPLAS with reference to sections, figures, boxes, etc of the textbook related to the part of the code in question. Such references are usually displayed after the word "REFERENCE:" (in capitals) on commented lines. Searching for this word will take you to the line of code where the particular routine has a reference to the textbook. NOTE: Occasional references to other textbooks/journal papers are also made following the word "REFERENCE:" on commented lines. 5. HYPLAS ERROR MESSAGING ====================== Most error/warning messages issued by HYPLAS are in the ASCII-format file ERROR.RUN (kept in the HYPLASHOME directory - ../HYPLAS_v2.0/bin). All such error/warning messages have an identification code (e.g. ED0015) which is printed both to the standard output (this is usually the computer screen) and to the relevant results file. If you wish to find where in the source code a particular message is being issued, then perform a search for the corresponding message identification code in the entire source code of HYPLAS. 6. FURTHER REMARKS ON HYPLAS ========================= 6.(a) Program efficiency THIS SECTION IS OF INTEREST ONLY TO THOSE WANTING TO MAKE HYPLAS RUN FASTER. It is particularly stressed in the textbook that this program has not been designed having efficiency in mind (refer to Section 5.1.2 of the textbook). Its structure has been designed mainly to illustrate in a relatively clear manner the computer implementation of the techniques and algorithms described in the text, with a particular view to the implementation of solid constitutive models and finite elements. For those who are especially interested in the speed of the code, there are a few tips that could help in this direction. Unfortunately, these involve modifications to the source code which is probably most appropriate to readers with a good level of experience in finite element programming. To those with this particular interest, we can suggest the following: (i) The use of faster linear solvers This is probably the change that would result in a greater gain in efficiency. The Frontal Method adopted in subroutine FRONT (file ../HYPLAS_v2.0/src/GENERAL/front.f) has been designed originally to save memory (back in the days when computer memory was severely limited). There are currently a vast number of methodologies which focus on speeding up the linear solution, in addition to reducing memory storage requirements (which is a particularly important issue in the solution of large scale problems). Some of these are extensions/refinements of the original Frontal solver. We remark that a number of such procedures (with their respective source codes) are available (conditions may apply) from the LAPACK (Linear Algebra PACKage - http://www.netlib.org/lapack) repository or from the HSL Library (http://www.cse.cse.scitech.ac.uk/nag/hsl). For the reader interested in gaining speed, we would recommend the replacement of the existing solver of FRONT by a faster one. We remark though that this is a substantial programming task. Another aspect here is the fact that computing times in FRONT are directly linked to the frontwidth of the system which, in the present version of HYPLAS is fixed and depends, for a given mesh, on how the degrees of freedom are numbered (node numbering). The incorporation of a frontwidth optimiser (which re-numbers the degrees of freedom in order to minimise the frontwidth) in FRONT could produce some good savings in computing times. Such savings become particularly noticeable in larger problems where the original node numbering produces an excessively large frontwidth. (ii) Material-specific computations The issues pointed out here affect only the computing times for specific material models and are expected to have a much lower impact in overall speed than the linear solver issue discussed above. Some of the material model-specific computations carried out in HYPLAS could be made a bit faster. For example, for isotropic models whose stress update is carried out in the principal stress space (such as the Tresca and Mohr-Coulomb models - see routines SUTR and SUMC, files ../HYPLAS_v2.0/src/TRESCA/sutr.f and ../HYPLAS_v2.0/MOHR_COULOMB/sumc.f, respectively) the spectral decomposition of the stress in carried out in the state update update routine and then repeated in the corresponding routine for computation of the consistent tangent operator (refer to files ../HYPLAS_v2.0/src/TRESCA/cttr.f and ../HYPLAS_v2.0/src/MOHR_COULOMB/ctmc.f, respectively, for the Tresca and Mohr-Coulomb plasticity models). Some savings in computing time can be achieved here by storing the stress eigenprojection tensors (these can be stored as state variables) during the execution of the state updating and then retrieving them later for use in the computation of the consistent tangent operator. This change can be incorporated to the code relatively easily. The computation of the exponential map and is derivative for the single crystal plasticity model (routines EXPMAP, file ../HYPLAS_v2.0/src/CRYSTAL/expmap.f and DEXPMP, file ../HYPLAS_v2.0/src/CRYSTAL/dexpmp.f) is carried out in three dimensions (these routines have been adapted from an earlier three-dimensional code). To improve efficiency, these can be adapted to work only in two-dimensional problems by removing the unnecessary operations related to the third dimension. 6.(b) Output of nodal averaged values The reader should be aware that the way in which nodal averaged values of stresses and other variables are calculated in HYPLAS is very basic (and rudimentary). This feature of the program is made available only to help those interested in producing contour plots, etc from results presented in HYPLAS result files and should be useful in many circumstances of interest. This facility has in fact been used in producing many of the figures presented in the textbook. But note, for example, that the values of incremental plastic multipliers for plasticity models may take (inadmissible) negative values when extrapolated from Gauss-point to nodes and averaged. We remark that more sophisticated and refined techniques of transferring Gauss point values of variables to nodal points and obtaining the corresponding smoothed field are available in the current literature. These fall outside the scope of the companion textbook of HYPLAS.
Platform: | Size: 11008084 | Author: gtcewli3 | Hits:

[SourceCode视频会议源码

Description: AcmCodec.cpp AcmCodec.h AddrBookDlg.cpp AddrBookDlg.h AudioPage.cpp BandWidthDlg.cpp BandWidthDlg.h [bin] BitCtl.lib CallDlg.cpp CallDlg.h CapturePage.cpp CapVideo.cpp CapVideo.h Color.lib Connection.cpp Connection.h DIBDraw.cpp DIBDraw.h DisplayPage.cpp Dogdll.h dogdll.lib G723Codec.h GDll.lib Global.cpp Global.h H2250Msg.txt H323Wnd.cpp H323Wnd.h HardwarePage.cpp HardwarePage.h HardwareSheet.cpp HardwareSheet.h [hlp] InfoTimer.cpp InfoTimer.h InputDlg.cpp InputDlg.h LanCodec.h LanMsg.cpp LanMsg.h LanVideo.lib ListenSocket.cpp ListenSocket.h LocalAudioThread.cpp LocalAudioThread.h LocalAudioWnd.cpp LocalAudioWnd.h LocalVideoThread.cpp LocalVideoThread.h LocalVideoWnd.cpp LocalVideoWnd.h MainFrm.cpp MainFrm.h MainFrm2.cpp MainFrm3.cpp MainFrm4.cpp MainFrm5.cpp MakeHelp.bat McastSocket.cpp McastSocket.h MediaQueue.cpp MediaQueue.h MessageDlg.cpp MessageDlg.h Mixer.cpp Mixer.h Netmeeting.txt NetoCtrl.h NetoCU.aps Netocu.clw NetoCU.cpp NetoCU.dsp NetoCU.dsw NetoCU.h NetoCU.ncb NetoCU.opt NetoCU.plg NetoCU.rc NetoCU.reg NetoCU.sln NetoCU.sln.old NetoCU.vcproj NetoCU.vcproj.old NetoCUDoc.cpp NetoCUDoc.h NetoCUView.cpp NetoCUView.h NetworkPage.cpp pop_Nr_connect.pop process.txt ProgDlg.cpp ProgDlg.h QuestionDlg.cpp QuestionDlg.h ReadMe.txt RemoteAudioThread.cpp RemoteAudioThread.h RemoteAudioWnd.cpp RemoteAudioWnd.h RemoteVideoThread.cpp RemoteVideoThread.h RemoteVideoWnd.cpp RemoteVideoWnd.h [res] resource.h RgbYuv.h Ring.dat SpeakerDlg.cpp SpeakerDlg.h Splash.cpp Splash.h StdAfx.cpp StdAfx.h TcpSocket.cpp TcpSocket.h Timer.cpp Timer.h TipDlg.cpp TipDlg.h UdpSocket.cpp UdpSocket.h VersionControl.cpp VersionControl.h VideoWnd.cpp VideoWnd.h VM 视频会议.rar WaveFile.cpp WaveFile.h WaveForm.h WaveIn.cpp WaveOut.cpp win32dll.lib YUVDraw.cpp ......
Platform: | Size: 3101897 | Author: awu0000 | Hits:

[Windows Developccombobox

Description: 自动完成的复合框的实现在AutoCompleteCombo.cpp和AutoCompleteCombo.h两个文件中,用户可以把这两个文件引入自己的工程中,删除"工程名.clw"文件后退出,再次进入工程系统会提示找不到"工程名.clw"文件,选择"“是(Yes)"重新创建一个,接下来在弹出的对话框里选择"Add all"就可以在新工程中使用CAutoCompleteCombo这个类了(注意引入头文件),我在示例对话框中创建了一个CAutoCompleteCombo类型的变量"m_combo",在对话框的"nInitDialog()"函数中添加了以下语句: // TODO: Add extra initialization here m_combo.AddString("America") m_combo.AddString("British") m_combo.AddString("China") m_combo.AddString("Dalian") m_combo.AddString("England") m_combo.AddString("France") 这样,用户在输入这些字符的头几个字符(不区分大小写)就可以看到自动完成的效果了.-automatic composite frame to complete the realization of the AutoCompleteCombo.cpp and AutoCompleteCombo.h two documents, the user can introduce these two documents of the project, delete the "project name. Clw documents "to withdraw, once again entered the system is not able to find" who works. Clw "document choose "" (Yes), "a re-creation of, the next in the pop-up dialog box you select" Add all "on the new projects CAutoCompleteCombo use of this category (Note the introduction of the first paper), in the example I created a dialog CAutoCompleteCombo type of a variable" m _combo "in the box" nInitDialog () "function to add the following phrase :// TODO : Add extra initialization here m_combo.AddString (" America &quo
Platform: | Size: 27648 | Author: wang | Hits:

[OpenGL programview3ds

Description: 源码3d格式转化软件view3ds下载 1,用VIEW3DS打开*.3ds文件; 2,左键点击打开的VIEW3DS显示区上任意一点将会弹出选择菜单; 3,按下E键选择:Export OpenGL C Code,将会自动生成两个文件*.h和   *.gl; 4,将两个文件拷到你的工程(为OpenGL环境)目录下; 5,在你的工程中加入#include"*.h"; 6,给*.h文件中生成的显示列表赋id,Model = GL3DS_initialize_--()   "--"代表3ds文件的名称; 7,调用显示列表:glCallList(Model) 。   ok!-source 3d format conversion software download a view3ds with VIEW3DS open*. 3ds documents; 2, Click on the button to open the display area VIEW3DS arbitrary point on the menu will pop up; 3, press the button to select E : Export OpenGL C Code will automatically generate two documents*. H*. Gl; 4, the two documents will peruse your project (for OpenGL Environment) directory; 5. your works include# include "*. h"; 6 to*. H documents generated by the display lists given id, Model = GL3DS_initialize_-- () "--" document on behalf of 3ds the name; 7, calling the display lists : glCallList (Model). Ok!
Platform: | Size: 45056 | Author: 沈淳 | Hits:

[Dialog_WindowClickDialog

Description: 点击按钮,弹出另一个对话框的Demo 第一步:添加(Insert Dialog)要弹出的Dialog,根据自己需要可以设计界面,因为我是一个简单Demo,所以很简单! 第二步:为添加的Dialog添加建立成一个继承DLG的类,class CDialog1 : public CDialog 第三步:在主对话框中为按钮添加函数。如下: void CClickDialogDlg::OnButton1() { // TODO: Add your control notification handler code here CDialog1 dlg dlg.DoModal() } 不要忘记#include "Dialog1.h"-Click of a button, another dialog box pop Demo of the first step: add (Insert Dialog) to the pop-up Dialog, according to their own needs can be designed interface, because I am a simple Demo, so very simple! Step two: add Dialog to add the establishment of a succession of DLG class, class CDialog1: public CDialog third step: in the main dialog box for the button to add the function. As follows: void CClickDialogDlg:: OnButton1 () (//TODO: Add your control notification handler code here CDialog1 dlg dlg.DoModal ()) do not forget# Include
Platform: | Size: 24576 | Author: SeVen Lee | Hits:

[Special EffectsDctQuant

Description: 工程名为DctQuant,编程实现了一帧CIF格式4:2:0的YUV图像的H.264的整数变换、量化以及逆量化、逆变换。具体的功能表述如下: 1、首先按“打开YUV”按钮,选择一帧格式为CIF的4:2:0的YUV图像(默认的YUV图像的格式为4:2:0的CIF格式)。选择完成后,可以看到显示的输入图像。 2、输入QP值,QP是0到51之间的整数值,超出范围,会弹出对话框提示。QP默认为28。注意:当改变QP值为0时,即没有量化,则点击转换按钮显示出的PSNR值即为输入图像的PSNR值。 3、点击转换按钮,可以看到经过变换量化和逆量化逆变换过程以后输出的图像以及显示输出图像的PSNR值(保留小数点后6位)和默认4x4块号为0的原始各像素值、整数变换后的值、量化后、逆量化后、逆变换后的值。 4、可以手动改变块号,块号的范围为0-6335,超出范围会弹出对话框提示。然后单击“输入块号”按钮即可显示此块号对应的原始各像素值、整数变换后的值、量化后、逆量化后、逆变换后的值。 -Works entitled DctQuant, programming of a CIF format, 4:2:0 YUV images H.264 integer transform, quantization, and inverse quantization, inverse transform. Expression of specific functions are as follows: 1, first press the "Open YUV" button, select a format for the CIF of the 4:2:0 YUV image (the default YUV image format 4:2:0 CIF format). Selection is complete, you can see displayed in the input image. 2, enter the QP value, QP is an integer between 0-51 values out of range, will pop-up dialog box prompt. QP default is 28. Note: When changing the QP value is 0, that is not quantified, then click the convert button to show the PSNR values of the PSNR values shall be the input image. 3, click the Convert button, you can see through the transformation inverse quantization and inverse quantization output of the image after the transformation process and display the output image PSNR values (retention decimal 6), and the default 4x4 block No. 0 of the original values of each pixel , int
Platform: | Size: 446464 | Author: 王婉君 | Hits:

[ApplicationsJB_Setup_En_V556

Description: 人机界面POP文本显示器第 POP-HMI HMI) , POP-HMI POP 50 , 22RS232/RS485/RS4LCD IP65 -Man-machine interface text display POP first POP-HMI HMI), POP-HMI POP 50, 22RS232/RS485/RS4LCD IP65
Platform: | Size: 7305216 | Author: 杨东东 | Hits:

[GDI-BitmapSaveAvi

Description: 压缩存储: SaveAvi [程序功能] 本程序提供图像显示和软件压缩存储的简单演示。 [适用的采集卡类型]: 本程序适用于mvboard1.h和mvboard2.h中包含的所有板卡。 [操作步骤] 首先,点击AVI采集按钮,此时会弹出一个对话框,在这里可以选择想要用的编解码器的种类和压缩质量。 然后,点击确定,此时就开始压缩存储了。 最后,点击停止采集,就会在当前目录下生成一个AVI文件。-Compressed storage: SaveAvi [program features] This program provides image display and software compression and storage of a simple demonstration. [Applicable to the acquisition card type]: This procedure applies to mvboard1.h and mvboard2.h contains all the boards. [Steps] First, click the AVI capture button, will pop up a dialog box where you can choose the codec you want to use the type and compression quality. Then, click OK, this time began to compress stored. Finally, click the Stop acquisition, will be in the current directory to generate a AVI file.
Platform: | Size: 141312 | Author: Nahuy Nil | Hits:

[GDI-BitmapSequenceCapture

Description: 连续帧采集: SequenceCapture [程序功能]: 本程序提供了连续采集存图的简单例子。 [适用的采集卡类型]: 本程序适用于mvboard1.h和mvboard2.h中包含的所有板卡。 [操作步骤]: 首先要点击“初始化设备”按钮,实现对板卡的初始化,能看到视频图像。 点击“连续帧采集”按钮,弹出一个对话框,可以输入采集帧数和选择存储路径及保存类型,并能输入文件。设置好后,点击“OK”,就开始连续采集和存图了。 最后,要结束程序,请按“退出”按钮。-Continuous frame grabber: SequenceCapture [program features]: This procedure provides a continuous deposit collected graph simple example. [Applicable to the acquisition card type]: This procedure applies to mvboard1.h and mvboard2.h contains all the boards. [Steps]: first click on " Initialize Device" button, to achieve the initialization of the board, could see video images. Click " continuous frame capture" button to pop up a dialog box, you can enter the path to capture frames and choice of storage and preservation types, and can input file. Set up, click " OK" , began to map the continuous collection and deposit. Finally, to end the program, please click " Exit" button.
Platform: | Size: 171008 | Author: Nahuy Nil | Hits:

[Windows Developgd

Description: 自己建立一个基于MFC的程序,并能对鼠标左键单击操作进行响应(弹出消息框)。 在程序编写过程中注意以下几点: (1) 建立工程的类型(Win32 Application)及需要包含的头文件(afxwin.h) (2) 从CWinApp派生自己应用程序类,从CFrameWnd派生自己框架窗口类 (3) 注意程序的构建过程:从应用程序类对象开始,调用基类构造函数,在其中调用InitInstance(),因其为虚函数,会调用自己重载的InitInstance(),我们可以在其中创建窗口。 (4) 在MFC程序中使用宏进行消息映射, 消息的处理放在框架程序中。 BEGIN_MESSAGE_MAP(…,…) …//消息映射宏 END_MESSAGE_MAP -Build a MFC-based program, and can operate on the left mouse button click to respond (pop-up message box). In the programming process note the following: (1) the establishment of project types (Win32 Application) and the need to include the header file (afxwin.h) (2) derived from its own application class CWinApp, CFrameWnd derived from their own frame window class (3) Note that the program construction process: starting from the application class object, call the base class constructor, in which the call to InitInstance (), because the virtual function will call itself overloaded InitInstance (), in which we can create window. (4) use the macro in the MFC program for message maps, message handling on the framework of the program. BEGIN_MESSAGE_MAP (..., ...) ...// Message map macros END_MESSAGE_MAP
Platform: | Size: 15360 | Author: 夏天 | Hits:

[source in ebookTDDOWNLOAD

Description: #include <stdio.h> #include <math.h> #include <stdlib.h> #include <float.h> unsigned __int64 mulmod(unsigned __int64 a, unsigned __int64 b, unsigned __int64 m) { static const double _2_64 = 18446744073709551616.0 unsigned __int64 rh, rl __asm { xor edi,edi mov eax,dword ptr [a] mov ebx,dword ptr [b] push eax mov ecx,dword ptr [b+4] mul ebx mov dword ptr [rl],eax mov dword ptr [rl+4],edx pop eax mul ecx mov dword ptr [rh],edx mov dword ptr [rh+4],edi add dword ptr [rl+4],eax adc dword ptr [rh],edi mov eax,dword ptr [a+4] mul ebx
Platform: | Size: 9861120 | Author: hh | Hits:

[GDI-BitmapDataShowClass

Description: 主要功能: 1.动态显示数据。在类中定义了两个大小为2000的double型数值。可显示小于2000组的X,Y数据。动态显示的原理为实时更新数据。只要更新x,y数据,在显示界面就会及时显示。 2.数据捕捉功能。当鼠标靠近数据点时,十字线会绘制一个红色的矩形捕捉框。 3.支持曲线平移,缩放,网格开关,时间显示以及文字说明。平移时,按住右键拖动鼠标;缩放时按住鼠标中键拖动鼠标。 4.支持颜色设置,具体可看弹出菜单。双击鼠标右键,弹出菜单可进行相应的操作。 5.类主要封装了一些设置函数和文件存储读取函数,在具体样例程序中列举了一些函数。具体函数可见点h文件,上面有具体说明。-Main features: 1. Dynamic display data. in the class defines two types of size 2000 double value. Group to show less than 2000 X, Y data. The principle of dynamic display is updated in real time data. As long as the updated x, y data in a timely manner in the display screen will display. 2. Data capture. When the mouse is near the data points, the cross line to draw a red rectangle will capture the box. 3. Support the curve of pan, zoom, grid switch, time display, and text. Pan, hold down the right-drag the mouse zoom, hold down the mouse button drag the mouse. 4. Support the color settings, specifically to see the pop-up menu. Double-click the right mouse button, pop-up menu for the appropriate action. 5. Principal function encapsulates some of the settings and file storage read function, in a specific sample program listed a number of functions. H files visible point specific function, the above specific description.
Platform: | Size: 168960 | Author: 黄雅威 | Hits:

[Linux-Unixui_aboutDialog.h

Description: Qt开发一个词典的对话框。能够弹出并显示用户和软件的一些描述信息-Qt development of a dictionary dialog box. To pop up and display some of users and software description
Platform: | Size: 1024 | Author: suncanoe | Hits:

[Otherlinearlistastack

Description: LinearList.h是线性表抽象类的头文件; LinearListSqu.h是顺序结构实现的线性表; LinearListLink.h是链表实现的线性表; StackSqu.h是堆栈类头文件,其中使用了LinearListSqu类,StackLink.h是堆栈类头文件,其中使用了LinearListLink类; main函数测试办法是压入10个元素,依次弹出,将该动作重复百万次并统计时间。-LinearList.h linear form abstract class header file LinearListSqu.h sequential structure to achieve linear table LinearListLink.h Chain achieve linear table StackSqu.h stack class header file, which LinearListSqu class , StackLink.h stack class header file, the use LinearListLink class the main function test is pressed into 10 elements, followed by pop-up, the action was repeated millions of times and statistical time.
Platform: | Size: 117760 | Author: meihanlei | Hits:

[Game ProgramMessageBox

Description: Pop up Message box by pressing H. good for help tips in games.
Platform: | Size: 8192 | Author: ManosDr | Hits:

[Windows Developvcgetodbcinst

Description: VC.NET获取电脑里所有安装的ODBC驱动程序名称,系统已经安装的ODBC驱动程序如下,使用SQLGetInstalledDrivers获取已安装驱动的名称(涵数在odbcinst.h里)。在弹出的窗口中,你会发现常用的ODBC驱动比如Access、SQLSERVER、Oracle等驱动列表已被显示出来。-VC.NET get all ODBC drivers installed computer name, ODBC drivers are already installed system, install the driver using SQLGetInstalledDrivers Gets the name (culvert in odbcinst.h years). In the pop-up window, you will find common ODBC drivers such as Access, SQLSERVER, Oracle and other drivers list has been displayed.
Platform: | Size: 28672 | Author: apudn71 | Hits:

[JSP/JavafDialog_v1.0.1

Description: fDialog是一个基于jQuery的弹出层插件,几乎能兼容包括IE6在内的所有常用浏览器。同时弹出层上所有元素都可以轻松定义。 fDialog遵循LGPL协议,永久性提供无偿服务。 更新日志 2015-06-03 :发布v1.0.0 2015-06-12 :更新为v1.0.1 1、宽高支持 width或w,height或h 两种方式调用 2、ajax模块,增加ajaxData参数 3、默认插件中增加拖拽功能(drag参数为true代码允许拖拽) 4、默认模板中去掉footer高度限制,防止在CSS3 box-sizing: border-box 模式下按钮超出的问题-FDialog is a jQuery based pop- up layer plug-in, almost compatible with all common browsers, including IE6. While all elements on the pop layer can be easily defined. FDialog follows the LGPL protocol and provides free services for the permanent. Update log 2015-06-03: v1.0.0 2015-06-12: update to v1.0.1 1, wide support for width or W, height or H two way call 2, AJAX module, increase ajaxData parameters 3, the default plug-in to add the drag parameter (true parameter for the drag) 4, the default template to remove the footer height limit, prevent the problem in the box-sizing: border-box CSS3 mode button beyond
Platform: | Size: 44032 | Author: xiaofei | Hits:
« 12 »

CodeBus www.codebus.net