form_field_buffer(3X)

πŸ“¦ version 15.1, in freebsd 14.5, freebsd 15.1

πŸ’– form_field_buffer(3X) β€” field buffer control

okay bestie, welcome to this Library calls page for form_field_buffer(3X). we're doing field buffer control today, and it's giving very specific forms-library energy. no cap. ✨

🌸 NAME 🌸

form_field_buffer β€” field buffer control. that's the whole name, and yes it's literally that on the tin. πŸ’…

✨ SYNOPSIS ✨

okay so include this and you're in:

#include <form.h>

int set_field_buffer(FIELD *field, int buf, const char *value);
char *field_buffer(const FIELD *field, int buffer);

int set_field_status(FIELD *field, bool status);
bool field_status(const FIELD *field);

int set_max_field(FIELD *field, int max);

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the tea, function by function. 🫢

The function set_field_buffer sets the numbered buffer of the given field to contain a given string:

  • Buffer 0 is the displayed value of the field. πŸ‘‘
  • Other numbered buffers may be allocated by applications through the nbuf argument of (see form_field_new(3X)) but are not manipulated by the forms library. iykyk β€” those extras are not the library's business.

The function field_buffer returns a pointer to the contents of the given numbered buffer:

  • The buffer contents always have the same length, and are padded with trailing spaces as needed to ensure this length is the same. yes, literally the same length twice β€” that's the manpage tea. β˜•
  • The buffer may contain leading spaces, depending on how it was set. πŸ™ˆ
  • The buffer contents are set with set_field_buffer, or as a side effect of any editing operations on the corresponding field. ✍️
  • Editing operations are based on the window which displays the field, rather than a string. The window contains only printable characters, and is filled with blanks. If you want the raw data, you must write your own routine that copies the value out of the buffer and removes the leading and trailing spaces. 😭✨
  • Because editing operations change the content of the buffer to correspond to the window, you should not rely on using buffers for long-term storage of form data. fr fr, don't treat it like your form-data vault.

The function set_field_status sets the associated status flag of field; field_status gets the current value. The status flag is set to a nonzero value whenever the field changes. πŸ”₯

The function set_max_field sets the maximum size for a dynamic field. An argument of 0 turns off any maximum size threshold for that field. periodt. πŸ’…

πŸ’€ RETURN VALUE πŸ’€

The field_buffer function returns NULL on error. It sets errno according to their success:

  • E_OK β€” the routine succeeded.
  • E_BAD_ARGUMENT β€” routine detected an incorrect or out-of-range argument.

The field_status function returns TRUE or FALSE. 🫢

The remaining routines return one of the following:

  • E_OK β€” the routine succeeded.
  • E_SYSTEM_ERROR β€” System error occurred (see errno(3)).
  • E_BAD_ARGUMENT β€” Routine detected an incorrect or out-of-range argument.

πŸŽ€ NOTES πŸŽ€

When configured for wide characters, field_buffer returns a pointer to temporary storage (allocated and freed by the library).

The application should not attempt to modify the data. It will be freed on the next call to field_buffer to return the same buffer. bestie, do not touch it. πŸ’…

🌈 PORTABILITY 🌈

These routines emulate the System V forms library. They were not supported on Version 7 or BSD versions. not me finding out the old-school drama 😭.

The set_max_field function checks for an ncurses extension O_INPUT_FIELD which allows a dynamic field to shrink if the new limit is smaller than the current field size. slay for shrinking fields, I guess. ✨

πŸ‘‘ AUTHORS πŸ‘‘

Juergen Pfeifer. Manual pages and adaptation for new curses by Eric S. Raymond. iconic. πŸ’–

🧚 SEE ALSO 🧚

curses(3X) and related pages whose names begin β€œform_” for detailed descriptions of the entry points. go read the form_ girlies, iykyk. πŸ¦‹


later, bestie β€” this ncurses 6.5 page is dated 2024-12-28. πŸ’–πŸ¦‹

πŸ“¦ where this page comes from