The plot on 1st stroke path gets automatically closed(i,e joins start & end points) even though I'm not using Close() API at the same time the other stroke path disappears .
Is it possible that the last coordinate pair does match the start coordinates? Generally there should not be any automatic Close() operation. I think there is something wrong with the coordinates you provide when the cycle is completed.
Since your application case is to plot a continues path, the following section can be useful for you: Evaluate and modify the coordinates stored in the Path Data object. Note the usage of the there described ShiftNodes() method when the path is full. The method removes the oldest value from the path object and shifts the entire content (the coordinates) of the path by given pixel offset. Then you can again append a new value. In this manner the path can continuously display new data.
Also some times the both the plots are disappeared.
Do you observe the behavior in the target system? If yes, check the console outputs. I suppose, there are too many data entries in the path to fit within the so called issue buffer. If this is the case, you will need to increase the configuration EW_MAX_ISSUE_TASKS in your Build Environment. See also: Optimizing the Data Memory (RAM) usage.
... with values beginning from 60-100 on X axis ...
I do not really understand the above case. However, for special scaling you have always the possibility to calculate the values in advance before feeding them into the path. You don't depend on the Scale() method.
how can we implement Auto Scaling such that if a the values exceeds the current scale it should upscale it
Similar is true for the 'auto-scaling'. You have to evaluate the range of all available values and knowing it calculate from this range the appropriate scaling factors. The consequence: when the scaling factors change, you have to reload the path data with new (scaled) values. For this purpose you will need to store a copy of the data without any scaling and use it in your evaluation. The path stores only the already scaled data. The path data object does not implement any auto-scaling functionality. Its a detail of your implementation.
What might be the issue
Have you checked the console outputs for evtl. error messages? Possibly, the issue buffer is too small for the path data. See also my first answer above.
Ask Embedded Wizard
Welcome to the question and answer site for Embedded Wizard users and UI developers.
Ask your question and receive answers from the Embedded Wizard support team or from other members of the community!