• Code:0X0
Reason:Success!Description::
• Code:0X100
Reason:Window name is nullDescription::Each window must have a unique name.
• Code:0X101
Reason:Window name already used by other windowDescription::Each window must have a unique name.Assign another name to the window you are creating.
• Code:0X102
Reason:Window name too long.Description::A window name length cannot exceed 32 bytes.
• Code:0X103
Reason:The window your referred doesn't exist.Description::Check if you have assigned a correct window name or handler.
• Code:0X104
Reason:MYTUI system is not initialized.Description::Before doing any operations you must assure the function MYTUIinit() is called.
• Code:0X201
Reason:The internal pointer of window is null.Description::This is a severe internal error.
• Code:0X209
Reason:The specified window is not initialized.Description::Make sure that you have sepcified the correct window name or handler.
• Code:0X20A
Reason:Unknown object type.Description::Make sure you're running the correct MYTUI version.
• Code:0X20B
Reason:The window hasn't been drawn.Description::Some object functions must be called after the window is drawn.Refer to API manual for details.
• Code:0X20C
Reason:The window is in focus.Description::Some object functions cannot be called when the window is in focus.
• Code:0X210
Reason:The object name is null.Description::Each object must be assigned a unique name when it is created.
• Code:0X211
Reason:The specified name already exists when creating a object.Description::Each object must be assigned a unique name when it is created.
• Code:0X212
Reason:The specified object name too long when creating a object.Description::A object name length cannot exceed 32 bytes.
• Code:0X213
Reason:The specified object doesn't exist.Description::Make sure that you have sepcified the correct object name or handler.
• Code:0X214
Reason:The window cannot be activated.Description::If the window hasn't any objects can be activated, then the operation MYWINstar() will fail.
• Code:0X216
Reason:The request focusing on the specified object failed.Description::Either the object doesn't exist or it is an output-only object such as a label,progress bar etc.
• Code:0X217
Reason:The operation cannot be performed because underlying window has already been drawn.Description::Some functions(such as MYWINsetPosAndSize(),MYWINsetTitleMode()) must be called before drawing the window(function MYWINdraw())!
• Code:0X218
Reason:Cannot open the shared object in which your window callbacks reside.Description::You can assign appropriate preprocess,postprocess and escape callbacks for a window and call them in dynamic linking mode.If so,you must specify the correct path and name for the shared object.
• Code:0X219
Reason:A unresovled symbol found in the window's shared object.Description::Check your callback resource codes to assure all exported functions and variables have definite address if your window callbacks will be called in dynamic linking mode.
• Code:0X21A
Reason:Invalid data buffer for loading window parameters.Description::Make sure your TRF(MYTUI Resource File) is valid.
• Code:0X21B
Reason:Invalid window or object handler.Description::A handler cannot be zero!
• Code:0X21E
Reason:Window's preprocess function failedDescription::This is not a error since it is up to you to control the return code of the preprocess callback.MYTUI regards any non-zero codes as errors and issues warnings.
• Code:0X21F
Reason:Window's postprocess function failedDescription::This is not a error since it is up to you to control the return code of the preprocess callback.MYTUI regards any non-zero codes as errors and issues warnings.
• Code:0X220
Reason:The specified MyLabel object is not initialized.Description::Function MYWINnewObject() must be called before performing any operations on a label.
• Code:0X221
Reason:Either the specified handler not exist or it is not a handler of a MyLabel object.Description::Make sure you specified the correct handler for the MyLabel object.
• Code:0X223
Reason:Invalid data buffer for loading a MyLabel parameters.Description::Make sure your TRF(MYTUI Resource File) is valid.
• Code:0X240
Reason:The LineEditor is not initialized.Description::Function MYWINnewObject() must be called before performing any operations on a lineeditor.
• Code:0X241
Reason:The LineEditor is in focus. The request is denied.Description::Some operations such as MYLEDITsetDispLength() are not permited while the line editor is in focus. Refer to the manual for details.
• Code:0X248
Reason:Either the specified handler not exist or it is not a handler of a LineEditor object.Description::Make sure you specified the correct handler for the MyLineEdit object.
• Code:0X249
Reason:Invalid data buffer for loading MyLineEdit parameters.Description::Make sure your TRF(MYTUI Resource File) is valid.
• Code:0X24A
Reason:Cannot open shared object that the callbacks of the MyLineEdit reside.Description::Check if you assigned the correct shared object path for callbacks of the MyLineEdit in wdesigner tool.
• Code:0X24B
Reason:Cannot locate callback function in the shared object for the MyLineEdit.Description::Check if you assigned the correct callback function name for the MyLineEdit in wdesigner tool.
• Code:0X24C
Reason:The prompt string for the MyLineEdit is too long.Description::Make sure that prompt string is not more than 80 bytes.
• Code:0X24D
Reason:Invalid type for MyLineEdit.Description::It must be LEDIT_TYPE_STRING, LEDIT_TYPE_INT_B2 ,LEDIT_TYPE_INT_B8, LEDIT_TYPE_INT_B10, LEDIT_TYPE_B16 or LEDIT_TYPE_DOUBLE. The default type is LEDIT_TYPE_STRING if it is not specified.
• Code:0X24E
Reason:Connot convert the text of a MyLineEdit object into an integer or doulbe.Description::This error occurs only the type is LEDIT_TYPE_INT_XX or LEDIT_TYPE_DOUBE because an underflow or overflow occurs.
• Code:0X24F
Reason:There are invalid character in the text of an MyLineEdit object.Description::This usaually occurs when the type is LEDIT_TYPE_INT_XX or LEDIT_TYPE_DOUBLE because the text cannot be converted into an integer or double. Referr to strtol() or strtod() for more details.
• Code:0X250
Reason:Invalid time_t value when seting line edit's text from a time_t.Description::.
• Code:0X260
Reason:The MyButton is not initialized.Description::Function MYWINnewObject() must be called before performing any operations on a button.
• Code:0X261
Reason:The MyButton is in focus. The request is denied.Description::Some operations such as MYBUTTONsetBoxAttrib() are not permited while the button is in focus. Refer to the manual for details.
• Code:0X262
Reason:Either the specified handler not exist or it is not a handler of a MyButton object.Description::Make sure you specified the correct handler for the MyButton object.
• Code:0X264
Reason:Invalid data buffer for loading MyButton parameters.Description::Make sure your TRF(MYTUI Resource File) is valid.
• Code:0X265
Reason:Cannot open shared object that the callbacks of the MyButton reside.Description::Check if you assigned the correct shared object path for callbacks of the MyButton in wdesigner tool.
• Code:0X266
Reason:Cannot locate callback function in the shared object for MyButton object.Description::Check if you assigned the correct callback function name for the MyButton object wdesigner tool.
• Code:0X267
Reason:The prompt string for the MyButton object is too long.Description::Make sure that the prompt string is not more than 80 bytes.
• Code:0X268
Reason:The text for the MyButton object is NULL.Description::
• Code:0X280
Reason:The Drawdown ListBox is not initialized.Description::The drawdown listbox is the basis of some other widgets. It is not a standalone widget thus it is transparent to the end user. Report this error to xiaohuafan@yeah.net
• Code:0X281
Reason:The window has no room to contain the drawdown listbox.Description::Maybe the window's dimensions are too small. Note:The drawdown listbox is the basis of some other widgets. It is not a standalone widget thus it is transparent to the end user. Report this error to xiaohuafan@yeah.net
• Code:0X282
Reason:The Drawdown ListBox is in focus. The request is denied.Description::Some operations on drawdown listbox are not permited while the widget is in focus. Since the drawdown listbox is the basis of some other widgets( MyCombox, for example), you should check its derived widgets.
• Code:0X283
Reason:No item definitions for the drawdown listbox.Description::This error is usually occured when the user try to access items of the drawdown listbox( MYCOMBOXgetItemIndex() for example).
• Code:0X284
Reason:The specified item not found in the drawdown listbox.Description::
• Code:0X285
Reason:The item to be added into drawdown listbox cannot be null. It is a limitation since MYTUI version 1.2Description::
• Code:0X286
Reason:The value to be added into drawdown listbox cannot be null. It is a limitation since MYTUI version 1.2Description::
• Code:0X287
Reason:The item to be added into drawdown listbox already defined in the item array. It is a limitation since MYTUI version 1.2Description::An item must be unique within the drawdown listbox.
• Code:0X288
Reason:The value to be added into drawdown listbox already defined in the value array. It is a limitation since MYTUI version 1.2Description::An value must be unique within the drawdown listbox.
• Code:0X289
Reason:The index to refer item/value pair of drawdown list box is invalid.Description::Make sure it is greater than zero and is less than the items number.
• Code:0X2A0
Reason:The Combox object is not initialized.Description::Function MYWINnewObject() must be called before performing any operations on the object.
• Code:0X2A1
Reason:The Combox object is in focus and the request is denied.Description::Some operations such as MYCOMBOXsetListBoxAttrib() are not permited while the Combox object is in focus. Refer to the manual for details.
• Code:0X2A3
Reason:Either the specified handler not exist or it is not a handler of a Combox object.Description::Make sure you specified the correct handler for the Combox object.
• Code:0X2A4
Reason:Invalid item index for the specified Combox objec.Description::This error is issued by function MYCOMBOXgetItem(). Make sure you have specified the corrent index for the item.
• Code:0X2A6
Reason:The prompt string for the Combox object is too long.Description::Make sure that the prompt string is not more than 80 bytes.
• Code:0X2A7
Reason:Invalid data buffer for loading the Combox object parameters.Description::Make sure your TRF(MYTUI Resource File) where the Combox object resides is valid.
• Code:0X2A8
Reason:The lineedit component of the combox object is display-only.Description::This error is issued by function MYCOMBOXsetText() when the specified combox is not editabe.
• Code:0X2A9
Reason:The lineedit component of the combox object is editable.Description::This error is issued by function MYCOMBOXgetCurItemValue() when the specified combox is editabe.
• Code:0X2B9
Reason:The submenu name is null.Description::Each submenu has a unique name so you should give the non-null name for it when creating or accessing a submenu.
• Code:0X2C0
Reason:The submenu name is too long.Description::The length of submenu name cannot exceed 80 bytes.
• Code:0X2C1
Reason:The submenu name is already used by other submenu.Description::This error is usally occured when you add a submenu for a menuitem of a submenu. The submenu name must be unique within the submenu tree.
• Code:0X2C3
Reason:The specified submenu doesn't exist.Description::Make sure you have given the correct submenu ID.
• Code:0X2C4
Reason:The submenu object is not initialized.Description::Function MYWINnewObject() must be called before performing any operations on the object.
• Code:0X2C5
Reason:Null submenu pointer. It is an internal error.Description::Report this error to xiaohuafan@yeah.net
• Code:0X2C6
Reason:Null submenu item pointer. It is an internal error.Description::Report this error to xiaohuafan@yeah.net
• Code:0X2C7
Reason:The menu item name is too long.Description::The length of menu item name cannot exceed 80 bytes.
• Code:0X2C8
Reason:The menuitem name of submenu is already used by other menuitems.Description::This error is usally occured when you add a menu item for the submenu. The menu item name must be unique within the submenu tree.
• Code:0X2C9
Reason:The specified menu item doesn't exist.Description::Make sure you have given the correct menuitem ID.
• Code:0X2CC
Reason:Cannot add a submenu or a menu item because of two many menuitems or submenus.Description::MYTUI supports no more than 2048 submenu/menuitems at the same time.
• Code:0X2CE
Reason:The menuitem name of submenu is already used by other menuitems.Description::This error is usally occured when you add a menu item for the submenu. The menu item name must be unique within the submenu tree.
• Code:0X2D2
Reason:Invalid menu item type of a submenu.Description::Valid options are: MENUITEM_NORMAL, MENUITEM_IS_SEPERATOR or MENUITEM_HAS_SUBMENU.
• Code:0X2D3
Reason:Cannot open shared object that the callbacks of the submenu reside.Description::Check if you assigned the correct shared object path for callbacks of the pulldown/popup menu menu in wdesigner tool.
• Code:0X2D4
Reason:Cannot locate callback function in the shared object for submenu object.Description::Check if you assigned the correct callback function name for the pulldown/popup menu object in wdesigner tool.
• Code:0X2D5
Reason:Invalid privilege value for the submenu/menuitem.Description::The privilege should be a unsigned long value.
• Code:0X2E0
Reason:Pulldown menu pointer is null.Description::This is a severe internal error. Report this error to xiaohuafan@yeah.net
• Code:0X2E1
Reason:The pulldown menu object is not initialized.Description::Function MYWINnewObject() must be called before performing any operations on the pulldown menu.
• Code:0X2E2
Reason:The Pulldown Menu object is in focus and the request is denied.Description::Some operations such as MYPDMENUsetPos() are not permited while the object is in focus. Refer to the manual for details.
• Code:0X2E3
Reason:The submenu name is null.Description::Each submenu has a unique name so you should give a non-null name for it when creating or accessing a submenu.
• Code:0X2C0
Reason:The submenu name is too long.Description::The length of submenu name cannot exceed 80 bytes.
• Code:0X2E6
Reason:Unkown key binding function definiton for the pulldown menu.Description::This is a internal error. Please report it to xiaohuafan@yeah.net
• Code:0X2E7
Reason:Either the specified handler not exist or it is not a handler of a Pulldown Menu objectDescription::Make sure you specified the correct handler for the Pulldown Menu object.
• Code:0X2E8
Reason:There are no submenu definitions for the Pulldown Menu object.Description::Without submenu definitions a Pulldown Menu is almost useless(for example, it cannot be activated by MYTUI)
• Code:0X2E9
Reason:The submenu you want to access doesn't exist.Description::Make sure you specified the correct handler and submenu ID(or submenu name) for the Pulldown Menu and its submenu.
• Code:0X2F8
Reason:The menuitem you want to access doesn't exist.Description::Make sure you specified the correct handler and menuitem ID(or item name) for the Pulldown Menu and its menuitem.
• Code:0X2F9
Reason:Invalid data buffer for loading the Puldown Menu object's parameters.Description::Make sure your TRF(MYTUI Resource File) where the Pulldown Menu object resides is valid.
• Code:0X2FA
Reason:Invalid privilege value for the submenu or menuitem of the Pulldown Menu objectDescription::The privilege should be a unsigned long value.
• Code:0X400
Reason:The Popup Menu object you want to access doesn't exist.Description::Make sure you specified the correct handler for the popup menu object.
• Code:0X401
Reason:Invalid data buffer for loading the Popup Menu object's parameters.Description::Make sure your TRF(MYTUI Resource File) where the Popup Menu object resides is valid.
• Code:0X500
Reason:The scroll window object is not initialized.Description::Function MYWINnewObject() must be called before performing any operations on the scroll window object.
• Code:0X501
Reason:The scroll window object is in focus and the request is denied.Description::Some operations such as MYSWINDOWsetInvisible() are not permited while the object is in focus. Refer to the manual for details.
• Code:0X502
Reason:The parent window hasn't enough room to contain the scroll window object.Description::Maybe the parent window's dimensions are too small.
• Code:0X504
Reason:The file name for loading or saving scroll window's content is null or empty.Description::Make sure you specified the correct file name.
• Code:0X505
Reason:Cannot open the specified file for loading or saving scroll window's content.Description::Make sure you specified the correct file name or have the read/write permission.
• Code:0X506
Reason:The scroll window object you want to access doesn't exist.Description::Make sure you specified the correct handler for the scroll window object.
• Code:0X507
Reason:Cannot change the maximum line limit for the scroll window object.Description::For the reason of safety, if the scroll window already has some text lines, we cannot change the MaxLines property for it. Eithor set this property when creating object or after calling MYSWINDOWclear().
• Code:0X508
Reason:Cannot create a pipe while executing function MYSWINDOWexec().Description::Check your command for MYSWINDOWexec() to see if it is valid.
• Code:0X509
Reason:Invalid data buffer for loading the scroll window object's parameters.Description::Make sure your TRF(MYTUI Resource File) where the scroll window object resides is valid.
• Code:0X600
Reason:The listbox object is not initialized.Description::Function MYWINnewObject() must be called before performing any operations on the listbox object.
• Code:0X601
Reason:The listbox object is in focus and the request is denied.Description::Some operations such as MYLISTBOXsetMultiSelect() are not permited while the object is in focus. Refer to the manual for details.
• Code:0X602
Reason:The parent window hasn't enough room to contain the listbox object.Description::Maybe the parent window's dimensions are too small.
• Code:0X603
Reason:The prefix string too long.Description::Its length must be 2 bytes. The default value is '()' for multi-selection mode and '[]' for single-selection mode. You can assign other string for it.
• Code:0X604
Reason:The prefix string must be printable.Description::
• Code:0X605
Reason:The item index is beyond the actual available values.Description::It should be not less than 0 and less than the items number.
• Code:0X606
Reason:Items number has reached the maximum value, cannot add items any more.Description::Items number cannot exceed 4096.
• Code:0X607
Reason:The listbox object you want to access doesn't exist.Description::Make sure you specified the correct handler for the listbox object.
• Code:0X608
Reason:Invalid data buffer for loading the listbox object's parameters.Description::Make sure your TRF(MYTUI Resource File) where the listbox object resides is valid.
• Code:0X609
Reason:Cannot open shared object that the callbacks of the listbox object reside.Description::Check if you assigned the correct shared object path for callbacks of the listbox in wdesigner tool.
• Code:0X60A
Reason:Cannot locate callback function in the shared object for the listbox object.Description::Check if you assigned the correct callback function name for the listbox object in wdesigner tool.
• Code:0X700
Reason:The progress bar object is not initialized.Description::Function MYWINnewObject() must be called before performing any operations on the progress bar object.
• Code:0X701
Reason:The character for displaying progress bar must be printable.Description::The default value is a space char.
• Code:0X702
Reason:The progress bar object you want to access doesn't exist.Description::Make sure you specified the correct handler for the progress bar object.
• Code:0X703
Reason:Invalid data buffer for loading the progress bar object's parameters.Description::Make sure your TRF(MYTUI Resource File) where the progress bar object resides is valid.
• Code:0X780
Reason:The datagrid object is not initialized.Description::Function MYWINnewObject() must be called before performing any operations on the datagrid object.
• Code:0X781
Reason:The datagrid object is in focus and the request is denied.Description::Some operations such as MYDGRIDaddField() are not permited while the object is in focus. Refer to the manual for details.
• Code:0X78A
Reason:The request cannot be processed since the datagrid already has records of data.Description::Functions MYDGRIDaddField() and MYDGRIDaddFldOption() can only be called when the datagrid hasn't data records.
• Code:0X78B
Reason:The field name of the datagrid object cannot be null.Description::This error is raised functions MYDGRIDaddField() when a null field name is passed in.
• Code:0X78C
Reason:The field name of the datagrid object is too long.Description::The maximum length for the field name is 32 bytes.
• Code:0X78D
Reason:The field to be created already exists.Description::Check the field name if it is unique within the datagrid.
• Code:0X78E
Reason:Invalid field type when adding a field for the datagrid object.Description::The field type must be MYLINEEDIT, MYCOMBOX or MYLABEL.
• Code:0X78F
Reason:The display length for the field of the datagrid object is too long.Description::This length cannot be greater than the width of the datagrid( not include the box).
• Code:0X790
Reason:The field of the datagrid to be accessed doesn't exist.Description::Check if you have specified the correnct Window handler/Datagrid Handler/Field index for the field.
• Code:0X791
Reason:The specified line of data record in the datagrid object doesn't exist.Description::Check if you have specified the correct line index for the data record.
• Code:0X792
Reason:No data records exist in the datagrid object.Description::Check if you have inserted data records into the datagrid object.
• Code:0X793
Reason:Two many lines of data for the datagrid. Cannot add records anymore.Description::This error usually occurs when calling MYDGRIDinsertLine() or MYDGRIDappendLine(). Check if the line number has reached the limitation value. You can expand the limitation with MYDGRIDsetMaxLines() in this case.
• Code:0X794
Reason:Cannot set predefined select options for the specified field of the datagrid objectDescription::This error occurs when calling function MYDGRIDaddFldOption(). Only field of MYCOMBOX type can have select options. Check if you are really operating on a COMBOX field.
• Code:0X795
Reason:Cannot set text for the field with COMBOX type of the datagrid object.Description::This error occurs when applying function MYDGRIDsetText(). Since all cells with the COMBOX type are actually MYCOMBOX objects and their lineedit components are read-only, you should use function MYDGRIDsetCurItem() instead.
• Code:0X796
Reason:Cannot set current item for the specified cell of the datagrid objectDescription::This error occurs when calling function MYDGRIDsetCurItem() to cells which are not in MYCOMBOX type. Check the field index parameter(Col) please.
• Code:0X797
Reason:Too many field definitions. Cannot add fields for the datagrid anymore.Description::You cannot create more than 512 field definitions for a datagrid.
• Code:0X798
Reason:The datagrid is locked, request for adding/deleting data line is denied.Description::This error occurs when you tring to deleting or adding a data record in the deleting preprocess calback or inserting postprocess callback function. The operations are not permitted in such cases.
• Code:0X799
Reason:Cannot get select options for the specified field of the datagrid objectDescription::This error occurs when calling function MYDGRIDgetFldOption(). Only field of MYCOMBOX type can have select options. Check if you are really operating on a COMBOX field.
• Code:0X79A
Reason:Invalid option index when geting select options for the specified field of the datagrid objectDescription::This error occurs when calling function MYDGRIDgetFldOption(). Check if you have specified the valid option index for the COMBOX field.
• Code:0X7A0
Reason:Cannot open shared object that the callbacks of the datagrid object reside.Description::Check if you assigned the correct shared object path for callbacks of the datagrid in wdesigner tool.
• Code:0X7A1
Reason:Cannot locate callback function in the shared object for the datagrid object.Description::Check if you assigned the correct callback function name for the datagrid object in wdesigner tool.
• Code:0X7B1
Reason:The datagrid object you want to access doesn't exist.Description::Make sure you specified the correct handler for the datagrid object.
• Code:0X7B2
Reason:Invalid data buffer for loading the datagrid object's parameters.Description::Make sure your TRF(MYTUI Resource File) where the datagrid object resides is valid.
• Code:0X7B3
Reason:The option to be added into datagrid field cannot be null. It is a limitation since MYTUI version 1.2Description::
• Code:0X7B4
Reason:The value to be added into datagrid field cannot be null. It is a limitation since MYTUI version 1.2Description::
• Code:0X7B5
Reason:The option to be added into datagrid field already defined in the option array. It is a limitation since MYTUI version 1.2Description::An option must be unique within the datagrid field.
• Code:0X7B6
Reason:The value to be added into datagrid field already defined in the value array. It is a limitation since MYTUI version 1.2Description::An value must be unique within the datagrid field.
• Code:0X7B7
Reason:The index to refer item/value pair of datagrid field is invalid.Description::Make sure it is greater than zero and is less than the items number.
• Code:0X7B8
Reason:The datagrid field is not MYLINEEDIT.Description::This error occurs when call MYDGRIDsetFldLeditType().Make sure you are setting the text type for a MYLINEEDIT field.
• Code:0X7B9
Reason:The request is denied since it is issued from callback functions.Description::Some functions cannot be executed in callback functions such as MYDGRIDsetCurLine().
• Code:0X7BA
Reason:The string for searching in datagrid is null.Description::A null string is meaningless for searching.
• Code:0X7BB
Reason:The string for searching is too long!Description::It shouldn't be greater than 256 bytes.
• Code:0X7BC
Reason:No data found for the search condition in datagrid!Description::
• Code:0XC00
Reason:Cannot open the MYTUI Resource File(TRF).Description::Make sure you specified the correct path for the TRF file.
• Code:0XC01
Reason:Cannot read the MYTUI Resource File(TRF).Description::Make sure you have permission to read the TRF file.
• Code:0XC02
Reason:Cannot write the MYTUI Resource File(TRF).Description::Make sure you have permission to write the TRF file.
• Code:0XC03
Reason:Invalid MYTUI Resource File(TRF).Description::Make sure the TRF file is really created by Wdesigner tool.
• Code:0XC04
Reason:Invalid version of MYTUI Resource File(TRF).Description::Maybe the version of your wdesigner tool is too low to read the TRF file in high version.
• Code:0XC05
Reason:Corrupted MYTUI Resource File(TRF).Description::Parameter length for the window definition is wrong. The file is corrupted.
• Code:0XC06
Reason:Corrupted MYTUI Resource File(TRF).Description::Object number of the MYTUI window is wrong. The file is corrupted.
• Code:0XC07
Reason:Corrupted MYTUI Resource File(TRF).Description::Parameter length of certain MYTUI object is wrong. The file is corrupted.
• Code:0XC08
Reason:MYTUI Resource File(TRF) name is null.Description::Check if you have specified a null name for the TRF file.
• Code:0XC09
Reason:Severe error: Object parameter length error.Description::Report this error to xiaohuafan@yeah.net ASAP.
• Code:0XC0A
Reason:The MYTUI Resource File(TRF) name doesn't match the MYTUI window.Description::Check if your TRF file name is in the form like 'xxx.trf' where xxx must be the same as your MYTUI window name and the file suffix must be 'trf'.
• Code:0XC0B
Reason:The MYTUI Resource File(TRF) name doesn't match the MYTUI window.Description::Check if your TRF file name is in the form like 'xxx.trf' where xxx must be the same as your MYTUI window name and the file suffix must be 'trf'.
• Code:0XC0C
Reason:The MYTUI Resource File(TRF) name doesn't match the MYTUI window.Description::Check if your TRF file name is in the form like 'xxx.trf' where xxx must be the same as your MYTUI window name and the file suffix must be 'trf'.
