[wuuemmParticipant]

When grid is an jqxGrid element and data is an item

$.each(source._source.datafields, function (i, e) {
    if (e.type === 'date') {
      data[e.name] = source.formatDate(new Date(data[e.name]), 'dd/MM/yyyy HH:mm');
    }
  });
grid.jqxGrid('updaterow', id, data);

This works. Why not include this in the library?
The date format is arbitral here, should get info from grid columns definition in general solution.
The date format coming from server is a timestamp (number).

[wuuemmParticipant]

When grid is an jqxGrid element and data is an item

$.each(source._source.datafields, function (i, e) {
    if (e.type === 'date') {
      data[e.name] = source.formatDate(new Date(data[e.name]), 'dd/MM/yyyy HH:mm');
    }
  });
grid.jqxGrid('updaterow', id, data);

This works. Why not include this in the library?
The date format is arbitral here, should get info from grid columns definition in general solution.
The date format coming from server is a timestamp (number).

[wuuemmParticipant]

This won’t work on row update. At least I don’t know how to implement. If I once define the date format for a column and it works on initial data binding, I want all subsequent row updates (same item data format from server) to be formatted as defined while a grid was created, without any extra code. You’ve provided properties for formatting when data is initially bound but forgot to apply them when a single row/item is updated.

[wuuemmParticipant]

Nonsense, Peter, sorry, it sucks. If I once define the date format for a column and it works on initial data binding, I want all subsequent row updates (same item data format from server) to be formatted as defined while a grid was created. The argument “the method is called by the developer” is ridiculous, as all methods are called by developers. You’ve provided properties for formatting when data is initially bound but forgot to apply them when a single row/item is updated. This is the point.

[wuuemmParticipant]

Can’t see such a component. Hard to develop within 4 years?

[wuuemmParticipant]

With the same settings showWeekends: false in view, firstDay: 1 in localization, monthView shows me all days but Saturday (v.8.0.0), i.e. I get six columns with a gap between Friday and Sunday.

My current (rather obvious) workaround is to come back with firstDay setting (set it to default 0). It does not matter whether Sunday is first or last as long as I don’t want to see this day by purpose.

[wuuemmParticipant]

disabled: true is fine, but needs modifying CSS. What HTML readonly property was invented for, was to prevent input only, without affecting neither ability to use in form posts nor the styling (the former purpose doesn’t matter here as JQWidgets disabled fields can be also easily read). So the look is an issue.

Your implementation does something else (what exactly, is a good question) making it hardly useful.

[wuuemmParticipant]

Use case:

1. Enter your own jseditor: https://jseditor.io/?key=scheduler-edit-dialog-
2. Right-click on a cell, then click on “Create New Appointment”
3. Fill in fields labelled “Title” and “Where”
4. Click on either calendar icon in fields “Start”, “End” or on either DropDownLists “Repeat”, “Calendar”

Effect – the content of top 2 fields is gone. Not expected behaviour, I suppose.

[wuuemmParticipant]

What if I update the same way I feed the row with the initial data, i.e. as a timestamp number? It’d be crazy to change the server feed format (i.e. item definition) depending on whether I’am creating a grid or updating one of its rows.

[wuuemmParticipant]

In ver. 8.0.0 this seems to be fixed only partly. Everything works as expected while editing an existing appointment.
If, however a fresh appointment is being created (“Create New Appointment”) there are still two critical issues:

1. Opening any popup (in result of a click on either jqxDateTimeInput or any jqxDropDownList) results in clearing values in almost all other fields.
2. Hiding fields.repeatContainer in editDialogCreate handler is ignored on subsequent dialog opening (while editing existing appointment).

I don’t attach or link to any user cases as your own fiddle samples show the same bugs in action.

Those issues should be fixed as soon as possible as they make the whole widget entirely useless.

[Author]

Posts