E (Menus and Other Resources)
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
-
Empty menus not allowed
-
An END keyword appears before any menu items are defined in the MENU statement. Empty menus are not permitted by Microsoft Windows 32 Resource Compiler (RC). Make sure that you do not have any opening quotation marks within the MENU statement.
-
END expected in Dialog
-
The END keyword must appear at the end of a DIALOG statement. Make sure that there are no opening quotation marks left from the preceding statement.
-
END expected in menu
-
The END keyword must appear at the end of a MENU statement. Make sure that there are no mismatched BEGIN and END statements.
-
Error Creatingresource-name
-
Microsoft Windows 32 Resource Compiler (RC) could not create the specified binary resource (.RES) file. Make sure that it is not being created on a read-only drive. Use the /v option to find out whether the file is being created.
-
Expected Comma in Accelerator Table
-
Microsoft Windows 32 Resource Compiler (RC) requires a comma between the event and idvalue parameters in the ACCELERATORS statement.
-
Expected control class name
-
The class parameter of a CONTROL statement in the DIALOG statement must be one of the following control types: BUTTON, COMBOBOX, EDIT, LISTBOX, SCROLLBAR, STATIC, or user-defined. Make sure that the class is spelled correctly.
-
Expected font face name
-
The typeface parameter of the FONT statement in the DIALOG statement must be a character string enclosed in double quotation marks ("). This parameter specifies the name of a font.
-
Expected ID value for Menuitem
-
The MENU statement must contain a MENUITEM statement, which has either an integer or a symbolic constant in the MenuID parameter.
-
Expected Menu String
-
Each MENUITEM and POPUP statement must contain a text parameter. This parameter is a string enclosed in double quotation marks (") that specifies the name of the menu item or pop-up menu. A MENUITEM SEPARATOR statement requires no quoted string.
-
Expected numeric command value
-
Microsoft Windows Resource Compiler (RC) was expecting a numeric idvalue parameter in the ACCELERATORS statement. Make sure that you have used a #define statement to specify the value and that the constant used is spelled correctly.
-
Expected numeric constant in string table
-
A numeric constant, defined in a #define statement, must immediately follow the BEGIN keyword in a STRINGTABLE statement.
-
Expected numeric point size
-
The pointsize parameter of the FONT statement in the DIALOG statement must be an integer point-size value.
-
Expected Numerical Dialog constant
-
A DIALOG statement requires integer values for the x, y, width, and height parameters. Make sure that these values, which are included after the DIALOG keyword, are not negative.
-
Expected String in STRINGTABLE
-
A string is expected after each numeric stringid parameter in a STRINGTABLE statement.
-
Expected String or Constant Accelerator command
-
Microsoft Windows Resource Compiler (RC) was not able to determine which key was being set up for the accelerator. The event parameter in the ACCELERATORS statement might be invalid.
-
Expected VALUE, BLOCK, or END keyword.
-
The VERSIONINFO structure requires a VALUE, BLOCK, or END keyword.
-
Expecting number for ID
-
A number is expected for the id parameter of a CONTROL statement in the DIALOG statement. Make sure that you have a number or a #define statement for the control identifier.
-
Expecting quoted string for key
-
The key string following the BLOCK or VALUE keyword should be enclosed in double quotation marks.
-
Expecting quoted string in dialog class
-
The class parameter of the CLASS statement in the DIALOG statement must be an integer or a string enclosed in double quotation marks (").
-
Expecting quoted string in dialog title
-
The captiontext parameter of the CAPTION statement in the DIALOG statement must be a character string, enclosed in double quotation marks (").