Search found 2354 matches

by Maxim Gorkovsky
Thu Nov 14, 2019 12:05 pm
Forum: Bryntum Gantt
Topic: PDF export for Gantt
Replies: 6
Views: 144

Re: PDF export for Gantt

Hello.
We are working on this feature at the moment. Likely first version will be finished next week.
by Maxim Gorkovsky
Fri Oct 18, 2019 5:40 pm
Forum: Bryntum Gantt
Topic: Custom DependencyModel not mapping fields
Replies: 4
Views: 108

Re: Custom DependencyModel not mapping fields

Hello. I can reproduce this problem. Here is a ticket: https://app.assembla.com/spaces/bryntum/tickets/9393-impossible-to-override-dependency-fields-in-gantt/details Thank you for report! I also noted that doc is a bit outdated. So far it appears the only way to define working dependency via the dat...
by Maxim Gorkovsky
Fri Oct 18, 2019 5:18 pm
Forum: Bryntum Gantt
Topic: Custom Dependency Tooltip
Replies: 2
Views: 59

Re: Custom Dependency Tooltip

Hello. I see how it can be difficult to customize the tooltip. I opened a ticket to adopt more friendly approach: https://app.assembla.com/spaces/bryntum/tickets/9392-make-dependency-tooltip-as-customizable-as-tasktooltip/details I see several solutions so far: 1. Read tooltip doc , provide config w...
by Maxim Gorkovsky
Fri Oct 18, 2019 4:58 pm
Forum: Bryntum Gantt
Topic: Usage of field property inside columns configuration - problem with name column
Replies: 11
Views: 281

Re: Usage of field property inside columns configuration - problem with name column

As far as I see mapping works fine with other fields, only name is troubled for some reason. Speaking of mapping fields you can read more in the doc . Long story short: fields are transformed to the accessors (get/set) with corresponding name and they read/write data according to the mapping. So whe...
by Maxim Gorkovsky
Fri Oct 18, 2019 4:32 pm
Forum: Bryntum Grid
Topic: Keyboard binding for delete row
Replies: 1
Views: 101

Re: Keyboard binding for delete row

Hello.
You can listen to keydown event:

Code: Select all

EventHelper.on({
    element : grid.element,
    keydown : event => {
        if (event.key === 'Delete') {
            grid.selectedRecord.remove();
        }
    }
});
Also I'd check that event target is a cell inside the grid.
by Maxim Gorkovsky
Fri Oct 18, 2019 4:19 pm
Forum: Bryntum Grid
Topic: Modifying dropdown cells from other dropdown cells
Replies: 6
Views: 78

Re: Modifying dropdown cells from other dropdown cells

In general it is not a good idea to use undocumented features as they are subject to change. You can try navigating up from the combo to the grid and read record from store.

Code: Select all

this.up('grid').store.getById(id)
by Maxim Gorkovsky
Fri Oct 18, 2019 4:09 pm
Forum: Bryntum Gantt
Topic: Task Editor
Replies: 16
Views: 296

Re: Task Editor

I can see this problem in our advanced demo. In fact, after load you would see changes in the task store immediately. I opened ticket about this: https://app.assembla.com/spaces/bryntum/tickets/9390-task-store-in-angular-advanced-demo-has-changes-after-load/details Workarond would be to commit store...
by Maxim Gorkovsky
Fri Oct 18, 2019 2:40 pm
Forum: Bryntum Gantt
Topic: Usage of field property inside columns configuration - problem with name column
Replies: 11
Views: 281

Re: Usage of field property inside columns configuration - problem with name column

My bad, I confused different name fields. I can see this problem in our advanced demo too, I opened a ticket: https://app.assembla.com/spaces/bryntum/tickets/9389-cannot-set-datasource-to-name-field-in-task-model/details Thank you for report! Also overriding Id field should be like this: class MyTas...
by Maxim Gorkovsky
Fri Oct 18, 2019 12:03 pm
Forum: Bryntum Gantt
Topic: Usage of field property inside columns configuration - problem with name column
Replies: 11
Views: 281

Re: Usage of field property inside columns configuration - problem with name column

Because in the data set which you use there's no `Name` fields, only `name`. Update key and it will be picked up.

Please do not include our sources to the test case, we only need to know version (1.1.5 in this case)