Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

menu_new(3menu) [debian man page]

menu_new(3MENU) 														   menu_new(3MENU)

NAME
mitem_new - create and destroy menu items SYNOPSIS
#include <menu.h> ITEM *new_item(const char *name, const char *description); int free_item(ITEM *item); DESCRIPTION
The function new_item allocates a new item and initializes it from the name and description pointers. Please notice that the item stores only the pointers to the name and description. Those pointers must be valid during the lifetime of the item. So you should be very careful with names or descriptions allocated on the stack of some routines. The function free_item de-allocates an item. Please notice that it is the responsibility of the application to release the memory for the name or the description of the item. RETURN VALUE
The function new_item returns NULL on error. It sets errno according to the function's failure: E_BAD_ARGUMENT Routine detected an incorrect or out-of-range argument. E_SYSTEM_ERROR System error occurred, e.g., malloc failure. The function free_item returns one of the following: E_OK The routine succeeded. E_BAD_ARGUMENT Routine detected an incorrect or out-of-range argument. E_CONNECTED Item is connected to a menu. E_SYSTEM_ERROR System error occurred (see errno). SEE ALSO
ncurses(3NCURSES), menu(3MENU). NOTES
The header file <menu.h> automatically includes the header file <curses.h>. PORTABILITY
These routines emulate the System V menu library. They were not supported on Version 7 or BSD versions. AUTHORS
Juergen Pfeifer. Manual pages and adaptation for new curses by Eric S. Raymond. menu_new(3MENU)

Check Out this Related Man Page

menu_new(3MENU) 														   menu_new(3MENU)

NAME
mitem_new - create and destroy menu items SYNOPSIS
#include <menu.h> ITEM *new_item(const char *name, const char *description); int free_item(ITEM *item); DESCRIPTION
The function new_item allocates a new item and initializes it from the name and description pointers. Please notice that the item stores only the pointers to the name and description. Those pointers must be valid during the lifetime of the item. So you should be very careful with names or descriptions allocated on the stack of some routines. The function free_item de-allocates an item. Please notice that it is the responsibility of the application to release the memory for the name or the description of the item. RETURN VALUE
The function new_item returns NULL on error. It sets errno according to the function's failure: E_BAD_ARGUMENT Routine detected an incorrect or out-of-range argument. E_SYSTEM_ERROR System error occurred, e.g., malloc failure. The function free_item returns one of the following: E_OK The routine succeeded. E_BAD_ARGUMENT Routine detected an incorrect or out-of-range argument. E_CONNECTED Item is connected to a menu. E_SYSTEM_ERROR System error occurred (see errno). SEE ALSO
ncurses(3NCURSES), menu(3MENU). NOTES
The header file <menu.h> automatically includes the header file <curses.h>. PORTABILITY
These routines emulate the System V menu library. They were not supported on Version 7 or BSD versions. AUTHORS
Juergen Pfeifer. Manual pages and adaptation for new curses by Eric S. Raymond. menu_new(3MENU)
Man Page

2 More Discussions You Might Find Interesting

1. Programming

Error compiling GTK Accelerator (C programming)

I believe this may be a difference in GTK+-2.0 and GTK+-3.0. I followed this tutorial and ended up with this error: # gcc -Wall -g mnemonics.c -o mnemonics `pkg-config --cflags gtk+-3.0` `pkg-config --libs gtk+-3.0` mnemonics.c: In function ‘main': mnemonics.c:44:61: error: ‘GDK_q' undeclared... (3 Replies)
Discussion started by: Azrael
3 Replies

2. Programming

Combining Qt with GTK only one problem!

I am using this code: g_signal_connect(showapp_option, "activate", G_CALLBACK(&MainWindow::show_app), appindicator); so as to connect my indicator menu item to the function show_app(), and it works just fine, irregardless the fact that I get the following warning: warning: converting from... (11 Replies)
Discussion started by: hakermania
11 Replies