gnats/301: No way to get at allow-any-value field flag

gnats/301: No way to get at allow-any-value field flag

[yngve.svendsen]

>Number:         301
>Category:       gnats
>Synopsis:       No way to get at allow-any-value field flag
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Nov 19 17:52:53 -0500 2001
>Originator:     yngve.svendsen@clustra.com (Yngve Svendsen)
>Release:        4.0
>Organization:

>Environment:

>Description:
There is currently no way to find out through the gnatsd command set whether a field has the allow-any-value flag set.
>How-To-Repeat:

>Fix:
Add support for a property named something like 'allow-any-value' in the FTYPINFO command
>Unformatted:
 

_______________________________________________
Gnats-prs mailing list
Gnats-prs@gnu.org
http://mail.gnu.org/mailman/listinfo/gnats-prs

Re: gnats/301: No way to get at allow-any-value field flag

[Milan Zamazal]

>>>>> "ys" == yngve svendsen <yngve.svendsen@clustra.com> writes:

    ys> There is currently no way to find out through the gnatsd command
    ys> set whether a field has the allow-any-value flag set.

How about FIELDFLAGS?

  fieldflags responsible
  350 textsearch allowAnyValue requireChangeReason 

  fieldflags priority
  350 textsearch

Regards,

Milan Zamazal

-- 
The rush to reproduce Microsofts window environment seems to overshadow the
design process of determining what a window environment should be, and what its
ultimate users will want.                  -- Barry Fishman in gnu.misc.discuss

_______________________________________________
Gnats-prs mailing list
Gnats-prs@gnu.org
http://mail.gnu.org/mailman/listinfo/gnats-prs

Re: gnats/301: No way to get at allow-any-value field flag

[Yngve Svendsen]

At 22:06 03.12.2001 +0100, Milan Zamazal wrote:
> >>>>> "ys" == yngve svendsen <yngve.svendsen@clustra.com> writes:
>
>     ys> There is currently no way to find out through the gnatsd command
>     ys> set whether a field has the allow-any-value flag set.
>
>How about FIELDFLAGS?
>
>   fieldflags responsible
>   350 textsearch allowAnyValue requireChangeReason
>
>   fieldflags priority
>   350 textsearch

Sigh. Seems there's no longer any excuse not to implement support for 
allow-any-value in Gnatsweb.

Thanks for clearing this up -- I thought I'd tested fieldflags, but it must 
have slipped my mind. This is the last feature holding up the final beta of 
Gnatsweb 4, and I hope I'll get around to adding it this week.

- Yngve


_______________________________________________
Gnats-prs mailing list
Gnats-prs@gnu.org
http://mail.gnu.org/mailman/listinfo/gnats-prs