Premium support for our pure JavaScript UI components


Post by symas »

Hi

When I try to use the Feature "NestedEvents", I get the log-message

Feature 'nestedEvents' not available, make sure you have imported it.

I have enabled it like

[features]="scheduler2Config.features"

and this is my config for features:

     features: {
        nestedEvents : true,
         filter: true,
         eventEdit: {
             readOnly: true,
             items: {
                 blubb: {
                     type: 'textarea',
                     label: 'Blubb',
                     name: 'blubbfield'
                 }
             }
         }
     }
     

Do I need to do anything extra? I can't find anything else in the documentation.
https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/feature/NestedEvents

Thanks for your help.
Best Regards
Thomas


Post by tasnim »

Hello,
When you want to use a feature in Angular you need to have a suffix after the feature name that is 'Feature' (in the markup)
for example :

<bryntum-scheduler-pro
	[nestedEventsFeature] = "scheduler2Config.features.nestedEvents"
	[taskEditFeature] = "..."
	....
</bryntum-scheduler-pro>

Please checkout this guide https://bryntum.com/products/schedulerpro/docs/guide/SchedulerPro/integration/angular/guide#features


Post by symas »

Hi Tasnim

Thanks for your reply. When I do this, I get the error

Can't bind to 'nestedEventsFeature' since it isn't a known property of 'bryntum-scheduler'

Can you help me about this?

Best Regards
Thomas


Post by tasnim »

Hey Thomas,

Are you using bryntum-scheduler or bryntum-scheduler-pro.
Nested events are not supported in bryntum-scheduler but in bryntum-scheduler-pro


Post by symas »

Hi Tasnim

I use bryntum-scheduler-pro

import { BryntumSchedulerComponent } from '@bryntum/schedulerpro-angular';

Post by tasnim »

You should import BryntumSchedulerProComponent instead of BryntumSchedulerComponent

import { BryntumSchedulerProComponent } from '@bryntum/schedulerpro-angular';

Post by symas »

Hi Tasnim

Thank you. This was a mistake in my migration. I had started with bryntum-scheduler and then migrated to bryntum-scheduler-pro and didn't change this.

Now, I haven't any error. But I have tried to make some nested events like this:

     events: [
        {
            id: `1000_0`,
            resourceId: 1000,
            name              : 'Manually scheduled',
            startDate         : '2022-11-29',
            duration          : 5,
            manuallyScheduled : true,
            children          : [
                { id : `1000_0_0`, name : 'Start here?', startDate : '2022-11-29', duration : 2, resourceId: 1000, },
                { id : `1000_0_1`, name : 'End here?', startDate : '2022-12-03', duration : 2, eventColor : 'orange', resourceId: 1000,  }
            ]
        },
        {
            id: `1000_1`,
            resourceId: 1000,
            name              : 'Manually scheduled',
            startDate         : '2022-11-29',
            duration          : 5,
            manuallyScheduled : true,
            children          : [
                { id : `1000_1_0`, name : 'Start here?', startDate : '2022-11-29', duration : 2, resourceId: 1000, },
                { id : `1000_1_1`, name : 'End here?', startDate : '2022-12-03', duration : 2, eventColor : 'orange', resourceId: 1000,  }
            ]
        }
     ]

But the events are not shown.

When i didn't use nestsed events, the events are shown:

01-12-2022_16-15-54.png
01-12-2022_16-15-54.png (15.62 KiB) Viewed 606 times

Can you help me one more time, what I am doing wrong?


Post by tasnim »

You should not use resourceId, You should use assignments instead.

Please check this doc https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/feature/NestedEvents and compare with the live demo how the data is structured


Post Reply