02-28-2007 12:34 AM
02-28-2007 07:41 AM
In the event my suggestions fail you, please post your code so we can look closer.
1) Check the sequencing of the operations performed on the graph to make sure that data dependacy dicatates the cursor actions occur before you get the image.
2) You did not mention how you are getting the image. Invoke node >>> Get image has been very effective in getting LV to update the image of objects.
3) Post LV 6.1 (?) the "Defer FP Updates" will force a screen update when set true AND false.
Like I said, if you want a good answer, post some code.
Ben
02-28-2007 05:53 PM
02-28-2007 06:06 PM
I cannot reporduce your problem, but still...
Also try this:
right-click on your graph and select "advanced...synchronous display".
02-28-2007 06:42 PM - edited 02-28-2007 06:42 PM
Message Edited by sadeghi on 02-28-2007 06:45 PM
02-28-2007 07:50 PM - edited 02-28-2007 07:50 PM
Message Edited by altenbach on 02-28-2007 05:52 PM
02-28-2007 07:51 PM - edited 02-28-2007 07:51 PM
Message Edited by Ben on 02-28-2007 07:52 PM
Message Edited by Ben on 02-28-2007 07:54 PM
02-28-2007 07:53 PM
02-28-2007 09:03 PM
Many thanks for your suggestions. I had tried sequencing the graph by sending the data wire to the for loop where cursor positions are determined and adding a 0.5s delay before the image export, but they didn't help, so I took them out. It seems like my problem is particular to my system, so I'll try looking at it later.
By the way would passing the graph wire to the loop always make sure the graph is updated before the operation in the loop take place or is it better to place the graph indicator inside a sequence frame? And does it make any difference whether the graph data is sequenced first or the settings?
03-01-2007 07:15 AM
Put he graph in a seq as Christian illustrated and make sure it happens before any of the other properties are applied.
Post an update of your code after you mod it, in the event the issue remains.
Ben