Using the latest dhtmlxScheduler (2.3) and dhtmlxChart (3.0), if dhtmlxScheduler is loaded after dhtmlxChart it will completely break dhtmlxChart:
- dhtmlChart checks if window.dhtmlx exists, if it does not it creates a simple object via window.dhtmlx = {};
- dhtmlxScheduler seems to rely on older (?) APIs, instead of adding functions on dhtmlx ns, it unconditionally sets dhtmlx to a function to which it adds only an (apparently unused) dhtmlx.extend_api function (which does not exist in dhtmlxchart for what it’s worth
As a result, all the functions dhtmlxchart adds to the dhtmlx namespaces are removed/destroyed, which breaks dhtmlxchart (dhtmlXChart constructor uses a number of functions from the dhtmlx namespace).
This issue seems to solve itself if I simply replace the dhtmlx-setting in common and scheduler by the same call sequence as that in dhtmlxChart (conditionally assigning an object to window.dhtmlx).
Does that seem like the correct solution, or is it likely to pose further issues later on?