Dear all,
I wonder where I can get the dataset/log of this toggle callback graph:
I want to improve the performance of my app so knowing the timing of each task would be a way to do so.
Cheers!
I want to improve the performance of my app so knowing the timing of each task would be a way to do so.
Hi, I know that @jcuypers dedicated some time to extract information from this.
Hi, these graphs are constructed based on information that is extracted from an (internal) redux store (you can see the structure, by using a redux debugger in your browser) As far as I know, there is currently no extraction possible through CSV or other. There was an idea for a feature with table-like event representation but this was like sided since the basics of the basics with a pop-out window doesn’t work as expected .
For your use cases, even if export would be possible in some ways, I would rather revert to custom timings on callback. In this way, you could log granular performance data per subtask instead of just callback info. But still no export all option as a file.
Maybe there is a way you can save the redux logs (as it has playback logs) itself from the browser and get something useful… But I’m afraid it’s quite obscure.
1 Like
Many thanks for the info, jcuypers! Indeed, I should focus on my app code, rather than what play with this (unknown) data.
Actually, I could extract the real-time timing and action right from console using another callback function. Here is an initial result to share with you.
What I want is every time I click the mouse, I will get a table like that.
The current trouble is how I can know if the mouse has been clicked. Still no answer yet!
Cheers,
1 Like
Hi, looks nice. what about a client side callback detecting mouse clicks? Not sure how the propagation would work. It should also have the context functionality available if you need it.
Regards,
J.
I haven’t looked up Clientside callback so I have no clue.
The way I separate the time windows (see screenshot) is really dependent on which callback triggers first (or last).
It can be solved if I can decide “my callback” to fire last.
“My callback” is the one to call the function to show the table below. This is exactly the current issue as far as I know triggering callbacks can runs pretty randomly. So if “my callback” to fire somwhere in the middle of entire callback chains after 1 click, it will stop before the last callback triggers.
