Bug 86074 - Cursor stays 'On' after a newtEntry is processed.
Cursor stays 'On' after a newtEntry is processed.
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: newt (Show other bugs)
rawhide
All Linux
medium Severity low
: ---
: ---
Assigned To: Miroslav Lichvar
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-13 11:29 EST by Olivier Baudron
Modified: 2015-01-07 19:04 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-06-08 11:59:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Olivier Baudron 2003-03-13 11:29:42 EST
To reproduce the bug:

1. Run a form with a newtEntry inside.
2. Select the entry, type some text, then return.
3. The cursor is now visible when switching between
   the various components of the form.

A testcase follows:

/* ------------ test.c --------------- */
#include <stdlib.h>
#include <newt.h>

int main (int argc, char **argv) {
    const char *res;
    newtComponent form_1, form_2, button, entry;

    newtInit();
    newtCls();

    newtCenteredWindow (40, 10, "Test");
    form_1 = newtForm (NULL, NULL, 0);
    button = newtButton (17, 5, "Ok");
    newtFormAddComponents (form_1, button, NULL);
    newtRunForm (form_1);

    entry = newtEntry (15, 2, "", 10, &res, NEWT_FLAG_RETURNEXIT);
    form_2 = newtForm (NULL, NULL, 0);
    newtFormAddComponents (form_2, entry);
    newtRunForm (form_2);
    newtFormDestroy (form_2);

    newtRunForm (form_1);
    newtFormDestroy (form_1);

    newtFinished();
    return 0;
}
/* ----------------------------------- */

$ gcc -Wall -o test test.c -lnewt
$ ./test

Press 'Return'.
Type some text then 'Return'.
The cursor is now visible (near the button).
Comment 1 Miroslav Lichvar 2006-06-08 11:59:44 EDT
Fixed in newt-0.52.2-7.

Note You need to log in before you can comment on or make changes to this bug.