This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 94152 - RFE from Customer - would like a user friendly dialog for dateTimeConverter
Summary: RFE from Customer - would like a user friendly dialog for dateTimeConverter
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Gregory Murphy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-02 22:03 UTC by bugbridge
Modified: 2007-02-02 22:03 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2007-02-02 22:03:53 UTC
Description:
DESCRIPTION OF PROBLEM
--------------------------------
It would improve the usability of this component if it works like the
numberConverter component after you drop the component on another component a
dialogue box pops up and prompts you to enter pattern data.  With the
dateTimeConverter you need to get into the properties
sheet and enter a pattern with no pre-derfined patterns to select from.  It
would be nice if all converter components have the same behavior of prompting
you with a dialogue window with a dropDownList with pattern possibilities for
date time formats.
ERROR MESSAGES
----------------------
None.
STEPS TO DUPLICATE
-------------------------
Just compare the different behavior between numberConverter and
dateTimeConverter components.

WORKAROUNDS
-------------------
Fish around in documentation for date time patterns.

Description (Entry 2):
Here's an example using numberConverter:

1) Drop a static text
2) Drop a Number converter
- a nice dialog to set properties opens.

vs. a dateTime Converter
1) Drop a static text
2) Drop a dateTimeConverter
- no dialog opens, property sheet reset to show the dateTimeConverter properties

Workaround:

        Any workaround found by the tester is in the Description field.