SetAxis operates at the end of procedure?

Share icon

Fri, 03/03/2017 - 08:05 am

Hi Forum!!

I am writing a procedure for which I plot some data.

it goes something like:

// THERE IS SOME CODE ABOVE

    //Plot Original Dataset
    Display /K=1 /W=(0, 180, 320, 450) /N=OriginalPlot Original_Y vs Original_T
    SetAxis /W=OriginalPlot /a=2 bottom 700, 1200

    //Convert frame number to timepoints
    Prompt FPS, "Frames per second: "
    DoPrompt "Please indicate the frame rate at which the data was collected", FPS;
        if (V_flag)
            return -1
        endif  
   
    Duplicate /O Original_T, Original_Time
    Original_Time /= FPS
    AppendToTable /W=Data Original_Time

// THERE IS SOME CODE BELOW


So, there is a  DoPrompt after the  display and  SetAxis operations.
My problem is that  SetAxis only kicks in at the end of the procedure. Why does it not updates the graph before the  DoPrompt ? Not sure why this happens.
I have no  DelayUpdate operations written anywhere and still this happens.
No flags in SetAxis that could induce this.

Any ideas on how to update the graph before  DoPrompt?

Many thnaks!!

R.
During execution of user functions, for the most part re-drawing the screen is suppressed because it is slow. But some aspects of a graph are not updated until it has been drawn, including the effects of a call to SetAxis. That's why you need to call DoUpdate to have it take effect.

John Weeks
WaveMetrics, Inc.
support@wavemetrics.com

March 7, 2017 at 09:49 am - Permalink