After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 315988 - new GtkEntry Inputmask ability
new GtkEntry Inputmask ability
Status: RESOLVED DUPLICATE of bug 50276
Product: gtk+
Classification: Platform
Component: Widget: GtkComboBox
unspecified
Other other
: Normal enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2005-09-11 13:17 UTC by JoseAntonio S.A.
Modified: 2005-09-11 16:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description JoseAntonio S.A. 2005-09-11 13:17:59 UTC
Distribution: Debian testing/unstable
Package: gtk+
Severity: enhancement
Version: GNOME2.10.2 unspecified
Gnome-Distributor: Debian
Synopsis: new GtkEntry Inputmask ability 
Bugzilla-Product: gtk+
Bugzilla-Component: combobox
Bugzilla-Version: unspecified
Description:
Please describe your feature request:
This describes exactly what i wish:
http://bugs.async.com.br/show_bug.cgi?id=438

"It would be interesting if a subclass of GtkEntry could be provided
that did
automatic validation of the text inserted in it. For instance, a field
that
allowed entry only of numbers, or letters.

A bonus would be the provision of an input mask, which would provide
static
markers that could be filled in normally: "__/__/____" for a date, for
instance." or  _ _  - _ _ _ _ _ _ _ _ _   for phone number, etc.

Thanks!




------- Bug moved to this database by unknown@gnome.bugs 2005-09-11 13:17 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was jose.antonio.sa@gmail.com.

Comment 1 JoseAntonio S.A. 2005-09-11 14:41:36 UTC
component is GtkEntry, not Combobox, sorry for the mistake.
Comment 2 Owen Taylor 2005-09-11 16:39:03 UTC

*** This bug has been marked as a duplicate of 50276 ***