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
These two windows are graphed with potentially different X axes. The flowview window can graph by timestamp (like the graph window does) or by frame number. But, even when it graphs by timestamp it does so without biasing the timestamp to start at 0 like the graph window does. The graph window has an automatic bias to start at X=0 because it's easiest to set up graphs this way. But, because of this discrepancy, it is extremely difficult to look at data in both windows and be looking at the same point in time.
There are a few options here.
The flowview window could bias to start at 0 on the X axis as well. It currently doesn't do that because it is trying to match timestamps to the main frame list.
The graph window could quit biasing to 0. This might be the best option because then it will match the timestamps in flowview and on the main frame list. That synchronizes everything. It is currently possible to cause the main list to bias to start at 0 time so that button can be used to make all of the windows start from 0 time on the X axis.
Also, it might be possible to cause a click on the graph in either flowview or graphing window to update the other so that the view is centered on the same X position / timestamp.
The text was updated successfully, but these errors were encountered:
These two windows are graphed with potentially different X axes. The flowview window can graph by timestamp (like the graph window does) or by frame number. But, even when it graphs by timestamp it does so without biasing the timestamp to start at 0 like the graph window does. The graph window has an automatic bias to start at X=0 because it's easiest to set up graphs this way. But, because of this discrepancy, it is extremely difficult to look at data in both windows and be looking at the same point in time.
There are a few options here.
The flowview window could bias to start at 0 on the X axis as well. It currently doesn't do that because it is trying to match timestamps to the main frame list.
The graph window could quit biasing to 0. This might be the best option because then it will match the timestamps in flowview and on the main frame list. That synchronizes everything. It is currently possible to cause the main list to bias to start at 0 time so that button can be used to make all of the windows start from 0 time on the X axis.
Also, it might be possible to cause a click on the graph in either flowview or graphing window to update the other so that the view is centered on the same X position / timestamp.
The text was updated successfully, but these errors were encountered: