Eclipse Community Forums: NatTable » Problem using DateCellEditor

Home » Eclipse Projects » NatTable » Problem using DateCellEditor(DateCellEditor sets the cell value to null)

Problem using DateCellEditor [message #1701736]

Wed, 15 July 2015 05:52

Eclipse User

Hi,
I am trying to show a date editor in one of the columns in my NAT UI.

I have included the following in my code :
configRegistry.registerConfigAttribute(EditConfigAttributes.CELL_EDITOR,
new DateCellEditor(),DisplayMode.EDIT, DATE_LABEL);

On clicking that particular cell, i get a calendar instance to choose a date from.
I can easily choose different dates from it. But the moment i shift to any other cell, the date cell value becomes empty.

i have a check in setDataValue() :
if (userValue == null)
super.setDataValue(columnIndex, rowIndex, "");
else
super.setDataValue(columnIndex, rowIndex, userValue.toString());

I am not sure why the userValue is null always in this case.
Am i missing anything here?
Attached are 2 screenshots for the same.

How can i set this selected date in the date column?

Attachment: Snapshot2.PNG
(Size: 2.10KB, Downloaded 250 times)
Attachment: Snapshot1.PNG
(Size: 8.61KB, Downloaded 251 times)

Re: Problem using DateCellEditor [message #1701745 is a reply to message #1701736]

Wed, 15 July 2015 07:04

Eclipse User

What do you mean with "i have a check in setDataValue()"?

I typically would say that you need to ensure a correct data type. The DateCellEditor needs a Date conversion to work correctly. So you need a DefaultDateDisplayConverter.

Re: Problem using DateCellEditor [message #1701832 is a reply to message #1701745]

Thu, 16 July 2015 02:06

Eclipse User

Hello Dirk,

I am already using a DefaultDateDisplayConverter.

configRegistry.registerConfigAttribute(CellConfigAttributes.DISPLAY_CONVERTER,
new DefaultDateDisplayConverter(),DisplayMode.NORMAL,
DATE_LABEL);

configRegistry.registerConfigAttribute(CellConfigAttributes.DISPLAY_CONVERTER,
new DefaultDateDisplayConverter(),DisplayMode.EDIT,
DATE_LABEL);

But it displays message : Cannot format given Object as a Date at org.eclipse.nebula.widgets.nattable.data.convert.DefaultDateDisplayConverter canonicalToDisplayValue.

if i double click a particular cell to edit and enter nothing , the pointer gets stuck in that cell when i try to shift to another cell. For this I am overriding the setDataValue to check for blank data
if (userEnteredValue == null)
super.setDataValue(columnIndex, rowIndex, "");
else
super.setDataValue(columnIndex, rowIndex, userEnteredValue.toString());

I am not sure what is missing.
On digging more into the code, i see that null value is passed as date to DateCellEditor , I don't know why. As on the UI , I am able to see the selected date.

Re: Problem using DateCellEditor [message #1701834 is a reply to message #1701832]

Thu, 16 July 2015 02:34

Eclipse User

Quote:

Cannot format given Object as a Date at org.eclipse.nebula.widgets.nattable.data.convert.DefaultDateDisplayConverter

Well, that message says everything. The object in your data model is not a Date.

And where did you override setDataValue()? DataLayer? IDataProvider? It looks like you are setting a String. So is the value in your data model a String? Why should that work in conjunction with Dates?

Re: Problem using DateCellEditor [message #1701839 is a reply to message #1701834]

Thu, 16 July 2015 03:10

Eclipse User

Hello,

I am overriding the setDataValue() in bodyDataLayer. I am setting string values for rest of the columns
For this particular date column, my setDataValue() has something like this:

if(columnIndex== <<dateColumnIndex>>)
{
Object cal = cellEditor.getEditorValue();
super.setDataValue(columnIndex, rowIndex, cal );
}
else if (userEnteredValue == null)
super.setDataValue(columnIndex, rowIndex, "");
else
super.setDataValue(columnIndex, rowIndex, userEnteredValue.toString());

-Roma Lahoti

Re: Problem using DateCellEditor [message #1701840 is a reply to message #1701839]

Thu, 16 July 2015 03:15

Eclipse User

Sigh ... for such things converters should be used. But if you like it more to override internal methods to achieve behavior that can be configured, go ahead and loose the ability to update and get bugfixes and new features in the future.

I really don't understand why most of the cases reported here in the forum use overriding in favor of configuration.

Previous Topic:	NatTable in Eclipse RAP with RAPe4 Incubator
Next Topic:	Installation Error

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jun 12 22:08:44 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter