Search found 2328 matches

@pfund This issue is caused by the way of how the ALAP status is propagated in the dataset. Currently, it is propagated down to all successors of the ALAP task. In your dataset, Task21 is set as ALAP and that propagates the ALAP status downstream to all successors, among which are the tasks 33 and 3...

@dominicdolan What version of our component do you use? IIRC we've fixed this issue recently, please try to reproduce with the latest code?

Ah, reproduced now, thanks for the clarifications. We'll be fixing it soon.

@lucacervo98 Hi, this issue does not seem to be reproducible? (see the video I posted in the ticket)

The exception says - some asynchronous calculation was attempted to be performed in the synchronous context. This is usually a bug, to tell more I need to be able to reproduce this, please provide a test case if possible.

@lanpeng Hi, it seems this issue has been already fixed - see the video I've uploaded into the ticket. Please try reproducing it with the latest version of our code and let me know?

Hi,

You can provide a startDate : new Date() config for the scheduler during instantiation. This will disable the calculation of earliest date and match the old behavior for the case when no startDate config was provided.

@vladip Hi, the 2nd issue you reported has been resolved, the fix will be available in the next release and in the tomorrow nightly.

I'll be checking the 1st issue now.

The multiSelect config of the AssignmentField (which is inherited from the combo box) is not applicable in this case. AssignmentField does not render a list items, like combo box. Instead, it completely replaces the combo's picker with the custom widget - AssignmentPicker which is a grid. So using m...