[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bug / inconsequent handling of field_status for fields not marked O_
From: |
Thomas Dickey |
Subject: |
Re: bug / inconsequent handling of field_status for fields not marked O_EDIT |
Date: |
Sat, 1 Oct 2005 17:47:58 -0400 |
User-agent: |
Mutt/1.5.9i |
On Mon, Sep 05, 2005 at 01:24:36PM +0200, Frank van Vugt wrote:
> Hi,
>
> When one enters a field not marked as O_EDIT and the form driver
> receives/processes a regular key for it, then it's status is not changed
> (field_status() returns false).
>
> However, pressing <arrow_right> before entering a regular key WILL mark the
> field as dirty (field_status() returns true), though obviously it's contents
> won't change.
I made some changes to demo_forms to investigate this, but don't see this
behavior. If you have a simple test program for comparison, that might be
helpful (or you could look at demo_forms and see why I'm not testing it
properly ;-).
For demo_forms (today I added) -t option to initialize the fields, and
use ^T to toggle each to readonly (O_EDIT not marked). Then traversing
with ^N and trying a right-arrow followed by any text only gets a beep
and no change in status (it would show "modified" in the block at the
bottom of the screen). Note that I'm calling set_field_status() when
the O_EDIT flag is first turned off, to ensure that field_status() would
only be returning changes after that point.
--
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net
signature.asc
Description: Digital signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: bug / inconsequent handling of field_status for fields not marked O_EDIT,
Thomas Dickey <=