Support Forum
Search found 2087 matches
Generally, the "ghost task" is just an HTML element you create and destroy as needed, that you would move with mouse moves and that which will react to mouse clicks. Crosshair cursor is easily achievable with css ( cursor: crosshair ) that will be applied or removed when needed. On click y...
Combination of autoHeight and React component renderer is currently not supported. The existing logic for non-react content is that each cell is rendered in the background, its height is measured and then it is set on the row. For React renderer it would be necessary to create and render all necessa...
The javascript version uses javascript techniques, ignoring the limitations that would be present for typescript, for example defining a custom properties for classes that are not in typings. Although it would be possible to convert (you can try to change the extension to .ts) still it would be stre...
To explain: ganttToolbar.ts is a leftover that should have been deleted and it is not used by the demo. The easiest way how to use the toolbar the advanced demo uses is the same way as it is used by the demo and how @tasnim explains above. Even if you had an Angular component that would encapsulate ...
Try to remove type: 'name' from your column config.
columns is a config option what means that it cannot be changed at runtime. There is also a columns property but it is read-only. Screenshot 2023-11-29 at 11.19.21.png That means that although it apparently works because the columns are always re-created at React re-renders, it is not a sustainable...
Also, we have a big dataset example that uses React renderers. Do you hit performance problems also at https://bryntum.com/products/scheduler/examples/frameworks/react-vite/bigdataset/dist/ ? If not, then what is different between your implementation and the demo?
I'm curious though if you know what changed between these versions, to avoid this in the future. Yes, we do know what has changed. We have fixed this bug: https://github.com/bryntum/support/issues/7861 All our products run through extensive testing so we also added the specific test for this issue....
The problem here is that your code tries to change the value of tbar during the React re-renders. Although tbar is both config option and property, it is a read-only property. https://bryntum.com/products/calendar/docs/api/Calendar/view/Calendar#property-tbar Screenshot 2023-11-27 at 11.55.23.png Th...
I also tried to run the demo app but I couldn't make it working. I removed node_modules and yarn.lock , and tried npm i which failed. I have also tried yarn and it fails as well. Could you please post a simplest possible showcase without node_modules that we could run with npm i and npm run dev ?