You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This qlik extension seems very good to me, hence why I would like to work with it.
My problem though is that I want to make a gantt chart of different processes which are very detailed.
The frames of these processes should be measured in seconds.
I can't see a way at this moment to make that work in qlik with this extension, while I am able to make it work in JavaScript using the standard Google chartloader.
In the google chartloader I can just give a duration in milliseconds without having to give any specific dates which is perfect in my case.
Maybe this is an upgrade worth making, since the most detailed the timeline can go at the moment is days.
Kind regards
Troy
The text was updated successfully, but these errors were encountered:
When I created the qlik-sense-timeline chart I was working for Qlik. I have since changed companies and unfortunately no longer have access to a copy of Qlik Sense to test any changes with.
Please feel free to fork this repository and if you find a way of achieving what you are attempting you can open a pull request for me to apply the changes back to this master copy?
Hello
This qlik extension seems very good to me, hence why I would like to work with it.
My problem though is that I want to make a gantt chart of different processes which are very detailed.
The frames of these processes should be measured in seconds.
I can't see a way at this moment to make that work in qlik with this extension, while I am able to make it work in JavaScript using the standard Google chartloader.
In the google chartloader I can just give a duration in milliseconds without having to give any specific dates which is perfect in my case.
Maybe this is an upgrade worth making, since the most detailed the timeline can go at the moment is days.
Kind regards
Troy
The text was updated successfully, but these errors were encountered: